Fact is, non-software engineering projects have been doing this for nearly a century. Software engineering is still struggling to do it, and we all pay the price for it with data breaches.

I'm pretty sure I already saw a story about a model reverse engineering from a binary. It's ultimately just assembler.

You mean upstream.

You can credit Jack Welch and the "MBA Revolution" of the 90s with this. "A good manager can manage anything!" is what they say. They are wrong in more cases than right.

Same shitty service, higher prices, shiny new name.

That's what really surprises me. Windows now lacks its equivalent of vi or nano. ("ed" doesn't count. Notepad in windows 11 is a completely different app, and it's pretty terrible in comparison. It became more like wordpad (another underappreciated app)

Odd that you never hear these kind of remarks about people switching to MacOS. It's just handwaved away under the assumption "Apple did it, so it's super easy". The fact is, users will very likely figure it out, even the dumber ones. The determination to set your own wallpaper goes a long way.

Control networks were around long before "the internet" existed. Remote sites like these would probably have employed a mixture of strip chart recorders collected at regular intervals (still in use to this day), a VHF/UHF radio link, maybe even a satellite uplink. You probably did less actual control because the link might have been one-way, but if you are running an oil well, there is also storage tank filling up that you needed to get a signal from the high level switch telling you to get your ass out there and empty the tank.

Long ago they just had people making rounds, and tanks just overflowed into berms if you didn't get there in time. I've seen the results myself. But we're all better off with this infrastructure communicating back to a central control.

You clearly have never worked in one of these environments. These PLCs don't just run everything by themselves; in fact, connecting them to an external system is pretty much required. In almost every case, they are monitoring temperatures, pressures, levels, etc and transmitting that information to a SCADA (or similar) so that control operators can make adjustments, call for maintenance, etc. Much of the data they collect is useed for making business decisions and very likely is subject to reporting required by regulatory agencies. Sure, you could try using a local data logger, but then not only do you have to collect that logger, but what if it fails and you don't find out for a month? Permit violation. It's just like operating a chemical plant except the footprint is much larger.

The industry standard is to use a VPN, so whoever is putting these PLCs directly "on the internet" is doing something that everyone has been told not to do for decades. The second "sin" is that the PLC was not in run mode, which would prevent any modifications. I wouldn't be surprised if it was mainly small organizations who just buy some off-the-shelf setup and stick a 2G or LTE modem in it.

Yeah, the assumption that it can be robots all the way down is predicated on a combination of ignorance and a belief in "exponential" improvements in robots, forever. Far more likely to hit a fundamental limit. A more likely outcome might be AI controlled, mostly brain dead meatbots.

I swear I typed ofetch and got autocorrected.

You're not wrong, but unfortunately they made the fetch API so "flexible" that it also requires extra code to do simple things like a timeout or external abort. So you have to spend time writing code on what is the least important part of your application - fetching a remote resoo. Or you can just use axios / fetch / whatever, and save yourself the time.

Right, this is the part I didn't get. How can you fall for "oh you need to install a new codec" bullshit. It's like a rogue plugin from 2005.

Fucking html editor from 1999.

Which is different than "The meeting said something on my system was out of date"

That makes it sound like you joined a meeting and Teams told you to install a malicious plugin, which is not what happened.

Franky, it says something about the developers if they fell for a powershell iwr | execute scam.