Except this is not about languages running on embedded platforms, this is about hosting a language inside an application, for providing e.g. scriptability of a GUI application.

In the US, speed limits are legally to be set after the 85th percentile of actual speeds. So if everyone is speeding, the speed limit should legally be changed such that at most 15% of drivers will be speeding at that stretch of road.

This kind of data might just as well be used to help determine areas where the speed limit is wrong.

I'm installing a new computer.
I know, I'll use Linux!
I'll use kernel series 2.2 because I remember that one from when I was a kid. Simple and proven. Great choice I just made!

I remember seeing this kind of notation in my grade school textbooks. (I'm from Denmark by the way.)
Though usually it'd be presented with otherwise marked fields, rather than parentheses, and accompanied by short instructions. In earlier grades accompanied by a drawing representing the kind of problem solving needed, instead of written instructions. Like this:

Fill in the blanks, so both sides are equal:
4 + 3 + 2 = ___ + 2

In later grades, regular equation notation was then introduced, substituting x and y for blanks to fill in. Then you'd get a question like this:

Find the value of x in each equation:
4 + 3 + 2 = x + 2
x = ___

My following argument might not work if you follow it through, but consider it anyway.

Every time you consume a plant, you might deny an animal a source of food or a space for living. What if you eating an apple caused a sparrow to die of hunger, who could otherwise have survived off that apple? In this way, consuming plants might also negatively affect animals.

Huh?

H.264 is not "closed source", it's an open standard with open source encoders (famous x264, everything points to it being the best quality encoder available anywhere) and decoders (libavcodec), it's just that a bazillion companies have patents that cover every corner of video coding. It might be "unfree", but it's certainly not "closed source" or "closed standard" or "proprietary".

Last time I had a 35mm film developed (which was late last year), apart from the negatives, I got digital prints of it. I didn't ask for it, but it's what I got. Naturally the negatives were developed chemically, as that's required, but after that most shops will scan the negatives and produce digital prints from that. And it isn't even cheap. Don't get me started on the price of getting low-resolution (about 5-6 MP JPEG) scans burned onto a CD, it's ridiculous.

So all that stuff about a "tunnel of light" is a lie? It's just infinite blue?

I want my money back.

What about that game "Chess" where you command an army to mercilessly slaughter an entire kingdom? If that isn't brutal I don't know what is.

This is a server-checks-client-security thing, not a Microsoft-checks-customer-setup thing. Refusing to work with known-broken software.

Maybe the reason nobody bothers reading documentation is that they have become used to it being poor to non-existent. It's not even worth looking for so when it does exist nobody bother with it because they assume it isn't there or isn't worth it.

But then what happens when 301Works dies?

File a bug against the application.