| ▲ | Python JIT project was asked to pause development(discuss.python.org) | |||||||||||||
| 34 points by kbumsik 2 hours ago | 9 comments | ||||||||||||||
| ▲ | kelvinjps10 a minute ago | parent | next [-] | |||||||||||||
What a shame it will receive a halt when they where starting to make progress I know that after submitting the pep it will go back to development. But t would have been better to just keep the development and the pep for an actual release or continue and if gets rejected ask them to stop | ||||||||||||||
| ▲ | 12398761 a minute ago | parent | prev | next [-] | |||||||||||||
That was kind of overdue. The project started five years ago while massively overpromising. They should perhaps have kept it in a separate branch back then, but now is the next best time. CPython's selling point was that it is simple, fast enough with C extensions and the code was accessible. Complicating the code base for occasional 50% speedups (and regressions ...) just isn't worth it. There are so many other languages that fill that need. Now, I hope that the PEP does not overpromise again and is accepted because of Instagram pressure. Instagram can keep its own JIT fork or switch to PHP, Go or whatever. | ||||||||||||||
| ▲ | Qem an hour ago | parent | prev | next [-] | |||||||||||||
> For that reason, the Steering Council is formally requesting a Standards Track PEP be authored that the community can discuss and the Steering Council can formally accept (or reject), making the case for the JIT as a supported, non-experimental part of CPython: its guarantees, its maintenance commitments, and its impact on redistributors. I didn't notice the current PEP was a provisional one. Hope the new one gets approved. The experimental JIT was reported to finally breaking even and surpassing the default interpreter just a couple of months ago[1]. [1] https://fidget-spinner.github.io/posts/jit-on-track.html | ||||||||||||||
| ||||||||||||||
| ▲ | OutOfHere 28 minutes ago | parent | prev | next [-] | |||||||||||||
Losing development momentum for a beancounting reason like this one is a sure way to kill a project. It works every time. Once development is halted, it is very difficult to pick it back up. | ||||||||||||||
| ▲ | jhayward 6 minutes ago | parent | prev | next [-] | |||||||||||||
> While the intent is not to call for competing proposals, we believe that now is a good time to discuss and propose alternative proposals as well. If I were a contributor I would read such language as saying "we have no respect for you or your intelligence, so we'll just straight up gaslight you and expect you to accept it." The dictum can't be read literally - it has to be read like the manipulative, narcissist-speak that it is. And what it's telling you is - get out. | ||||||||||||||
| ▲ | nmstoker an hour ago | parent | prev [-] | |||||||||||||
Duplicate of here: | ||||||||||||||
| ||||||||||||||