>If a child answers a phone, and someone on the other end tells them to harm themselves, the phone wouldn't be considered the risk.
You mean that the person on the other end of the phone would be considered the risk, right?
There is no person inside of an Amazon Echo. Your question does not go to a call center where someone decides how to answer it. There are no human beings involved, it's all automated.
I use NoScript to block unnecessary JavaScript on websites, so I'm used to pages failing to load. But this article's nice scrolling 3D animation works fine on mobile with only the 'economist.com' domain allowed to run JS.
Good take - defining a "low-level language" feels like trying to define a "cold temperature". It's all very relative.
We could say that a temperature is "freezing" if it is under 0C, and "boiling" if it is over 100C. But it's hard to nail down "cold" or "warm", as any group sharing a thermostat will tell you.
You can easily place arbitrary assembly commands or memory values in C code. Plenty of embedded codebases are littered with asm blocks in performance-critical areas. It's hard to see it as a high-level language in the age of javascript/python, but maybe the overton window has shifted.
Seems straightforward, right?