Me: Computer, please install this program
Computer: that program is dangerous
Me: why is it dangerous? It's a text editor.
Computer: Exactly! It can write FILES! To your HARD DRIVE! Do you understand how INSANELY DANGEROUS that is? Files! Just anywhere! Brrrrr. Don't thank me, I'm just doing my job. Keeping you safe.
Me: download it anyway, please. I want to edit files.
Computer: I'm reporting you for this. You are a menace to society. Files. For shame.
Me: What should I be doing instead of files?
Computer: Glad you asked! It's 2020. You should be spinning up a Kubernetes of Dockers on your public cloud each of which is a Github which send JSON messages over HTTP3 to the microservice host on your Virtualbox private cloud which is running a whole bunch more Dockers each of which is a Node.js which is pulling dependencies from
Me: files seemed a bit simpler than that
Computer: WELL WE HAD A VOTE AND YOU WEREN'T THERE AND WE SAID FILES SUCK.
@feoh the answer to "why make everything so complicated" is of course, "because Google won't fund any technology that can't handle a billion nodes, and if you're running a billion nodes the complexity pays off after the first million or so"
if you're trying to run one node, the complexity.... maybe doesn't pay off.
@natecull I think 'done wrong' is an oversimplification, but, I mean, look at the entire leftpad() fiasco as a for-instnace. One person de-publishing their work brought large chunks of the node.js ecosystem crashing down around its ears, and then there's the huge issue with malware in the NPM package registry... The list goes on.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!