3 ms·
I feel like people got hung up on computational performance for a while. 5 to 10 years ago, a bunch of big startups hit the scale where they needed to intention
by SkyPuncher 4y ago
I feel like people got hung up on computational performance for a while. 5 to 10 years ago, a bunch of big startups hit the scale where they needed to intentionally work around Ruby's limitations. People seemed fixate on those performance issues while overlooking the business context - that hitting that scale means you are wildly successful and solving problems most startups never have the chance to solve.
It seems there's a swing back towards people considering raw productivity. Especially, at early stage or pre-product market fit.
Given that Rails is highly correlated with Ruby usage, it's simply hard to beat how much productivity and breadth that Rails gives you. Especially, with how much "grunt" work is easily handled by it.
I love trying new frameworks on side projects, but I always find myself coming back to Rails. There is inevitably some nuanced situation that the framework doesn't handle that would be ridiculously easy in Rails.
- dragonwriter 4y agoRuby has also improved single-threaded performance and introduced a parallelism construct, so, while it is still far from fast, the basic performance and scaling situation has improved somewhat.