Re:Log4j: Between a rock and a hard place
by vinceguidry on Sunday December 12, 2021 @01:09PM
(#29531961)
> You're blaming an ecosystem for being unstable, which while I agree, ultimately has nothing to do with the lang itself.
It has everything to do with the language. With no built-in module support (until recently!) and a weak type system, it's virtually impossible for Javascript to get anywhere near the stability of Java.
> makes you're entire point very ironic.
OP made an observation that we're having this conversation for this particular Java vuln but Javascript breakage never provokes anything like this. I don't understand where the ironing is. <insert-Princess-Bride-gif>
Well yeah. It never claimed to have one.
You're blaming an ecosystem for being unstable, which while I agree, ultimately has nothing to do with the lang itself.
The fact we're discussing the fact one of the most simple libs of a language (logging to the console) can have such a widely felt exploit in such a 'mature' lang makes you're entire point very ironic.