3 ms·
I think this is a very uphill battle because JS and most other languages are missing a key ingredient that Rails has had for 10+ years. It's having a long runni
by nickjj 6y ago
I think this is a very uphill battle because JS and most other languages are missing a key ingredient that Rails has had for 10+ years. It's having a long running large real world SAAS app that Rails is extracted from.
That means every feature of Rails is derived from a practical use case, and then it's well tested in that app before it's pushed out to the community. That's tested from an API and functionality point of view. By the time end users start to use it, the feature has likely been running in production for 6+ months. Maybe even serving billions of page views through it if you factor in Shopify and GitHub also running off Rails master.
It's all constantly in use, kept up to date and iterated on as a whole.
Creating a starter kit / boiler plate of libraries and opinions in another language / web framework is not the same. I think this is why even after 10+ years there's only a handful of popular Rails alternatives in other languages.
- ivanhoe 6y agoThere's plenty of JS code written out of the real needs and by teams running huge projects, take just Facebook as an example. Problem is that there are thousands of solutions for everything, and that saturation and bad signal to noise ratio makes it hard sometimes to pick the right lib (or even hear about it in the first place). Rails have a huge benefit of having a single team behind it, so you always have a recommended way of doing things, and the whole community is smaller, less libs to test, less rubbish to avoid, making the experience much more linear...