3 ms·

> The author is 100% correct on everything. The author is certainly correct on some things, but makes no good argument for why node.js should run in the Browse

> The author is 100% correct on everything. The author is certainly correct on some things, but makes no good argument for why node.js should run in the Browser. I'm not even clear he understands what node is, or what he would gain from being able to use it in the browser, when it can already run Javascript just fine as is. No, Google should stop the show and bring node.js to his browser because he can't be bothered to go to Google to look up what a PATH is. I'm not saying programming can't be much more user-friendly; it certainly can be and should. Heck, maybe Chrome would do well to ship with a lightweight IDE to edit code in outside of the console. But the author hasn't listed a reason node.js has a place in Chrome natively, and is going on to claim they should. Talk about entitlement.

xenocratus 6y ago
It's by no means an IDE, but Chrome does have Workspaces: https://developers.google.com/web/tools/chrome-devtools/workspaces https://developers.google.com/web/tools/chrome-devtools/work... . In any case, I remember using this (or something similar that maybe I forgot?) when I was doing frontend work, it was quite neat, especially if you had a local server recompiling things as you made changes.
imtringued 6y ago
There are tools that do what he wants but they are not node.js. That's the problem. The insistence on a specific tool and the desire that the entire world changes to accommodate you instead of just picking a different tool that does what you want.