4 ms·
Most certainly opening the door to a diffetent kind of bugs. This mentally of tying bugs to a language demonstrates a very poor understanding of the issues them
by ordiel 5y ago
Most certainly opening the door to a diffetent kind of bugs. This mentally of tying bugs to a language demonstrates a very poor understanding of the issues themselves, and if anything a large impacting bug demonstrates wide adoption of an individual piece, most probably choosen due to its stability or ease of use.
Remember heartbleed?...
- staticassertion 5y ago> Most certainly opening the door to a diffetent kind of bugs. No? There's no law of conservation of bug class or something, you can eliminate bug classes without introducing a new one. > This mentally of tying bugs to a language demonstrates a very poor understanding of the issues themselves, No it doesn't. > and if anything a large impacting bug demonstrates wide adoption of an individual piece, most probably choosen due to its stability or ease of use. I don't think this has held true historically, and log4j is a good example of this (though there are many others). > Remember heartbleed?... A weird point to bring up since heartbleed was an out of bounds memory read.