> That's how it happens: a tiny little change flings the door wide open. Someone solves their own local problem and misses the bigger picture. Just in case any

> That's how it happens: a tiny little change flings the door wide open. Someone solves their own local problem and misses the bigger picture. Just in case anyone missed it: that's pretty much exactly the same thing that happened with the recent Log4Shell disaster. Someone wanted to have a config value from JNDI in their logs and thought it would be cool to have log4j's string interpolation support that directly, found that it was easy to implement, and submitted a patch, which was accepted without any discussion.