What is the rough time estimate for the next release? I know, whenever it's ready
1 month, but I keep saying that...
What is the plan for each subsequent release, up to 1.0? The todo.txt just lists 0.9.x, so maybe it will asymptotically approach 1.0 but never get there.
Essential for 0.9.6:
Essential for 0.9.8:
What does being at 1.0 mean?
It means we make some backwards compatibility promises and hence feature freezes. In particular, bugfixes will be backported to the version 1.x line and all new stuff will be added to a 2.x line. Also code that's in a "grey area" should continue to compile in the version 1.x line, but the compiler might give new warnings about questionable constructs.
It means we make some backwards compatibility promises and hence feature freezes. In particular, bugfixes will be backported to the version 1.x line and all new stuff will be added to a 2.x line.
Hmmmm... is that a good way to approach future development? Seems to me that this line of thinking is what has brought on the Python 2/3 schism.
Nimrod already has a tool for prettifying Nimrode code right? Would it perhaps be possible to create a framework that allows Nimrod to "upgrade" Nimrod code, by applying some rules to transform the code into code compatible with the new version, wherever possible? I've haven't seen anyone do something like that yet.
It means we make some backwards compatibility promises and hence feature freezes. In particular, bugfixes will be backported to the version 1.x line and all new stuff will be added to a 2.x line. Also code that's in a "grey area" should continue to compile in the version 1.x line, but the compiler might give new warnings about questionable constructs.
Does this mean that we won't get new features which do not affect backward compatibility in the "1.x line"?
Nimrod already has a tool for prettifying Nimrode code right? Would it perhaps be possible to create a framework that allows Nimrod to "upgrade" Nimrod code, by applying some rules to transform the code into code compatible with the new version, wherever possible? I've haven't seen anyone do something like that yet.
Doesn't Python have a tool which converts Python 2 code to Python 3 code? In any case the Python 2 vs Python 3 situation is far worse because Python code is not compiled, with Nimrod your apps will not depend on any interpreters and so will continue to work post-compilation.
Hmmmm... is that a good way to approach future development?
It's the only way I can see that works. Stability comes from continued bugfixes while at the same time stopping adding new features.
Nimrod already has a tool for prettifying Nimrode code right? Would it perhaps be possible to create a framework that allows Nimrod to "upgrade" Nimrod code, by applying some rules to transform the code into code compatible with the new version, wherever possible?
That can work but it takes up precious resources that would better be spent elsewhere.
Does this mean that we won't get new features which do not affect backward compatibility in the "1.x line"?
Yes, pretty much.