When I want to point out to the kind of morons who post on the Internet, I'll tuck this post away.

Well, SD cards are basically a solid lump of plastic with metal contacts. That's what makes them exceptionally rugged because all the bits are suspended in a plastic/resin enclosure

As for the computers, the SSD data could be recoverable - chip-off data recovery is a thing. Basically you desolder the NAND chips, then use a rig to image them onto the PC.

The PC software then reconstructs the SSD data using the controller algorithms and data tables and rebuilding the mapping tables.

It does require the NAND be intact enough to read.

Yup, the sad truth is that if you really want to save children, you need to ban parents.

In the new CEO's expertly crafted I-am-villain statement; he explains: "The past, he added in an email, is “simply not relevant to the new future.”"

I, um, guess it was polite of him to not talk about "the bigger picture" to the people whose eyes he shut down?

Will these ones retain vendor support longer than the last batch?

Also remove the ability to load JavaScript off any host other than the originating one. Right now things are a huge mess because scripts can be pulled from anywhere, increasing the attack surface. It's why things like NoScript default to not running scripts from unknown hosts.

If every website had to host their own JavaScript, it would tighten things up a lot.

Sure it would make some webmasters jobs more difficult because they need to keep pulling in code from Facebook and Google and X and other social media sites as well as from ad servers, but if you want to add that third party junk you should add to your workload.

And it's something browsers can start doing by allowing only single site JS - it will load only the JavaScript from the originating host.

This way you can't compromise one host and simultaneously attack millions of websites.

Then you would be wrong. Probably best to recuse yourself from weighing in on this dicsussion.

Opinions change.

In the early days where the dot-com bubble was happening, unions didn't make sense when people were making big bucks for knowing their way around a keyboard. Most anti-union sentiment starts here because the people were the "hot stuff" and seeing everyone else as dinosaurs not wanting to learn the latest "hot stuff" to keep themselves employed.

Unions were seen as a way for the luddites to stay employed doing what they do and avoid the technological revolution that's happening around them.

Of course, then the dot-com bubble popped, millions were out of work and the great disillusion happened where the "hot stuff" could no longer get jobs paying millions of dollars and driving Ferraris, but the jobs fell back to earth. They still paid well so most anti-union sentiment remained.

Fast forward to today, when "hot stuff" tech jobs are finally seeing the pain, and "programming" jobs that pay $10/hr are starting to crop up on job boards as AI replaces them.

It also follows with the whole "learn to code" thing - great at the beginning because it meant luddites were learning the "hot stuff". Nowadays it's seen as a white elephant - training people to lower salaries even more by flooding the market.

You'll find the sentiment generally follows - when the going is good, unions are seen as unnecessary and useless. When the going starts getting rough, then people start looking at unions. The Chinese 996 was fine when you're 20 something making half a million dollars a year. But it's a lot less appealing when you're looking at jobs paying $75k a year and you're 35.

DLL Hell is the reason for snaps and flatpaks and other container formats.

Linux has DLL hell - it's caused by libraries being binary incompatible with themselves. Some libraries, like glibc, pride themselves on binary compatibility which is why programs linked against older glibc still run on newer glibc. But such capability means a lot of code goes into just keeping compatibility. It's why alternative C libraries exist that provide much of the same functionality but with half the size or less - they dump the backwards compatibility guarantees. Of course, they also only work for programs compiled against that library

If everything is properly versioned it all works great, but there's a lot of libraries out there and not all of them are properly versioned. You then end up with programs using incompatible versions of the library

In a fixed Linux system, sure, you can avoid such issues through careful library management and using overrides like LD_LIBRARY_PATH.

But there are also times when random binaries get passed about (in a company say) and it only works on half the Linux systems because the other half runs the wrong version of a library.

Or you compile something against a newer library, but because of odd system quirks it sometimes picks the wrong library version and errors out.

Big, complex programs like GIMP? Well it depends on hundreds of libraries, and chances are you either have to compile it yourself, or it's provided by your distribution because getting a random compiled version to work will likely have all sorts of library versioning issues.

So you can say no, but big complex applications, and even commercial software are adopting such formats so they guarantee the runtime environment and eliminates most of the support calls on missing libraries or libraries missing symbols and other fun things.

It also traps a car in the dead end. Given it's a neighborhood, there's probably not much space so stacking cars in the dead end will also mean neighbors are inconvenienced by having cars blocking their street or just making it much harder to navigate around.

Police radio? CB radio?
If you don't want data to be read. encrypt it. Don't rely on the links to protect you. As soon as your WiFi data gets to the AP, it's no longer encrypted.

Police radios these days are often trunked which is about as best you can do - many places require unencrypted radios because it's your right to be able to audit law enforcement - the same set of rights that let you record the police (audio, video). Many have switched to trunked radio systems which helps get better frequency utilization by finding an empty channel. Though many systems are also digital to allow for even higher utilization, but they have to be unencrypted.

CB radio, by its very nature must be unencrypted - it is illegal to encrypt because it's given to the public to use and you're not allowed to monopolize it.

Lots of other stuff are unencrypted as well - usually things distributed on a one-to-many format. Aircraft use ADS-B, ships use AIS, which are all unencrypted because they're meant to be received by everyone in an area to decode and display - it's a literal broadcast. Sure you can spoof things, so it's also unauthenticated, but there's no way to encrypt things so anyone and everyone can authenticate it without anyone and everyone also having the key rendering the whole exercise moot.

Many satellite transmissions are unencrypted on purpose - weather satellites often transmit their data in the clear, as are satellite fax transmissions (again on a one-to-many transmission so you can send weather data to many vessels at the same time)

Much of the data is unencrypted because of its nature. You can encrypt it, but everyone getting it will then need the key to decrypt it and now you have a key distribution problem.

Funny enough, the commercial side of things is where stuff is encrypted - DBS satellites (e.g., Dish, DirecTV), satellite radio, etc.

I am sure my dedicated 5080 with cuda can run circles around your mac

I suspect that they feel at least incrementally less burned in this case; since, while it wasn't obviously a good idea for a product, it at least goes somewhere: if you can make a phone functional and adequately rigid at that size; it's quite possible that there's a more sensible device size that you can still apply the miniaturized motherboard and whatever mechanical engineering you did for rigidity to; and just fill the rest of the case with battery; and there may be some other cases where the ability to get an entire SoC and supporting components into a particularly tiny area or make a thin component of a larger system quite rigid is handy.

Still doesn't really explain flaying a normal phone until it barely has a normal day's use with a totally fresh battery when you are still going to glue an entire baby spy satellite to one end of it; but some of the actual engineering is probably reusable.
The 'butterfly' keyboards, or the under-mouse charging port, by contrast, went nowhere. They tried and failed at a few iterations of keyboards that committed expensive suicide if you looked at them wrong; then just went back to allocating the extra mm or whatever once Jony was safely out of the picture; and it's not as though putting the port on the bottom rather than the front of the mouse involved any interesting capability development.

Whatever product manager thought that the 'air' would be a big seller deserves to feel bad; but the actual engineering team can probably feel OK about the odds that a future phone will look somewhat air-like if you were to remove the normally shaped case and larger battery.

Banning pornography is a key part of Project 2025, mind you. How that comes about is a bit up in the area, but it's coming. It's one of the bigger unfulfilled parts that Trump hasn't touched yet.

And the way individual states are doing things to make abortion illegal in all states, even in states without such laws.

It's all laid out in the book, everything that's happening, how it's happening is right there

lol uh you think backup companies only have your data only in one place? This would be like you thinking your favorite pizza place doesn't know what a tomato is

Go learn about raid or something