Comment by compiler-devel
2 hours ago
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?
The obvious answer is that LLMs are not quite the machine gods they're marketed as, innit.
I don't understand what you're saying.
Your presumption is that code is "cheap" because of LLMs. I am challenging the premise. Maintaining code in production for a product used by billions of people is not cheap, with or without LLMs. Perhaps your shitty disposable code that you write for yourself and never subject anyone else to is cheap, but if your code is in a large, complex codebase and has to actually work for everyone who uses it, not so much.
1 reply →
> what are the good reasons for dropping legacy code?
Reducing attack surface.
That is a good reason. Is XSLT known for security problems the same way that CGI was?