If someone causes financial loss by posting LLM text and is then found to have removed a watermark. Everything in civil law is implicitly inside a if(someone harmed && they sue you) {} block.
Scrolling down to reach the HTML keyboard, and then back up to see what I typed, is obnoxious. I have a keyboard installed, and it doesn't pop up because something on the page tells my browser it doesn't need to. Was this vibecoded?
I remember a case from Germany where an elderly lady chose to speed down the pedestrian sidewalk and bike lane and mowed down a whole family in central Berlin. 4 deaths I think, no charges, no suspension.
Consider a kernel that boots on several different machines with different capabilities. Patching the call instructions at init time, to point to either one version or another of a frequently used function, saves time.
It's not like the standards have official legal status. You're allowed to develop your own mobile network technology that isn't 5G and doesn't infringe any patents - the government isn't saying that only 5G can be 5G, so it's a theoretically fair playing ground.
Can the US government prove they did (a headline is not proof)? Can Qualcomm even enforce patents against Huawei anyway, or vice versa? Maybe they're just handshake-agreeing on the status quo.
I actually made a Linux distribution that relies on this being your latest comment, since you didn't say this wouldn't always be your latest comment. If you post any newer ones, it will break.
That depends how far in advance of running the code you're modifying it. You could see a JIT compiler as an extreme type of SMC. Or a Monero miner - its hashing algorithm relies on running randomly generated programs.
It's possible to write safe code in C or C++ but it's extremely difficult to read existing code and prove it's safe, without using as much effort as it takes to write it in the first place. This includes the code you wrote last month whose surrounding code has changed. And you have to be right every time while the attacker only needs you to be wrong once. The problem is not writing the code, it is continually verifying it.