Stopped reading at the graphic. None of those descriptions for dishes sound anything like what a developer would write. Just pure obscurantist nonsense. "Cow secretions" to refer to cheese? Really? Even though that's more ambiguous, wordier, less helpful, and less descriptive? The author tells on their own shoddy writing skills. A developer might be guilty of writing "Pizza - goat's milk mozarella, wood fire oven" instead of "Cheese pizza" but certainly not that nonsense.

It's a pretty good outcome, yeah. Kind of makes one wonder why copyright needs to be 70 years + life, when the overwhelming majority of sales are in the first year...

It's a signal whether you like it or not. Saying "well shucks anything could go out of business" is meaningless. What partners and customers want to know is the liklihood of that happening. Moreover, going out of business isn't the only risk to consider but also pivoting into another business entirely.

You can short without tail risk, e.g. buying puts.

There are no programs that will fully transpile Perl to not-Perl, because that would require parsing Perl.

A code converter that kindof-sortof-but-not-really transpiles (like Python's 2to3) would require a lot of debugging of ugly machine generated source code. Who wants to do that? Would probably be even harder than a full rewrite. (How many Python libraries were actually ported using 2to3?) Similar for using any translation an LLM might spit out.

So yes, by hand. And it's not obvious if a full rewrite of a complex library would be easier than porting its runtime to WASM, especially when said runtime has been ported to countless other systems already.