4 ms·
Yeah because screw security, right? I'm hella fatigued too! Did you even read the article or just blast out your opinion reading the title? > With these chang
by joshmanders 11y ago
Yeah because screw security, right? I'm hella fatigued too!
Did you even read the article or just blast out your opinion reading the title?
> With these changes, you may be wondering what is going to happen to the existing Buffer() constructor. The answer is simple: nothing much. This pull request adds a note to the documentation that the existing Buffer() constructors have been deprecated however the constructor will continue to operate without any changes. In Node.js core terms we call this a “soft deprecation” or “docs only deprecation”. Existing code that uses the Buffer() constructor will continue to operate as it has before.
- officialchicken 11y agoConjecture much? Or do you just like to copypasta articles and not actually provide an argument. Often, when writing extremely high-performance code, you give up security (and rely on higher-level contexts, like jails) A stable API and one that should have had the zero-out feature to begin with would have been a better response to my statement.