Re:The GIL and its effects on Python multithreading
by pharmakom on Wednesday September 29, 2021 @07:13AM
(#28692261)
Does this seem really inefficient to anyone else? Why is there not a language that can do the prototype and offer a high performance ceiling? Julia seems like a candidate.
[ Parent
| on HN ]
Re:The GIL and its effects on Python multithreading
by penteract on Wednesday September 29, 2021 @11:55AM
(#28695439)
There's a language design tradeoff - Python is is the result of the designers almost never saying "We should do this to make Python faster, although it would make the language slightly harder to program in."
This even goes as far as choosing not to make improvements that improve performance but make the implementation more complex (for example adding a JIT), which allows Python to continue to add language features.
Re:The GIL and its effects on Python multithreading
by lmm on Wednesday September 29, 2021 @09:01PM
(#28702033)
The language isn't the hard part. One of the more programming-oriented data scientists was actually happy to write Scala to start with, but honestly getting from a prototype to a production-quality implementation is pretty much a rewrite anyway (e.g. you have to consider all the error cases).
Re:The GIL and its effects on Python multithreading
by FuckButtons on Wednesday September 29, 2021 @03:25PM
(#28698610)
It doesn’t work like that in any other industry, why should it work for software? Mechanical engineers don’t put prototypes into production, why should software engineers?