René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Introduce the Nil Object","articleBody":"Hello and sorry in advance for all typos!\n\nI'd like to introduce a new Object in the core, which consistently represents a null value but is not `null`. Why is this interesting?\n\nOne of the main pain points in Streams (not just core) is that `null` isn't a good choice for end-of-stream value in object mode. Highland.js resolves it with it's own _.nil value. But this works fine only for the same install. as soon as we have two dependencies, each having it's local highland dependencies, the _.nil check is flawed. a central instance would solve some pains here.\n\nwhy core? it's the single point of truth in Node.js context. This value could also provide more interoperability to different user-land packages.\n","author":{"url":"https://github.com/greelgorke","@type":"Person","name":"greelgorke"},"datePublished":"2014-12-10T13:29:55Z","url":"https://github.com/nodejs/node/issues/136"}