3 ms·
Doesn't this tell a lot about how much (unit) testing is undergoing in Java-land? If a Ruby VM were to change its behaviour so to cause crashes, dozens of proj
by gioele 15y ago
Doesn't this tell a lot about how much (unit) testing is undergoing in Java-land?
If a Ruby VM were to change its behaviour so to cause crashes, dozens of project will start to see red in one or two test cases. From that, it is easy to pin down the problem to 10 lines of code and report it upstream. In Java-land (and, sadly, many other lands) applications suddenly crash and nobody knows why.
- smackfu 15y agoWell we're not talking simple methods that are breaking. It's generally UI stuff that is under specified or places where the Oracle JVM uses native code, etc.
- tomjen3 15y agoNot all problems in computers are evidence of no unit-testing. In this case it is simply that a bunch of groups (especially gcj but properly also icedtea) published half-completed implementations of a standard and declared it was good enough to use because it didn't come from Sun.