One major difference, assuming you've got full platform support(should be the case on any server or workstation that isn't an utter joke; but can be a problem with some desktop boards that 'support' ECC in the sense that AMD didn't laser it off the way Intel does; but don't really care); is that ECC RAM can (and should) report even correctable errors; so you get considerably more warning than you do with non-ECC RAM.

If you pay no attention to error reports ECC or non-ECC are both rolling the dice; though ECC has better odds; but 'proper' ECC and Linux-EDAC support will allow you to keep an eye on worrisome events(normally with something like rasdaemon, not sure what other options and preferences there are in terms of aggregating the kernel-provided data) and, unless the RAM fails particularly dramatically and thoroughly, will give you much better odds of knowing that you have a hardware problem while that problem is still at correctable levels; so you can take appropriate action(either replacement, or on the really fancy server systems, some 'chipkill'-like arrangement where the specific piece of DRAM that is failing gets cut out of use when deeemed unreliable without having to bring the system down.

Sometimes you'd get a BSOD that was a fairly clear call to action; when the error called out something recognizable as the name of part of a driver; but that is mostly just a special case of the "did you change any hardware or update any drivers recently?" troubleshooting steps that people have been doing more or less blind since forever; admittedly slightly more helpful in cases where as far as you know the answer to those questions is 'no'; but windows update did slip you a driver update; or a change in OS behavior means that a driver that used to work is now troublesome.

Realistically, as long as the OS provides suitable support for being configured to collect actual crash dump material if you want it; it's hard to object too strongly to the idea that just rebooting fairly quickly is probably the better choice vs. trying to make the BSOD a genuinely useful debugging resource; especially given how rare it is for the person with useful debugging ability to happen to be at the console at the time of crash(rather than just an end user who is ill equipped to make sense of it; or a system that mostly does server stuff, quite likely not on actual physical hardware, where nobody has even touched the physical console in months or years; and it's more or less entirely useless to display a message there; rather than rebooting and hoping that things come up enough that management software can grab the dump files; or giving up and leaving the system in EMS so that someone can attach to that console.

Not that suprising with a software person.

With ECC, memory will go "bad" too, just a bit later. If you buy good quality memory, it will be fine for far longer than the time you are going to use it. Bad memory will overwhelm ECC way before that time.

AGI? Hahaha, no. The fake just gets more complex.

So now it can "confess" to being an incompetent asshole. Already more than the typical CEO can do, but still unusable.

... For our elected officials, that is.

The article doesn't say anything about heat absorption. I wonder if the fabric traps most of the heat associated with the light as well? I'm assuming it would.

Well, the energy absorbed by the fabric has to go somewhere - typically it's converted to heat. Granted, it could be highly reflective elsewhere in the spectrum - like it could take that energy and convert it to IR light so it doesn't get hot.

The bigger issue is physical releases. Netflix has a policy of no physical releases of their content. It's why many directors have stopped working for Netflix - they don't want to see their work "locked up" and unable to be enjoyed by people without a subscription. Maybe the odd director can enjoy a theatrical release but only because it's required for award consideration.

Also means that no movie is static and can be edited freely, like Amazon has with the James Bond movies. (Admittedly they are a product of their time, and if you didn't take that to account, they play completely differently now without the historical context. But still offensive or not, it's needed to study the historical context of the movie, not some cleaned up version that you can only get on physical media).

Long ago when Quicktime was dying because Apple abandoned it in the 2000s; the developer list had an email asking opinions about open sourcing quicktime. Apple should have open sourced most of it. MKV didn't need to happen. I certainly liked the ability to have reference movies that just worked and took no space.

MKV did need to happen. MKV is a free and open container format, made in a way that ensures it tramples on no one's rights (e.g., the lack of FourCC codes for identifiers).

MOV is still wildly popular in industry, and subsets of it are part of the MPEG4 standard - the MP4 file format is a subset (basically limiting what an MP4 file can contain since it's only really for h.264 video and a few audio formats).

I especially like their fries and their salad bowls.

The Trump adminstration has released a video of how these vehicles might be used in America:

https://www.youtube.com/watch?...

Well, not if you include females.

You ask a stupid question. Try harder.

Nonsense. But you nicely show the stupidity of the average person here.

First, obviously a self-driving car comes with accountability. It just sits in a different place. And second, most humans cannot adapt to unusual situations either.

The bottom line is that self-driving cars already kill less people per distance driven than regular cars or are close to it. But I guess people like you are fine with people dying just so long you have not adjust to anything new.

Trump wanting something small and cheap? That must be a first in his life.