News for hackers. Stuff that matters.
Re:Any sufficiently advanced uninstaller is indistinguishabl... by fergie on Wednesday September 13, 2023 @02:32AM (#37492952)
Why is the recommended javascript way of doing it

    var fso = new ActiveXObject("Scripting.FileSystemObject");
rather than

    var fs = require('fs') // (or the appropriate ES6 incantation)

?
Re:Any sufficiently advanced uninstaller is indistinguishabl... by tedunangst on Wednesday September 13, 2023 @02:42AM (#37493029)
Windows doesn't ship with node.js.
Re:Any sufficiently advanced uninstaller is indistinguishabl... by casselc on Wednesday September 13, 2023 @02:43AM (#37493034)
Because it’s JScript, which was abandoned prior to ES6.
Re:Any sufficiently advanced uninstaller is indistinguishabl... by thangngoc89 on Wednesday September 13, 2023 @02:44AM (#37493036)
It’s JScript. Not JavaScript and definitely not Node.JS
Re:Any sufficiently advanced uninstaller is indistinguishabl... by coldtea on Wednesday September 13, 2023 @02:56AM (#37493111)
The latter is not "javascript" in general, it's just a Node.js (a specific v8 Javascript runtime + native integration and libs like fs bundle) API.

And the former windows version is JScript which is an implementation Javascript just using an different name for trademark reasons, but tied to an old version of the JavaScript standard (which is confusingly called "ecmascript" officially), plus some Windows-specific integrations, like ActiveXObject and COM/OLE support.

(There's also a later .NET version of JScript to add to the confusion).

Re:Any sufficiently advanced uninstaller is indistinguishabl... by vbitz on Wednesday September 13, 2023 @02:56AM (#37493113)
Because JScript was introduced back in Windows 98 and the modern APIs were introduced 10 years later (in the case of Node.js).