I prefer that bugs get fixed when found. In my experience the Java way is 'oh, a...

mbell on Jan 1, 2015 | parent | context | favorite | on: MRI Developers Don't Use RubySpec and It's Hurting...

I prefer that bugs get fixed when found.

In my experience the Java way is 'oh, a bug, well, that's a bug defined in the spec so we can't fix it now, we'll make a note for the next version'...5 years pass.

The 'I don't want to touch working code' argument is another strange Javaism. If you expect your code to not rot your going to have to constantly maintain it anyway.

gear54rus on Jan 1, 2015 [–]

And sadly, it seems the same with JS. Year 2015:

  x = null;
  typeof x; //object
  x.a = 1;  //TypeError: x is null