2 ms·
I think the point many are making here is, if you're going to break compatibility as was done with Python 3, then fix the underlying issues with the implementat
by filereaper 10y ago
I think the point many are making here is, if you're going to break compatibility as was done with Python 3, then fix the underlying issues with the implementation.
- Python 2 calls out to C code alot? Ok, rebuild the interpreter in such as way that allows for a JIT. Prevent callouts to C or severely limit them. JITs are mature technologies now, many dynamic languages have it.
- Remove the GIL, make it fan out for multicore.
- Add a Generational Garbage collector, remove the reference counted one with timely finalization.
- Add back all the missing features for FP that people are asking for.
If you're going to break compatibility, don't take half-measures, go all the way.