Those types of fishing expeditions run counter to the basic principle of "presumed innocent until proven guilty", at least in my mind. So I'm not crying over this news.

So, in order to protect against possible military applications(known for their cost-sensitivity...); we are making the sale legal as long as El Presidente gets his cut? That's in character, sure; but what's the paper-thin excuse for that being a cogent policy idea?

Worked for NASA... *yawn*. Holds 140 patents... yeah, so what?

But this dude also invented the Super Soaker - now THAT's legit guy cred!

That seems like a ludicrously specious argument. Bash is pretty much always available on any of these platforms - and exactly how "up-to-date" would it need to be to run a script?

Besides, you know what's not available on pretty much any brand new system? Homebrew.

It made me think of an old Monty Python skit - although I mis-remembered the "sensible" party, originally thinking they'd called it "serious".

Bookkeeping?

I mean, both Mac App Store packages and Flatpaks are already self-contained... so there's no dependency management you have to think about with those "apps". And WSL already supports numerous Linux distros, each of which already has its own package manager (e.g. dnf, apt).

If I'd known ahead of time that it was gonna take me so long to find my checkbook, I might've done that! But I do that for bills - most of them are electronic transfers, but for a couple the bank actually mails a check. It's certainly easier.

"A hypochondriac and his money are soon parted."

I actually had to write a paper check recently. Took me 30 minutes to find my darn checkbook.

No, it would piss off a lot of the other passengers - even though it is legal behavior.

Talk to someone who does street photography about their confrontations sometime.

I only knew two people who wore Google Glasses, and honestly - they tended to frequently be assholes even before they got the glasses. The addition of the Google Glasses just exacerbated their personality issues.

Members of the current administration will certainly talk about anti-competitiveness, along with a copious amount of Trump spewing random unrelated crap when he gets asked about the merger - but then Netflix will funnel money to Trump in some manner and the deal will get done.

Netflix might buy into the ballroom, it might promise to develop "Trump: The Making of a Beloved Modern King", or money will quietly flow directly into the Trump family's pockets. One way or the other, this is going to be allowed to happen.

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.

I especially like their fries and their salad bowls.