3 ms·
I somehow got stuck upgrading from Rails 3 to Rails 4. Nightmare... I've been through 5 Rails upgrades. Rails 2 to Rails 3 was a nightmare... Rails does not s
by briantakita 12y ago
I somehow got stuck upgrading from Rails 3 to Rails 4. Nightmare...
I've been through 5 Rails upgrades. Rails 2 to Rails 3 was a nightmare...
Rails does not scale well with complexity & is a pain to maintain...
There are a number of reasons for that. Rails started off favoring syntactic sugar over architectural integrity. They are gradually iterating toward a solid architecture. However, that required some significant api changes, which causes upgrade pain.
Also, the prevalence of monkey-patching (largely due to an unsound & overly complicated architecture), exasperated these issues.
Rails architecture is still overly complicated & misses the mark, IMO.
DHH's infamous "golden path" direction put the blame on the developers, when Rails itself had some major architectural flaws.
Rails Routes + Controllers are horrible. Why do we want an extra level of indirection? Sinatra/Express.js are easier to reason about RESTfully.
Asset Pipeline is horrible. The Node.js ecosystem (i.e. browserify) is much better. Client/Server separation of architecture scales in complexity more readily than the Rails monolith monstrosity.
I'm kindof bummed that Rails became so big. The "Rails Way", while being a step forward from what was there before, became too prevalent; sucking up too much mindshare; inhibiting further evolution of the broader ecosystem.
It's time we let Rails slowly die. There are many better libraries & frameworks out there.