This still happens all the time, take npm-It's hard to describe well, but I hope people will try Go (or similar alternative), you'll really see how much more robust it is. addHeader() in because no one in core believed in a progressive API, they didn't use node in real-world applications to see the need. I'm not trying to screw them over but someone has to be honest. Many of these same people make money from consultation, where it's advantageous to have a broken system.

Having broken concepts is one thing, but resisting change when they're obviously broken is not a good thing. Also plenty of people make a living/name from Node, of course they're more likely to praise it than to be honest about its faults, I'm definitely a minority in that respect. I'm definitely not the only one writing large systems, but I think the tolerance level varies per developer. It has always bothered me that people would advocate such broken systems (streams etc) when real-world alternatives were better even before now, even C has a much better example of what a stream should be. If you follow me on twitter you probably see me complain about it in various ways all the time, it's not that I'm bored with it, node's problems are real and some people just seem to ignore them, or maybe just deal with them because they know backwards compat can't be broken immediately. Five years of working with someone will do that to you. I think the issue is we've been slowly accepting that the node is the right way to do things. It's so easy to get caught up in the details but if you don't step back and use your own product you're screwed! I think the main problem is often people working on the depths of some system forget to really use it.

That is if the core people can admit that it's not great to work with :) I'm not saying those are due to terrible engineering or anything, but they were choices that were made and Node is stuck with them for the foreseeable future until breaking changes can be made. Node has many design flaws down to its very roots. It went even better than I had hoped, and is much less frail. I decided that if I could do it in a week, and if it went well that I would ditch node. Like I mentioned in my post, I decided to rewrite an application that I had been working on for the last month with Go. The thing that is enjoyable Go is that it IS production ready, if I could say the same about node I would still be using it. Not at all, my claims of node not being production ready are 100% legit, and based on real-world applications.

Sync breeze enterprise 10.0.28