René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Documentation: Stability Indexes","articleBody":"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.\n\nAre the stability indexes in the documentation up to date? The [online documentation](https://iojs.org/api/all.html) states 1.0.1 is the current version.\n\nThis is significant because 1.0 is supposed to preserve backwards compatibility for ever (see quote). But the following indexes are marked unstable:\n- Stream\n- Cluster\n- Crypto\n- punycode\n- readline\n- tty\n- Domain (this is basically deprecated, right?)\n\nOf course, the quote below says \"no node 2.0 is not a commitment, but a prediction.\"\n\n[Quoting Isaac Schlueter](https://groups.google.com/forum/#!topic/nodejs-dev/88J3y7Msx3Y) (this was a while back, 1/2/2012):\n\n```\nWhen was the last time you updated your version of awk or sed or grep,\nor even thought about them?  For all intents and  purposes, those\ntools are *done*, and that's a big part of why they're so useful and\nhave been able to spread so widely.  That's why you *actually notice*\nwhen some OS has a relevantly different sed, because it's so rare.\n\nWe need to make node the kind of stable platform that can be a part of\nthe operating system and Just Work.  Going from 1.0 to 2.0 would mean\nanother significant architectural change, and I would consider that a\nfailure on our part.  Not a \"this was all for naught\" type failure,\nand definitely not something that we'll hesitate to do if the\nsituation warrants it, but certainly an indication that we didn't plan\nas well as we should have.\n\nSo, \"no node v2.0\" is not a commitment, but it is a prediction.\n(Unless, of course, we decide that 2.0 means something other than\n\"architectural break from 1.0\", in which case, who knows?  Ultimately\nit's just a number anyway, let's not forget that.)\n```\n","author":{"url":"https://github.com/alexwoehr","@type":"Person","name":"alexwoehr"},"datePublished":"2015-01-14T09:57:58Z","url":"https://github.com/nodejs/node/issues/387"}