Re:Third High Severity CVE in Log4j Is Published
by ashtonkem on Sunday December 19, 2021 @10:13PM
(#29621189)
It's a bit of conservative culture, and a bit the result of success. There is a lot of Java code out there, and a lot of it is quite old. Finding and replacing every single instance of log4j out there would be a lot of work, and before this incident of relatively low benefit to everyone involved.
It's Java; the ecosystem is, politely, rather conservative and slow moving.