4 ms·

I know I am going to get some hate for this from the "Python-stans" but..."python" and "performance" should never be associated with each other, and same for an

I know I am going to get some hate for this from the "Python-stans" but..."python" and "performance" should never be associated with each other, and same for any scripting/interpreted programming language. Especially if it has a global interpreter lock. While performance (however you may mean that) is always a worthy goal, you may need to question your choice of language if you start hitting performance ceilings. As the saying goes - "Use the right tool for the job." Use case should dictate tech choices, with few exceptions. Ok, now that I have said my piece, now you can down vote me :)

danielrico 1y ago
That's used by some people as excuse to write the most inefficient code. Ok, you are not competing with c++, but also you shouldn't be redoing all the calculations because you haven't figured the data access pattern..
ahoka 1y ago
Have you read the fine article?
- game_the0ry 1y ago
  I did, thought it was pretty good an upvoted it.
throwaway6041 1y ago
> the "Python-stans" I think the term "Pythonistas" is more widely used > you may need to question your choice of language if you start hitting performance ceilings. Developers should also question if a "fast" language like Rust is really needed, if implementing a feature takes longer than it would in Python. I don't like bloat in general, but sometimes it can be worth spinning up a few extra instances to get to market faster. If Python lets you implement a feature a month earlier, the new sales may even cover the additional infrastructure costs. Once you reach a certain scale you may need to rewrite parts of your system anyway, because the assumptions you made are often wrong.
- game_the0ry 1y ago
  > Developers should also question if a "fast" language like Rust is really needed... Agreed.
deleted 1y ago
[deleted]
wiseowise 1y ago
Do you get off from bashing on languages or what?
ActorNightly 1y ago
>"Use the right tool for the job." Python + C covers pretty much anything you really ever need to build, unless you are doing something with game engines that require the use of C++/C#. Rust is even more niche.

danielrico 1y ago

That's used by some people as excuse to write the most inefficient code. Ok, you are not competing with c++, but also you shouldn't be redoing all the calculations because you haven't figured the data access pattern..

ahoka 1y ago

Have you read the fine article?

game_the0ry 1y ago
I did, thought it was pretty good an upvoted it.

throwaway6041 1y ago

> the "Python-stans" I think the term "Pythonistas" is more widely used > you may need to question your choice of language if you start hitting performance ceilings. Developers should also question if a "fast" language like Rust is really needed, if implementing a feature takes longer than it would in Python. I don't like bloat in general, but sometimes it can be worth spinning up a few extra instances to get to market faster. If Python lets you implement a feature a month earlier, the new sales may even cover the additional infrastructure costs. Once you reach a certain scale you may need to rewrite parts of your system anyway, because the assumptions you made are often wrong.

game_the0ry 1y ago
> Developers should also question if a "fast" language like Rust is really needed... Agreed.

deleted 1y ago

[deleted]

wiseowise 1y ago

Do you get off from bashing on languages or what?

ActorNightly 1y ago

>"Use the right tool for the job." Python + C covers pretty much anything you really ever need to build, unless you are doing something with game engines that require the use of C++/C#. Rust is even more niche.