It doesn't say they got arrested, but apparently the person in question didn't turn off the Bluetooth device when asked to. Ignoring or disobeying the instructions of flight attendants is a federal offense.

There were movies but they weren't very good.

From the 1700s, Magic lanterns had moving parts, and there were magic lantern shows.

The Phenakistoscope was a kind of simple movie, and was projected on a stage by the mid 1800s.

The Zoopraxiscope was used with a projector from 1880 in public lectures. It is of interest because it used actual photographs.

The Kinetoscope was a little later, by 1892.

If your company relies on "oral tradition" to maintain documentation, then your company may not survive with or without AI.

"Oral tradition" is the engineering process of knowledge being lost. That is to say it's not engineering.

Maybe he should have made a backup earlier.

What? Where did you get that from? The Neo uses the Apple A18 Pro SoC. It was widely reported (here on Slashdot even) that Apple was using binned iPhone chips for the first batches of Neos, with the defective cores deactivated.

It used to be managers demanding some kind of design document before implementation took off. That means nice pictures they can show to middle management to prove that we're actually thinking and not monkeying around with code until we get a working ball of spaghetti we can ship to production so it can run out of memory and fall over. This documentation has boxes with arrows pointing to the obvious integrations and dependencies needed to make the thing work, and the system itself is just a box with in that system. That's not BAD for someone to look at who has no idea what the system is. Sure, it's a "architecture" diagram or a high-level design. Hand-building one of these in whatever tool you have (some terrible Confluence plugin, Figma, etc) is time consuming and has little to do with actual architecture. You're too lazy to include all of the important parts - NGINX routing, containers, container hypervisors, load balancers, keystores, all the infra that it actually runs on is implied here. You include a little database icon and draw an arrow to that. Cute!
The actually useful documentation is now in the codebase in markdown files. These are both for code agents (lets be honest, it's just Claude) and humans. They're human readable. They're also bot-readable, because bots build a memory model using the markdown formatted text, or so I'm led to believe.
You can have sequence diagrams in ASCII or Mermaid format generated while the code is being generated. Just make sure to tell the code agent to update any documentation as a task at the end of any change. Text generation is cheap, code documentation is just text or markup or more code (mermaid is code-like) and code itself is text, and so is readable. Claude likes to add wayyyy too many verbose comments, and tells you every little detail of what the code is doing.
If there is high turnover at software jobs, its because management hates software engineers. If there's no documentation for the next person to look at, then someone's not doing a good job of keeping live documentation in the codebase.

I've inherited lots of completely crap projects from devs who just couldn't be bother or didn't know any better, mostly the latter. All the documentation/intent in the world isn't going to fix that shit. It won't make you popular to say this is garbage and no amount of wishing otherwise is going to make it production-ready. But you do have to say that, then throw it into production and say yep, it ran out of memory and crashed predictably. Now either tell the stake-holders (wooden stakes?) we've abandon that plan or set the timeline back a few months to rewrite it.

Clearly we're all terrified now, so I'd say their job is done.

They can just sit back and relax and watch us all live in fear.

"Jensen Huang positions RTX Spark as a complete reinvention of the PC"
He's comparing this to the leap between rotary phones and cell phones. Or is it flip phones and smart phones? I can't tell.
They look exactly like the MacBook Pro I'm typing on right now.
They're touting the fact that they had to rewrite the Windows kernel scheduler for the RTX chip.
Copilot, in all its forms, stinks. It's not the model's fault (use any model really), it's the tool implementation itself.
This is not the first laptop to include tensor cores, so again it's not a reinvention of the PC.
IDK maybe it is. Maybe Jensen is not full of hyperbole. Seems unlikely though.

Maybe they need an invitation to help them feel special so they forget the CLOUD act exists.

No company outside the US should do business with a US company if they care about their data sovereignty.

Is this really a top performing game device, or just a thin client to sell cloud SAAS crap? I'm not always attached to the internet and I'm not interested in renting my compute.

AMD graphics are stable if you use the open source drivers, but if you need their closed drivers for whatever reason (eg opencl) then they are extremely unstable and much worse than nvidia.

Of course if you're going to arm then apple is currently about the best option.

This is what happens when you don't consider all the edge cases.

The edge cases break the law.

Creator: DO NOT USE THIS IF YOU ARE AI
AI: [uses it, takes damage]

I fail to see how using it against the wishes of the creator makes the creator liable even though they explicitly made it so that if you DID use it, you took damage.

And they'll have to pay more for it than . . . nothing for another rehash of a franchise they already own.

if you downloaded the program without paying for it, without authorization?

Gonna bet most boiler plate licenses absolve the creator of literally every bit of damage.