But he is right though. If Nintendo really wants it gone they’ll just pull a sony-bleem. As long as there is no real regulation for this stuff, there is not much you can do.

I think also showing real attempts at cybercrime would have a real liability aspect

I think it is more like “this error should NEVER EVER EVER EVER appear”. Then, as it is customary, it did.

But they kinda sorta do. It is not like Chromebooks are locked down like an iPhone. I had an old Samsung Chromebook, you could just turn off trusted boot with a flick of a switch (okay it did reset your device), and just run what you wanted. It’s just with arm based stuff running what you want is not trivial. You run what you can which is often nothing.

Weeell “bullshit” is easy to claim but not necessarily untrue. So with android phones this is definitely a problem. Industry wide firmware support for these ARM SOC-s are often ranging from not long enough, to fucking atrocious. You get basically two years of new drivers, and a security update maybe. The way LinageOS manages to support phones like the note 3, from like android 4, to 11, is basically creating manifests, that use drivers from newer, still supported, but “similar-ish” components. And the note 3 was a flagship device, easily the fastest phone of it’s generation. These Chromebooks, especially the ones schools can and do afford, are built to the penny. There is ultimately no point in pushing a software update to a device for a significant cost, that makes it so slow that no reasonable person would ever consider using it.

What is the solution to this? Hard to say. Not buying hardware so incredibly obsolete that it has to run an alternate OS, is a start. Maybe just use PC-s and deploy linux.