Closed
Description
I know this is probably jumping the gun, as the 1.0 was just released, but I think a lot of people may have this question.
Are the stability indexes in the documentation up to date? The online documentation states 1.0.1 is the current version.
This is significant because 1.0 is supposed to preserve backwards compatibility for ever (see quote). But the following indexes are marked unstable:
- Stream
- Cluster
- Crypto
- punycode
- readline
- tty
- Domain (this is basically deprecated, right?)
Of course, the quote below says "no node 2.0 is not a commitment, but a prediction."
Quoting Isaac Schlueter (this was a while back, 1/2/2012):
When was the last time you updated your version of awk or sed or grep,
or even thought about them? For all intents and purposes, those
tools are *done*, and that's a big part of why they're so useful and
have been able to spread so widely. That's why you *actually notice*
when some OS has a relevantly different sed, because it's so rare.
We need to make node the kind of stable platform that can be a part of
the operating system and Just Work. Going from 1.0 to 2.0 would mean
another significant architectural change, and I would consider that a
failure on our part. Not a "this was all for naught" type failure,
and definitely not something that we'll hesitate to do if the
situation warrants it, but certainly an indication that we didn't plan
as well as we should have.
So, "no node v2.0" is not a commitment, but it is a prediction.
(Unless, of course, we decide that 2.0 means something other than
"architectural break from 1.0", in which case, who knows? Ultimately
it's just a number anyway, let's not forget that.)
Metadata
Metadata
Assignees
Labels
No labels