Re:Time for developers to address the chaos of Node.js and NPM
by calibas on Friday March 30, 2018 @01:17PM
(#16717936)
I don't know if it's still the case, but one of the first things I learned about JavaScript was how it was inherently secure. Then I actually started using the language, and learned what utter bullshit that is.
[ Parent
| on HN ]
Re:Time for developers to address the chaos of Node.js and NPM
by gramstrong on Friday March 30, 2018 @01:47PM
(#16718226)
> inherently secure
Who told you that? I don't think "inherently secure" is a thing in the tech industry.
Re:Time for developers to address the chaos of Node.js and NPM
by calibas on Friday March 30, 2018 @02:52PM
(#16718793)
I was taught that Javascript is safe because it has no input/output on its own, which is essentially true, but it's dangerous to work from that assumption since in the real world a program needs to have input/output to be useful.
Re:Time for developers to address the chaos of Node.js and NPM
by marshray on Friday March 30, 2018 @04:15PM
(#16719468)
Node.js adds that input/output.
Re:Time for developers to address the chaos of Node.js and NPM
by TheAceOfHearts on Friday March 30, 2018 @01:52PM
(#16718274)
The ECMAScript spec doesn't include details about its environment. You can run it in varying environments, each of which has different security criteria. For example, you can run a fully isolated JS VM that has no interactions with the real world, which is certainly quite safe. Node has full access to pretty much all the user's system resources, while the browser is a bit more sandboxed and restricted in what it can access.