Pitting a modern, ultra-broody Batman against a Joker who genuinely just wants to engage in Silver Age shenanigans for no other reason than to piss Batman off (despite the fact that this Joker is established as a murderer already) would be super fun.
Bonus points if Batman could’ve avoided most of the events of the movie by taking himself slightly less seriously.
Processor architectures maybe. They put Rust into Debian and it’s so bad that now e.g. amd64 is ruined forever for any OS and won’t see any new processors in the future. We’ll have to move to a different architecture. I didn’t watch the video since I treasure my brain cells too much but that’s what I choose to read into it.
(A more reasonable reading is that Debian now ships a kernel that includes Rust code and coincidentally has also dropped builds for several obscure architectures but I do not feel obliged to assume reason with a title and thumbnail like that.)
Pushing to prod without review and breaking the running application is a resume-generating event in many companies. In many others it’s not even possible because of programmatically enforced policies.
If your company’s response is not to prevent or dissuade it but to have other people work overtime to fix the mess then that’s a major management fail.
Try to educate your boss about best practices. This incident should give your arguments some more weight.
Deployment to prod should not be something a developer can do by themselves; a proper CI/CD system can be configured so that prod can only be deployed to by people with an appropriate role (product owners or lead devs if your company doesn’t have POs).
If you don’t have such a system, make it an explicit policy: Only Steve the lead dev (or someone specifically appointed by him while he’s absent) can push to prod; if anyone else does it they get invited to an uncomfortable meeting with Steve. If they do it again the meeting will be with HR.
But seriously, you should lobby for a proper CI/CD system (if none is present) and for the system to be configured so that a) you can’t merge to the main branch without a code review and b) deploying to prod only works from main and with explicit approval by a PO/lead dev. That should stop most of the shenanigans.
Until you update your EFI and have forgotten all about the fact that non-Windows EFI boot images need to be registered with the Secure Boot key store even if Secure Boot is off. And that the key store is wiped when updating the EFI.
And then you spend an entire afternoon trying to find out why your Linux boot every isn’t even recognized by the EFI anymore. Fun.
Eh. Admittedly, my experience with non-rolling distros is old, but I’d rather take “something minor breaks every couple weeks” over “I tried upgrading the system and now I can’t even get working shell commands if I chroot over from a live USB”.
Admittedly, that was when I tried upgrading to Fedora Core 5 (or was it upgrading from there?), so ancient history.
Unless other situations where the established technology wins due to inertia, sodium ion batteries have two benefits that make them interesting regardless:
Firstly, they are safer. A punctured sodium ion battery doesn’t catch fire, which massively simplifies safety design. That makes them very attractive for certain scenarios, especially ones where density is a secondary concern. That in turn means they get further development money instead of withering on the vine.
Secondly, they require fewer hard-to-obtain materials, which makes them attractive from a strategic perspective. This one should be less important than the safety factor but it’s also relevant.
I’m pretty sure we’ll actually see wet sodium cells in the wild if they are actually practical. Sodium ion tech is already being commercialized and if this brings it within the same ballpark as lithium ion then it becomes a very interesting choice for vehicles due to instant crash safety gains.
You can see the Rust they added to the kernel.
I got it as soon as I got a GPU that could comfortably run it… because it was bundled with said GPU. I did activate the key but never bothered to actually install it. Maybe later in case the handful of modders actually make something cool in there.
I was kinda interested before launch, hoping that this would be the game to finally force them to meaningfully overhaul the engine they’ve been carrying around since Morrowind (with some bugs dating back to then). Of course it wasn’t and of course they didn’t.