3 ms·
The issue is that by the time you bring in an ORM/database migrations, form builder, link builders, asset pipeline, admin panel, etc you have basically hobbled
by swanson 13y ago
The issue is that by the time you bring in an ORM/database migrations, form builder, link builders, asset pipeline, admin panel, etc you have basically hobbled together your own ghetto version of Rails without the vast resources/support that Rails has. One of the benefits of Rails is that it has all of those features mostly baked in - at the cost of some bloat.
But my project doesn't need all that, you might say. Well, that's fine, then use something like Sinatra. But I wouldn't build a non-toy web application without the above things.
- static_typed 13y agoIt is somewhat ironic you chose the word ghetto when discussing Rails, as it reminds of Zed's previous article. I think it is a good thing for new and maybe even experienced Ruby developers to build their own, to see a way beyond all the meta magic and five minute blogs, and that you really don't need that much plumbing to get things moving and understandable. At least it didn't say roll Rails in five minutes - it would take much longer than that to bake in all the security holes and to stick YAML parsers all over the shop.
- w1ntermute 13y agoIIRC, Zed was referring to the community, and not the software.
- conanbatt 13y agoFortunately most of the libraries available in the community are not rails dependent anymore and you can make a custom setup with exactly the things you need rather easily. Rails specific and exclusive features are mostly conventions and the flow from routes to controller and views, which for me is very disagreeable.