3 ms·

I am sorry this thread is turning into a flame... I would like to make clear that I am not questioning whether or not US is good thing to happen to CPython, ju

by ot 16y ago

I am sorry this thread is turning into a flame... I would like to make clear that I am not questioning whether or not US is good thing to happen to CPython, just that it is now a project without maintainers (the post suggests that they will stop working on it after the py3k-jit merge) and without an active community. As you said it is a very complex piece of code and even if it is "still functional" it is definitely not ready, as the performance gains are not substantial. I have nothing against calling it "stalled", but IMHO it is just an euphemism for "dead". Also I don't understand why people at Google decided to stop investing on it, the cost of 3 full time engineers is nothing compared to the millions they would save with a more efficient python implementation, given their huge python infrastructures (App Engine, for example).

jnoller 16y ago
If this is a flame war, then it's a pretty tame one :) As for Google's intentions, I've learned (as it has been explained to me time and time again) - never attribute smaller decisions to a larger strategy or "plan" of Google's. It probably not that they decided to stop investing in it, more than "something more interesting came up". I do wish that we could have funded work on core/the interpreter. That would be nice.