René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"meta: planning for promisified fs and crypto","articleBody":"This is largely a heads up.\r\n\r\nYesterday I posted a poll to Twitter asking how users felt about core providing a promisified API for `fs`... with two hours remaining in the poll, this is the result:\r\n\r\n![image](https://user-images.githubusercontent.com/439929/30445325-7fde30f0-993a-11e7-9f96-1d5c0ce31316.png)\r\n\r\nIt's clear that there is strong demand. I have heard from many who like the fact that `util.promisify()` is now a thing but feel that being forced to use it in order to get promisified core APIs is not a very ergonomic experience, and while many are using Promise-wrapper libraries to achieve this, there is obviously a strong sentiment towards having these provided by core itself.\r\n\r\nTherefore, I will be actively working towards the goal of providing Promise-enabled versions of all of the `fs` and `crypto` APIs in core. This will not be done all at once as there are a number of changes that may be required. For the crypto APIs, I will likely wait until async-iterators have landed with V8 6.2.\r\n\r\nI understand that not everyone is in love with Promises and not everyone wants to use them. The changes I have in mind will not touch the existing APIs, so anyone who wants to ignore the Promisified versions will be able to.","author":{"url":"https://github.com/jasnell","@type":"Person","name":"jasnell"},"datePublished":"2017-09-14T17:54:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":48},"url":"https://github.com/15413/node/issues/15413"}