Lots of ideas are patented, especially by large companies. Some ideas are pursued by the company themselves, while others sit in the patent war chest to (maybe) generate passive income and help with future litigation. Very occasionally they are used for prevention.
Regardless, such a system would be a reason for many people to avoid buying a particular car or brand of car.
A nanotube garrote would be the talk of the town.
What filesystem are you using?
My Samsung S90C OLED is pretty good. I spent a lot of time researching TVs and user reviews before I bought it though, and an LG OLED also made the shortlist.
It is possible to wrap something like python into a single file, which is extracted (using standard shell tools) into a tmpdir at runtime.
You might also consider languages that can compile to static binaries - something like nim (python like syntax), although you could also make use of nimscript. Imagine nimscript as your own extensible interpreter.
Similarly, golang has some extensible scripting languages like https://github.com/traefik/yaegi - go has the advantage of easy cross compiling if you need to support different machine architectures.
https://www.bbc.com/news/articles/crlr8gp813ko seems to have a good explanation. In short, it's complicated, and the IOC drew their lines.
Someone who lies is a liar. I lie unintentionally all too often, despite my best efforts not to (aside from some leg pulling.) Some people can't seem to help lying, and some others do it quite intentionally. We humans aren't very reliable or trustworthy, but we muddle on anyway, and we're not that bad, mostly.
Amd o stoll jsve pne tp thos dau!
Not much, although it's not strictly necessary for IPv6. But not much is pure IPv6 yet. Perhaps 2025 is the year of IPv6!
Lots of good advice here. I'll add that you could develop an understanding of IP networking and how it works on Linux, network interfaces, with containers, with iptables as well as stateful and stateless firewalls, CIDRs and basic routing, IP protocols and some common protocols like DNS and HTTP. This used to be pretty common knowledge in applicants 15 years ago, but very few have it today I find. DHCP and PXE boot is fun to learn too, and is still common in datacenters.
It is pretty easy to imagine separate streams of updates that affect each other negatively.
CrowdStrike does its own 0-day updates, Microsoft does its own 0-day updates. There is probably limited if any testing at that critical intersection.
If Microsoft 100% controlled the release stream, otoh, there'd be a much better chance to have caught it. The responsibility would probably lie with MS in such a case.
(edit: not saying that this is what happened, hence the conditionals)