3 ms·
No, this is particularly bad in Ruby. Many languages, esp. compiled do not have the same issues.
by gedy 5y ago
No, this is particularly bad in Ruby. Many languages, esp. compiled do not have the same issues.
- chucke 5y agoJava and log4j would like a word with you.
- jorams 5y agoThe problem with log4j is that they didn't introduce a breaking change, allowing vulnerable functionality the maintainers already considered problematic to stick around.
- dagmx 5y agoWhat language would avoid the problem?
- Gigachad 5y agoThat’s often the case but for this particular issue, it could have happened in any language because it’s still returning the exact same type. Its an array of the same record type in both instances.
- emodendroket 5y agoUltimately this is more social than technical.