64
Python
143d

So, I was out cruising in my sports car the other day. Porsche, two seater, about 400 hp.

When I stopped at a red light I was next to a man driving his family of four in his Volkswagen. I revved my car to show my power, but he seemed unfazed by my superior engine. When the light became green I floored it, he didn't have a chance of catching up, I just left him behind and laughed. He's so stupid for driving that slow car.

I can't understand why anyone would ever want to drive a Volkswagen when they are just so obviously slow?

👆This is how you sound like when you compare languages only based on how fast they are.

Comments
  • 14
    Then he put the dsg into d and floored the 2.0 crtdi and left your disgusting boxer in the dust
  • 6
    I drive a slow small car for reasons of economy and ecology. But as far as I know python, c an go all come with the same price tag and footprint. Of course there are other things to compare than speed. But in terms of speed python is really weak.
  • 16
    You had us in the first half... 🤣🤣🤣🤣
  • 4
    Good one mate
  • 7
    If the choice is between a Volkswagen and a Volkswagen as fast as a Porsche, the choice is obvious.
    There are other factors than speed. But speed in most cases is the equivalent of run time efficiency; and even if run time is cheaper than development time (which, by the way, is the reason for a lot of problems modern software has) it should be the most important thing to consider when choosing the tool for a job because every compromise you make here will affect every user every time while using your software.
  • 3
    @Benedikt if like the majority of companies your budget is limited and you throw it all at speed over a few hundred ms response latency then your app may end up being a dull system where users' real needs for features are not satisfied.

    It's an extreme argument, just like yours.

    Besides in most business scenarios I can guarantee you that an user doesn't give that many flying fucks if their app does X in 150ms or 950ms. Which gives you quite a margin to play with.

    We all have the same tendency to always judge in black or white like all this neverending faster/slower debacle.
    Sometimes in real life the trick is finding that sweet spot where everything's balanced, including speed, features, looks, DX, productivity and what have you.

    There are ofc extreme cases where speed is all that matters. They're rare.
  • 5
    @molaram Yes, you are talking about an extreme example, about an edge case. I did not speak about absolute performance, about the last milliseconds, but about efficiency.
    Think about Wirth's law: Software is getting slower more rapidly than hardware becomes faster.
    Why? Because people give development time more value than execution time.
    I don't say that thinks like Python, NodeJS, Electron, Angular, Unity and such are useless (I use some of them myself quite often) or that there are no reasons why bloated and inefficient software is as it is, but that we should runtime efficiency value much more because otherwise our software is getting slower more repidly than our hardware becomes faster.
    Look at the hardware requirements for modern software, from the most simple thinks to high end games; efficiency is missing everywhere and this wasn't the case when hardware wasn't as cheap as it is today.
  • 1
    @Benedikt this is all very relative .
  • 2
    @pythonInRelay overpriced garbage.
  • 2
    Well...
  • 3
    Side note: Porsche and Volkswagen are actually the same company. Porsche was bought by VW in 2009; the Porsche Holding now holds > 50% of VW.
  • 1
    @w00000t They also own: Audi, Ducati, Bentley, Bugatti, Seat, Skoda, Lamborghini, MAN and Scania.
  • 1
    Some cars are meant for everyday street driving, some cars are meant for circuits.
Add Comment