nytpu

Because attaching a debugger to the Linux Kernel is so convenient and easy :P

But yeah, I was just being lazy and dumb. I solved it within ten minutes of someone saying "why don't you just go through the binfmt_elf code?" A debugger would've probably been more tedious than reading the relevant code directly, but would've been just as effective.

Almost like those existing env vars made it clear that they were mistakes that make behavior inconsistent (especially libcurl) and they want to avoid repeating it with additional env vars. Having almost contributed to Curl before, they repeatedly note for contributors that just because old code does something questionable doesn't mean your new code is allowed to do it—if anything, you're just highlighting the questionable piece of old code as being important for them to rewrite soon (of course they can't remove the current env vars for compatibility reasons).

And the article specifically notes that the current solution doesn't work, but it requires discussion on what the best solution is instead of just taking the literal first solution suggested by someone.

I recommend reading the Telecommunications Act of 1996, which required all incumbent telephone companies to allow any other company to install equipment in their central offices and buy rights to already laid phone lines at a fixed rate, where all the expense of actually building and laying everything laid entirely with the owner of the central office.

Turns out that (fairly applied) antitrust doesn't care how much it money it costs an incumbent company to begin allowing competitors

Except they were originally "Apple Computers" until they slowly gained enough recognition to rebrand to "Apple," plus that was in 1984, there wasn't an oversatuated market of other computer brands also called "Apple," unlike "Element" which has tons of existing tech-related and non–tech-related overlap and is generic on top of it.