Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Drop-In Replacement for Memcached. Parent comment
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.
There are no comments on this comment yet.
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.