3 ms·
Anyone know why Guido seems to have reversed course in terms of keeping the CPython interpreter as simple as possible & is now supporting the addition of variou
by vlovich123 4y ago
Anyone know why Guido seems to have reversed course in terms of keeping the CPython interpreter as simple as possible & is now supporting the addition of various performance improvements to the interpreter?
- endgame 4y agoNot a python programmer, but I would guess that a) the language's semantics are pretty well-understood now and I wouldn't expect too many new control structures etc to come in (changes that would be much harder to make to an aggressively-optimised interpreter) and b) python is now so widely deployed that even small performance improvements are going to make large aggregate improvements to total time spent evaluating, total energy usage, etc.
- eesmith 4y agoI have a hard time understanding what "pretty well-understood now" means. Could you elaborate? The match statement was added in 3.10. That's a control structure with a pretty big change in semantics, right? And done only two years ago - well after this performance push began. What sort of changes do you think are precluded now, that might not have been precluded 10 years ago when things were less optimized? Since you aren't a Python programmer, you can't really answer these questions, which make me feel like your response muddied the waters rather than providing useful insight.
- hgftr 4y agoIt seems to me that he has tried to keep Python for the web relevant at Dropbox by adding typing and asyncio, but Dropbox switched to Golang. Now he is trying to keep it relevant for the web by adding the small speedups. (I say "he", actually most of the work is done by other people.)