It's a great stance for a language that focusing primarily on research and innovation, but it does put a damper on getting things done sometimes. Some stability

It's a great stance for a language that focusing primarily on research and innovation, but it does put a damper on getting things done sometimes. Some stability and concessions to practicality go a long way. I think that having a clean break at major revisions (e.g. Python 3, Lua 4.0 to Lua 5.0) and cleaning up cruft is probably a reasonable approach, as long as it's handled carefully and half the community doesn't stay with the old version. (It was easier with Lua because it's so small, and usually embedded in something else.)