cdmyrm

The whole point of magic cloud platforms is to upcharge for everything and convince people there's no other way to run software.

This should be considered criminal negligence.

Can I have a rootkit into your machine then? Since we're being hyperbolic.

1. Build a rootkit into your product.

2. Release your product.

Where is the paper wherein you've managed to solve the Halting Problem? I'd love to read it.

No, the absolute worst developers I've ever met are JS/TS developers. The entire ecosystem is a superfund site, courtesy of get-rich-quick bootcamps and the rent-seeking SaaS economy. Some tech bro spent three months teaching your entire company nothing but React; how good did you think your software was going to be?

Yes.

Serving HTML is actually really fast if you don't bolt 17 layers of JavaScript on top of it first.

There are plenty of other websites that don't do that. Perhaps one of those would work better for you?

Software developers don't actually write software anymore, they glue together VC-funded security nightmares every 1-3 years, before moving on to the next thing. This goes on and on until society collapses under its own weight.

npm is a nightmare.

Speak for yourself.

It's called air-gapping, and lots of adults do it.

Turns out, "knowing things" is a prerequisite for "doing things properly".

Any purported expert who uses software without considering its security is simply negligent. I'm not sure why people are trying to spin this to avoid placing the blame on the negligent programmer(s).

Should we outlaw C because it lets you dereference null pointers, too?

I'm sorry, but when will we hold the writers of crappy code responsible for their own bad decisions? Let's start there.

Good call. I'd seriously considering firing the developers responsible, too.

How confident are you that their log system is resilient, given the state of the rest of their software?

Yeah, turns out "modern" software development has more holes than Swiss cheese. What else is new?

This is actually precisely how package management works in Linux today... you release new versions, package maintainers package and release them, while ensuring they actually work. This is a solve problem, it's just that nobody writing JavaScript is old enough to realize it's an option.

You're allowed to have a support matrix. You can refuse to support versions that are too old, but you can also just... let people keep using programs on their own computers.