3 ms·
Ultimately the interesting thing to know is why they decided to stay on Rails instead of rewriting everything in a more performant language.
by pmontra 3y ago
Ultimately the interesting thing to know is why they decided to stay on Rails instead of rewriting everything in a more performant language.
- aaronbrethorst 3y agoJoel Spolsky wrote about it, actually: https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-...
- ericb 3y agoCPU cost is the obvious driver of who will win in this space, ergo, the correct optimization is to rewrite in assembly.
- iimblack 3y agoDon’t they also have a ton of custom ruby stuff like their own jit?
- campbel 3y agoThey employee the creator of yjit https://shopify.engineering/yjit-just-in-time-compiler-cruby https://shopify.engineering/yjit-just-in-time-compiler-cruby
- riffraff 3y agoShopify did develop a jit, but it's part of the main ruby runtime (they did other performance improvement too, all available in the standard ruby).
- abhibeckert 3y agoModern CPUs are fast, and it's trivial to scale compute instances if you need that. The database would be the bottleneck and that's got nothing to do with rails - it's all mysql.