Wouldn't Django, with its automatic admin, be better for replacing Access than Rails? The scaffolding in Rails is pretty bare-bones, but the Django admin (IMHO) is good enough to be used as the actual app if the situation warrants.
It's not that Rails culture makes GUI's the end product, it's that it's the necessity of the product. It's a web framework, not a database GUI. You could <i>build</i> a database GUI in Rails easily enough, but you're still using a database GUI that happens to run on a web framework.<p>The ignorance here (or at best, tenuous reasoning) is apalling. Jeez. You'd think this guy has never used Rails or something.
"Microsoft Access had been my preferred tool for creating applications centered on a relational database."<p>Here come the down mods, but anyone making that statement automatically loses any credibility of tech savvy and generates an enormous amount of pity. If access were all I could use, I would run scratch my eyes out.
Wait... does anyone know of a startup other than Caspio that is looking to target the Access market?<p>Rails isn't quite right for it. The world really does need an access-like product.
You may care to read the opinion in the article linked here: <a href="http://news.ycombinator.com/item?id=591102" rel="nofollow">http://news.ycombinator.com/item?id=591102</a><p>[Oracle office stuff] <i>did one thing better than any competitive product I knew of: it stored everything as rows in the standard database</i>