4 ms·
I don't see any problems with this. The devs also have to balance the weight of breaking current applications using their existing url parsing. It also doesn't
by zemaj 15y ago
I don't see any problems with this. The devs also have to balance the weight of breaking current applications using their existing url parsing. It also doesn't seem an unreasonable argument that users should expect node to carry on existing conventions from js in browsers. I'd make the same choice.
- IsaacSchlueter 15y agoI see that you also hate freedom. We should hang out.
- lysol 15y agoI 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.