So, on the minus side we've got people trying to game the system. On the more-minus side; the way they are trying to game the system suggests that peer review has, at least in part, been farmed out to chatbots because it's easier. Fantastic.

"A tandem charge the size of a solar system" isn't really the reassuring correction I was hoping for; to be honest.

Thankfully, you can sustain national greatness just by shouting belligerently about it; the idea that you actually need competence or execution is just a con; so this should have no side effects whatsoever.

Probably not great news that someone further up the Kardashev scale remains a fan of double tap strikes.

My suspicion is that they are probably in the clear. the USB PD spec includes 'vendor-defined messages'; both 'structured VDMs' that are standardized and 'unstructured VDMs' that are basically whatever the implementer feels like. This obviously doesn't prove that Nintendo are in full compliance with what the USB-IF really wants the USB trademarks applied to; but(along with the reports that it plays just fine with 3rd party chargers) it looks a lot more like a basically-compliant-minus-any-bugs-or-compatibility-hacks USB PD implementation that just doesn't mention DP alt mode unless it likes the unstructured VDM chatter. Dick move; but one you could do in full standards compliance.

Sounds like they are acting all pious over what is basically a workplace dispute over division of margins.

The outfits that do ransomware negotiations remain legal; because for some reason that's one area where nobody bats an eye at you doing business with transnational criminal syndicates; but they are basically just bagmen who take a cut of the deal for interacting with the disreputable ransomware guys for you. In this case, apparently one of the employees wanted a larger percentage of the cut than he was getting from his employer.

I suspect that what he did is some sort of crime in a way that what his employer does isn't; but it's the same business model; just with some disagreement over whether that guy gets a percentage directly as well or whether just the company does.

It's a shame IMAX isn't that advanced.

I've got 800w sound system in something the size of an NES cartridge. I run three of those for surround sound off my computer.

If only sound codecs allowed for vertical positioning of audio. I'd add a fourth amp and roll 8.1 out the corners of the room.

Eberhart seems like he may be falling for the hype himself. He says "What's happening now isn't innovation; it's aspiration masquerading as disruption..."; but fails to note the fairly profound differences in results between the orbital delivery guys and the moonshot guys; and how neatly that maps onto what is aspiration and what isn't.

Putting satellites into orbit is kind of mundane at this point, too common, too obviously useful; but it's sufficiently obviously useful that more or less anyone with nation-state aspirations wants to at least have a program that executes; and civilian and day-to-day operations want someone who executes but cheaper. And that exists. Going to the moon is cool, and it's a nice prestige project for when the gerontocracy needs to show that they still have it just like when they showed the commies what for; but it's unclear exactly what the point is or the stakes are beyond that. The customer presumably would like to actually land something on the moon, at some point, just to say that they did; but what they are buying is mostly aspiration on the cheap: We get to say that we have a lunar program for way less than Apollo money, you do some open-ended tinkering, honor satisfied.

He can talk about 'accountability'; but it seems like it's a fundamentally hard problem to actually sustain a lie about how serious you are, at an institutional level, in the long term. It's not like do-or-die projects are free of losers(especially because circumstances have a nasty habit of thrusting them on people whether they like it or not; rather than giving them the luxury of choosing whether or not to take on those stakes); but they tend to be animated by a sense of genuine urgency. Stuff that is, fundamentally, kind of optional, by contrast, tends to reflect that in bulk. Timmy Rockets may be genuinely more passionate about stir-welding than you've ever been about anything; but, like is cousin who is really passionate social worker, will soon discover that going to the moon and fighting poverty are open-ended projects we do because they sound nice, not because anyone who matters is actually committing to a deadline.

I can think of some niche cases where this might be useful(mostly HHD/SSD wear data; though bad actors have been able to tamper with those values without much difficulty); but overall this seems like throwing an awful lot of identifying data and a whole 'trust me bro' shadow subsystem at a problem that the data is unlikely to actually help all that much with.

This will be very good at fretting if the refurbisher swapped out RAM or mass storage; but it's not like onboard diagnostics are all that good at picking up the difference between a machine that has had a fairly hard life and now has somewhat dodgy ports and a bit of uncomfortable flex vs. one that sat on a dock most of its life and got unplugged only a handful of times; any any issue that the embedded diagnostics can pick up can also be picked up without any special recordkeeping by just running the diagnostics when you receive the device and verifying that it doesn't throw any errors out of the box.

If you've already got the trust me bro shadow subsystem I assume it's relatively cheap to propose having it keep more records; but I'm not really convinced of how much value is being added.

Is there some problem particular to human DNA that they are looking to solve; or is this just an extension of the ongoing work on DNA synthesis(if you are OK with relatively short segments that has come down to being something you can just order, not nearly as exotic as it once was) but being hyped because there's some human cell genetic engineering at the end; rather than just meeting more aggressive targets for achievable lengths?

You say 'involuntary psych hold'; I say 'MAU'!

Diminished maybe, but not all that much.

I think we can reasonably assume that if there's a huge blackout, it won't last forever. A lot of smart people will work hard on getting things up and running again. A few years ago in the USA it lasted for a bit longer, what was it, a week or two? Recently in Spain it lasted a few days. But all those power stations and power grid operators don't just shrug and go home. So getting through those days is probably all it takes for any reasonably realistic scenario.

And you can build things up piecewise. I've got my solar now. The next thing will be a battery. Once I have that, I can think about an electric car.

Rollover protection is part of why A pillars are so much thicker now. The first time I drove one of them, it amazed me how much I had to keep moving my head just to keep track of what was across the intersection.

That's what API's are for. You can run amuk all you want on the outside, then you ask the kernel for information or to take action by calling an API. There the system's code runs, which we expect will already be carefully tested and validated before it momentarily elevates privileges to do the work. If you made a stupid request, it gets ignored and control returned to you instead of crashing the kernel space. Then do whatever stupid things you like after the API return. At that point the system doesn't really care if you blow up because life will go on without you.

API's allow for "compartmentalization" of execution, and keep the dirty little fingers of random developers out of sensitive areas.

"why was it in the kernel to begin with?"

kernel changes should be tightly controlled. Not pushed out anytime a vendor has a (poorly tested) update they want to blast to the masses.

Keep outside party code out of the kernel !