3 ms·
> you better have chosen python JS maybe (well TS, not JS; you'd be a fool to use actually JS) but I've seen more than a few projects strangled by their choice
by IshKebab 4y ago
> you better have chosen python
JS maybe (well TS, not JS; you'd be a fool to use actually JS) but I've seen more than a few projects strangled by their choice of Python and the terrible performance it comes with.
People always say "it doesn't need to be fast"... until it does and it's too late. Or "we'll write the bottlenecks in C++"... until you realise that it's all bottleneck.
Mercurial and Scons are obvious public examples.
Language does make a difference, despite everyone being polite and saying it doesn't. Of course that doesn't mean it is the only or even biggest factor.
- mejutoco 4y ago> Or "we'll write the bottlenecks in C++"... until you realise that it's all bottleneck. Isn't this exactly how python works with pytorch, polars, and similar very fast libraries?
- IshKebab 4y agoYes it works for highly numerical code. Most code is not like that.
- mejutoco 4y agoIf we are pedantic all code running in a computer is numeric, but I get your point for gpu calculations for pytorch or numba, so I won't make that point :) I would describe polars a library to work with data (https://www.pola.rs/ https://www.pola.rs/). So we have a high-performance library in Python to work with generic data. I think that covers a lot of cases, since you can transform arbitrary parts of a program into data. Ask any lisp fan. Typescript is great, and the approach of having native high-performance modules works great for Python. You can offload, if you want to, a big part of your program to high-performance libraries. Maybe it is not the most elegant, but it works. Python is not cpp, but if it fits your use-case, it can be quite performant.
- cutler 4y agoStripe, Shopify and AirBnB did quite well with Ruby.
- IshKebab 4y agoRuby was such a poor choice for Stripe they ended up writing their own static type checker for it... https://stripe.com/blog/sorbet-stripes-type-checker-for-ruby https://stripe.com/blog/sorbet-stripes-type-checker-for-ruby > Unfortunately we were starting to see Ruby come apart at the seams: new engineers found it hard to learn the codebase, and existing engineers were scared to make sweeping changes. Everyone faced a constant tradeoff: run the fast, local tests which might not catch many breakages, or run all the tests, even the slow ones. Ruby was becoming a source of friction more than a source of productivity. I'm not saying you can't make good products with inferior languages.
- cutler 4y agoThat's after they had already made billions with Ruby and, BTW, Patrick Collison is still passionate about Ruby and has no plans to drop it even at Stripe's scale. No-one says Ruby will cater for all scaling scenarios but it can take you a long way with the advantage of moving quickly and developer happiness. Twitter started with Ruby and nothing stopped them form switching to Scala when the time was right. What is more common than ditching Ruby is splitting-off services to be written in a faster language. Best of both worlds. Your designation of Ruby as an inferior language begs the question inferior to what and inferior by what metric?