4 ms·

I don't see how any of that is relevant to the article, but the reason python beat out ruby was almost entirely due to ruby being really really slow.

• samhw 5y ago
  > the reason python beat out ruby was almost entirely due to ruby being really really slow Relative to Python, that language which notoriously makes C look like a sloth on training wheels...
  • joeberon 5y ago
    Python is much faster than MRI Ruby used to be back in the day
  • elcomet 5y ago
    So you might imagine what ruby felt like ...
  • spicybright 5y ago
    It's just an opinion, but in exchange for the speed hit you get a huge decent standard library, and lots of high quality libraries that you can stitch together much more easily than in C. In the vast majority of my use cases, I'll take the half second load hit in exchange for that (if it's even that long).
    • samhw 5y ago
      Yeah, it's totally dependent on what you're doing. It would be insane to write a simple script in C, and it would be insane to write an operating system in Python. Most code lies somewhere between those two extremes. I fully admit that the cult of performance is silly - and anyway, it can sometimes be easier to write performant code in a slightly more high-level language that you're extremely adept at writing. For instance, I'd wager most people could write a more performant web server in Go than they could in C, even if they could write a web server in C.