3 ms·
Though, they ended up writing a whole new Ruby JIT to deal with Ruby's performance, so clearly at some point the trade-off changes from "no systems programming,
by remexre 5y ago
Though, they ended up writing a whole new Ruby JIT to deal with Ruby's performance, so clearly at some point the trade-off changes from "no systems programming, a highly dynamic language instead" to "hardcore systems programming, to make the highly dynamic language fast enough"
- Mikeb85 5y agoI mean, if you can get performance for free, why not? Doesn't mean Ruby was too slow...
- hiptobecubic 5y agoI think the takeaway here is that it was more sensible to reimplement Ruby than to use something else. Think about that for a moment.
- jashmatthews 5y agoShopify got to huge scale first and then started sponsoring TruffleRuby and YJIT as research projects.
- shroompasta 5y agoInstagram was also initially built in monolithic Django