"Perchlorate is toxic to people only in the sense that it can disrupt the production of thyroid hormone, an important growth hormone needed by babies in the womb for normal development." (from https://www.scientificamerican.com/article/perchlorate-life-...)

Lots of people have this condition without perchlorate after all and it's just simple meds to fix it.

And of course it's easy to think of lots of apps that heavily use those or another form of GC.

Could indeed be a useful exercise to benchmark the cost.

This would still be more limied, since many vulnerabilities are apparent only when you consider more context than one function to discover the vulnerability. I think there were those kinds of vulnerabilities in the published materials. So maybe the Aisle case is also picking the low hanging fruit in this respect.

But in substance, if you have several subnets, then using ULA may make sense depending on what you're trying to do. However most home networks don't subnet.

This is not the case for the addresses returned. See eg https://www.rfc-editor.org/rfc/rfc6762

6.2. Responding to Address Queries

   When a Multicast DNS responder sends a Multicast DNS response message
   containing its own address records, it MUST include all addresses
   that are valid on the interface on which it is sending the message,
   and MUST NOT include addresses that are not valid on that interface
   (such as addresses that may be configured on the host's other
   interfaces).  For example, if an interface has both an IPv6 link-
   local and an IPv6 routable address, both should be included in the
   response message so that queriers receive both and can make their own
   choice about which to use.  This allows a querier that only has an
   IPv6 link-local address to connect to the link-local address, and a
   different querier that has an IPv6 routable address to connect to the
   IPv6 routable address instead.

"Gabriel argued that early Unix and C, developed by Bell Labs, are examples of the worse-is-better design approach." Whereas vibe-coding is not reviewing what code goes in, just judging it by whether it seems to work or not. I guess a common factor would be willingness to compromise on soundness.

Protesting the term is, I'd wager, motivated by something like: it sounds innocuous to nontechnical people and obscures what's really going on.

> is open gl the non web version of web gl? or are they completely different?

The current version of WebGL, WebGL 2, is like OpenGL ES 3.0.

This is the interesting part. What kind of UI or other mechanisms would help here? There's no silver bullet for detecting and crashing on "something bad". The adversary can test against your sandbox as well.

I'd wager in a alternate universe where Wayland didn't have all the mindshare, Steam Deck would still be a product (unless some butterfly effect nixed it).