Re:Python adopts a 12-month release cycle
by Lendal on Friday November 01, 2019 @01:00PM
(#21421043)
Given that the pace of technological innovation cannot be stopped and all existing technologies have flaws, the alternatives are:
A) Accept that your language will change over time and manage it.
B) Over time, keep changing to better languages after your language dies out.
Yeah, I think A would be the preferred option.
On why fixed release cycles are a good thing, I find this FAQ by Herb Sutter of C++ fame enlightening: https://herbsutter.com/2019/07/13/draft-faq-why-does-the-c-s...
It doesn't make them necessary, just likely better than the alternatives (ie. no change or changes “when it's done”).