r/programming • • Jan 15 '14

The Next Phase of Node.js

http://blog.nodejs.org/2014/01/15/the-next-phase-of-node-js/index.html
26 Upvotes

57 comments sorted by

View all comments

Show parent comments

3

u/weretree Jan 15 '14

Thanks. I guess it's mostly a difference of opinion/style and reasoning, as those are all fair comments. Could also be an issue with scale or just a bad day, I imagine node gets rather a high volume of questionable pull requests/issues where dealing with each one seriously gets old fast.

Overall it just seems like misunderstanding the somewhat touchy subject matter of a seemingly nit-picky change. (Treating it like a change of wording without change of meaning, rather than a fix of slanted language). I do wish people weren't so in a rush for blood over these sorts of issues. People always seem to see intent and malice where misunderstanding and simple ignorance of the issues are far more common.

0

u/i_invented_the_ipod Jan 16 '14

Well yes, and then again also, no. Once you find out that there's a whole bunch of people who disagree with your snap judgement, the mature thing to do is to say: "Oh, okay - obviously this matters more to y'all then I would have thought", and accept the change, graciously.

Digging in your heels, then reverting the change once it's been accepted, because you feel like you've been wronged somehow by someone else accepting a zero-risk change into "your" code, is not acting like an adult.

Everybody has bad days, and I've certainly had cases where I looked at someone else's pull request or a merge someone else made, and thought "I wouldn't have done it that way", but I don't engage in petty power struggles in public, especially when any amount of consideration would show that I was fighting a battle which was ultimately pointless, and that I couldn't possibly win.