Enterprise Java developers are scared to face the underlying human and cultural factors that led to such a massively boneheaded security vulnerability being possible.
Ahaha. Unfortunately they are not. As in they don't care enough to fear or face it.
Enterprise Java developers are ex-CORBA/DCOM/Smalltalk/Common Lisp developers actually, now busy building scalable Kubernetes clusters with Go to process CSV files with proper failover mechanisms.
LOL this one got an audible chuckle out of me
Real Enterprise Java developer are probably still using log4j 1.x so are unaffected by the bug.