Open source maintainers are out of bandwidth
Python's experimental JIT is being removed. Commenters called it bittersweet. One said they're tired of rewriting hot paths in Cython or Rust. Another said a technically exciting feature is dying partly to bureaucracy and a lack of personal bandwidth. A third made the conservative case: Python is a mature language with a huge user base, and backward compatibility matters more than speed. On the Debian side, a maintainer quit uploading to NEW, citing the use of LLMs in the process and the loss of unpaid free time they were willing to give.
The pattern: important infrastructure rests on a few people with limited time, and those people are now also dealing with AI-generated contributions, spam, and policy fights. When one drops out, features die.
Gforth hit 1.0, the OpenGL ES 3.0 teaching thread drew praise for forcing students to learn fundamentals, and the Pratt parsing post got a tidy tutorial discussion. Craft and fundamentals still have an audience in a loud time.
So what?
If your product depends on an open source project, find out how many people actually maintain it, and consider funding or contributing. A bet on a feature still labeled experimental, like Python's JIT, can disappear with little warning.
Read these
Python's experimental JIT to be removed
I will no longer upload to NEW
Gforth 1.0
I still teach OpenGL ES 3.0
Writing about pratt parsing so I remember it