compiler-devel

LLMs are only getting better and more competent, especially for code well-covered by tests. On such codebases it's definitely cheaper to maintain code with a LLM than by humans alone. I presume then that the XSLT implementation in Chrome is not well-tested.

That is a good reason. Is XSLT known for security problems the same way that CGI was?

I don't understand what you're saying.

In the age of LLMs I would expect that legacy code bet carried indefinitely. The LLMs will have it indefinitely in their training data, and with code "cheap" to produce now, what are the good reasons for dropping legacy code?

They'd be trading the seed constants for the timestamp constants, more annoying than cute honestly.

Will it be available for MariaDB, too?

Good points yet how others view the art doesn't affect my enjoyment nor practice of it. Like music, others can enjoy listening to a CD or play their own instrument; I don't care. Why allow others' style and practice influence how we enjoy programming?

I don't understand what's difficult about enjoying programming now that LLMs are everywhere. It's akin to musicians who still play their instruments despite having the ability to stream any music they'd like. Nothing's stopping them from playing their instrument. Why is programming any different?

Do you upgrade your computer when the major release goes out of support?

I always wait one year, upgrading to major release N-1 in August before N comes out in September. I made an exception last year and stayed on Sequoia. It will be August of next year before I consider Golden Gate.

Rosetta is still present in 27.

Nobody really cares about externalized costs. If they did, then cars, electricity, lithium batteries, etc wouldn't be as popular as they are.

Local first models like qwen 3.8 are surprisingly capable even on an M1 MacBook Pro with 32GB of RAM. SOTA is not the only game in town

Why? Does it bother you to see people using their own devices in the ways that they want?