3 ms·

As far as I can tell, nothing is going on, except the typical OSS drama. Frankly, I don't care who "owns" an OSS project, just as long as the thing works (and

by dmpk2k 12y ago

As far as I can tell, nothing is going on, except the typical OSS drama. Frankly, I don't care who "owns" an OSS project, just as long as the thing works (and node does). I leave dumb politics for people with too much idle time on their hands; I recommend you save your time and do likewise.

angersock 12y ago
Dumb OSS drama in the form of systemd is affecting a lot of people. See also Gnome3, OpenSSL, and other things. If we build our businesses on OSS, we all need to pay attention to what's going on. Currently, we use Node and may be doing long-term embedded installs of it--I'd like to see which way the wind is blowing before committing to that path.
- dmpk2k 12y ago
  Node.js has had a concept of API stability for at least a couple years; you can see it listed in all the docs. If you want something to work nigh indefinitely, stick to Stable or Frozen. Unless something radically changes, node is just as good as any other popular dynamically-typed language implementation out there. Probably better than most.
vdaniuk 12y ago
>dumb politics, idle time, typical OSS drama Feeling a bit trollish, aren't you? Consensus building is extremely important to make "the thing work" sustainably in OSS communities. I guess you don't want to invest time and resources into ecosystems that cease to develop only because some idiots (in the classical greek definiton "those who don't participate in politics") didn't care, right?
- dmpk2k 12y ago
  That's only if the consensus-building is in good faith by productive people. Just because politics is happening, doesn't mean it's good. Sadly, politics is easier than hacking code, and attracts a certain type of person; it makes them feel important without doing heavy lifting. I've read enough mailing lists over the years that I am unimpressed by this sort of drama, and the types it attracts. See also: bikeshedding.
- diminoten 12y ago
  Come on, no need to call names. And you have to admit, there's an eye for profit in here which is mucking up the whole thing. Someone's trying to make money off of Node.js's ecosystem, and it's not "consensus building" related at all, so it's actively harming the "make the thing work" part of this OSS community.

by dmpk2k 12y ago

angersock 12y ago

Dumb OSS drama in the form of systemd is affecting a lot of people. See also Gnome3, OpenSSL, and other things. If we build our businesses on OSS, we all need to pay attention to what's going on. Currently, we use Node and may be doing long-term embedded installs of it--I'd like to see which way the wind is blowing before committing to that path.

dmpk2k 12y ago
Node.js has had a concept of API stability for at least a couple years; you can see it listed in all the docs. If you want something to work nigh indefinitely, stick to Stable or Frozen. Unless something radically changes, node is just as good as any other popular dynamically-typed language implementation out there. Probably better than most.

vdaniuk 12y ago

>dumb politics, idle time, typical OSS drama Feeling a bit trollish, aren't you? Consensus building is extremely important to make "the thing work" sustainably in OSS communities. I guess you don't want to invest time and resources into ecosystems that cease to develop only because some idiots (in the classical greek definiton "those who don't participate in politics") didn't care, right?

dmpk2k 12y ago
That's only if the consensus-building is in good faith by productive people. Just because politics is happening, doesn't mean it's good. Sadly, politics is easier than hacking code, and attracts a certain type of person; it makes them feel important without doing heavy lifting. I've read enough mailing lists over the years that I am unimpressed by this sort of drama, and the types it attracts. See also: bikeshedding.
diminoten 12y ago
Come on, no need to call names. And you have to admit, there's an eye for profit in here which is mucking up the whole thing. Someone's trying to make money off of Node.js's ecosystem, and it's not "consensus building" related at all, so it's actively harming the "make the thing work" part of this OSS community.