3 ms·
Even with multithreading Python will still be slow. It's not like singlethreaded Python can keep up with singlethreaded C or even JS. This will just allow peop
by KeplerBoy 3y ago
Even with multithreading Python will still be slow. It's not like singlethreaded Python can keep up with singlethreaded C or even JS.
This will just allow people to waste even more compute resources to get somewhat quick results from Python instead of doing the right thing.
From an ecological viewpoint this PEP will be disastrous and keep entire power plants online.
- tjpnz 3y agoThe text editors people use to write said code will keep even more power plants online.
- miraculixx 3y agoEspecially PyCharm with its endless indexing. Have the time its key features are not available bc it has decided to go on another indexing spree. Alas that's for another thread ;)
- AlphaSite 3y agoPython is also getting a JIT, they’re pursuing performance on all axis.
- hanselot 3y agoSometimes the right thing is writing code in a language that reaches market before runway runs out.
- dgb23 3y agoEcosystem churn and exposing more issues to python contradicts this. The whole point of using languages like python, js etc. is to not worry about whole classes of problems and intricacies. There are modern languages with great tooling like Go, Rust or Clojure that have excellent support for safe concurrency and parallel execution etc. And there are reliable, well established languages like Java/C# that have been doing this forever.
- miraculixx 3y agoThis. Python had a unique stance, it was different for a good reason. The seamingly endless attempt to become more likeable to yet another subgroup of needs is not a good development. It started with static typing, it continued with async, and now we have free threading as the final draw.
- KeplerBoy 3y agoThat's fine for regular Python, but this doesn't convince me for multithreaded Python. Most Python modules which are optimized for performance (numpy, pytorch, pandas, and all others built on top of them) are already multithreaded and drop the GIL so you can parallelize your workload with the threading module. If someone really needs several threads of pure python being interpreted, something is afoul imo.
- BiteCode_dev 3y agoDo you include the man hours in those calculations? Because they pollute a lot between the car, the food, the electricity the computer and internet for devs consumes, etc.