4 ms·
A nit, but Ruby on Rails isn’t “old”. It’s mature. It still receives regular updates and release, even major version releases. What it isn’t any more is new or
by bartread 1y ago
A nit, but Ruby on Rails isn’t “old”. It’s mature. It still receives regular updates and release, even major version releases.
What it isn’t any more is new or trendy. Still pretty widely used though, and with good reason.
- fragmede 1y agoNot pick on Ruby, but is it a good reason? You've got 1 million lines of code and they’re written in Ruby and rewriting it would be, ah, untenable. But would ruby be the best choice today if you were starting from scratch? Maybe! But sheer inertia isn't a good reason in and of itself.
- dasil003 1y agoHe didn't say inertia, he said mature. It take a while for a language/platform to develop a solid ecosystem and stabilize. That absolutely has value, and is something you can't get out of a new system no matter what novel problems it solves. As far as new apps go, yeah I think it's still pretty optimal for a huge swath of web apps, especially for early incubation when you have <20 engineers and you need to move quick. Not if you need web sockets, or other concurrency / performance critical applications though.
- fgonzag 1y agoYes, I'd also think it's a great idea to build new apps in a language currently undergoing a distribution & supply chain war between the interested parties.
- fgonzag 1y agoIsn't the ruby gems community currently imploding and in the middle of a hostile takeover? Also I've read about quite a few recent politically aligned actions in the community. I don't know if I'd call that "mature".
- tdeck 1y agoThe same could be said about WordPress but it's hard to argue that isn't mature in the sense that your parent comment was referring to.