3 ms·
Thank you for clarifying this, it is the following excerpt that confused me since Scott Hammond referred to "users of Node.js" as "developers". > I was well aw
by r0naa 11y ago
Thank you for clarifying this, it is the following excerpt that confused me since Scott Hammond referred to "users of Node.js" as "developers".
> I was well aware of Node.js’ developer popularity and success — mainly because those who use and love Node.js also love to talk about it
I have a hard time imagining how different are the needs of the "strong developer community" and "node.js users". If anything they seem completely aligned. Node.js (and io.js) has done an amazing job taking into account community feedback.
I fail to see how more transparency, openness and empowerment for the developers "unbalance" the needs of both groups. The only "loser" in this whole open-governance thing seems to be Joyent.
In short, my feeling is that sentence could be reformulated as follow:
"While crucial, an open governance model by itself does not guarantee long-term success. We’ll need to balance the needs of the strong developer community with those of our shareholders"
Maybe I am a bit too cynical or harsh, please let me know if you disagree with me.
- rgbrenner 11y agoI agree with everything you wrote. However, users and developers of nodejs do have slightly different interests. I think Golang is a good example of this... the developers (mostly Google) want Golang to be small, less complex, etc (at the very least, it makes their job easier if they don't have to support certain features). But the users want generics, exceptions, and assertions (among other things). So there's this difference in point of view -- the developers have a certain vision of what Golang should be.. and the users just want to get their project (that happens to be implemented in Go) finished as quickly/efficiently as possible.