I wouldn't make the same choice. Node is young enough that a minor change like this with proper warning to developers should be expected. If Node's version was

I wouldn't make the same choice. Node is young enough that a minor change like this with proper warning to developers should be expected. If Node's version was >1.0.0 I'd expect this bug to have been fixed years ago. It's completely subjective, but it gives further credence to opinions that Node is a toy. Not that I agree with it.