3 ms·
The OA won't load so I'm basically just commenting on the headline. The purpose of a web framework is to abstract all the numerous nuts and bolts issues of bui
by dasil003 18y ago
The OA won't load so I'm basically just commenting on the headline. The purpose of a web framework is to abstract all the numerous nuts and bolts issues of building an application on the web which was never designed with applications in mind.
The reason Rails is so successful is because it identified the right interface to abstract for the maximum range of utility.
As a counter-example I often cite Drupal. Drupal is not just a CMS, but also a framework. It's incredibly well thought out and strikes an awesome balance of out-of-the-box functionality and customisability. The problem is that it comes with a lot of baggage, so you always end up with a lot of complexity that you don't need.
Adding high-level application features inevitably leads you down this road which—though appealing for projects without a proper budget (ie. most client work)—ends up forcing all kinds of small sacrifices in design, usability, performance, data modeling, and simplicity. Some projects could never get done without these sacrifices, so projects like Drupal are invaluable in terms of absolute value (especially to small businesses), but to add these features to something like Rails is to utterly destroy an incredibly useful general-purpose tool.
- jonnytran 18y agoI didn't mean in the core, necessarily. But it should be dead-simple to do -- a flip of a switch and a config file maybe.
- dasil003 18y agoDrupal ecommerce module is the perfect example. It tries it's best to be everything to everyone. I doubt you'll see a better turnkey solution that's not a standalone application.