While I feel sorry for the people involved, Oracle as a company richly deserves this, for reasons far too familiar to everyone here. This is a come-uppance that has been waiting to happen for decades.
I'm not sure this is the come-uppance you've been waiting for. Oracle still has a larger market cap than at any point in history except the last ~2 years.
Technically, they could do a whole bunch of things, including doing multihop routing via other connected televisions or insecure WiFi networks. There's no evidence that they do this, as far as I know, but also no reason why they couldn't do this in the future if they wanted to.
It would seem relatively easy to eliminate this sort of infinite loop by ensuring that all loops are finite, function call depth limited and so on. It isn't a case where you hit the halting problem; the halting problem applies to general programs, not programs deliberately constructed out of parts with finite and calculable limits to runtime - no building the Ackermann function for example, as it contains a recursive loop. With the resources available to Apple, they really have no excuse.
Amusingly, some of this is technically already happening. The shaders pass through downstream compilers that complain if they see what they determine to be a no-op infinite loop. To prove to the compilers that the loop terminates, most WebGPU implementations inject a u64 counter (technically a vec2<u32>) that counts down from u64:MAX and terminates the loop once it reaches 0. But that's such a large amount to count that the WindowServer is long gone. Fun discussion on this PR for wgpu, a Rust implementation of WebGPU: https://github.com/gfx-rs/wgpu/issues/6572
Well this is easy to detect and kind of intentionally so, but the broader issue is quite a bit harder. Replace "infinite loop" with some very difficult program that simply takes 30+ seconds to finish and you're back to the same problem.
It doesn't even need to be computationally difficult, you can also slam the memory bus with "far away" fetches that are randomly distributed, ensuring each fetch doesn't share a cache line with any surrounding fetches. There are popular UX effects with basically this workload, even, that's a naive implementation of a large radius gaussian blur basically...
With respect to tire pollution, buses are far less bad than cars. Providing a bus is not nearly empty, while the per-vehicle pollution is worse than a car, it's per-passenger pollution is much less.
If only it did. AI is designed to do what you tell it to, and that mostly works. But in the general case, AI does what it does, with no real guarantee of anything.
LLMs seem to have been fine-tuned to use metaphors, presumably because they read like vivid creative writing. The over-use of metaphor in LLM-produced text is exhausting.
Should chips like the Jetson Orin module be regarded as dual-use technologies? Or have similarly powerful embedded processors now become widely enough available that it isn't worth making the distinction any more?
reply