Slashdot Mirror


Node.js Forked By Top Contributors

New submitter jonhorvath writes: Several of the top contributors to Node.js, a popular open source run-time environment, have decided to fork the project, creating io.js as an alternative. The developers were unhappy with how cloud computing company Joyent was directing work on Node.js. Mikeal Rogers said, "We don't want to have just one person who's appointed by a company making decisions. We want contributors to have more control, to seek consensus." Here's the new repository, and a README file to go with it. A developer at Uber tweeted that they've already migrated to io.js on their production systems. It'll be interesting to see how many other sites follow.

18 of 254 comments (clear)

  1. main site by Trepidity · · Score: 4, Informative

    I believe this is one part of the "Node Forward" project.

  2. Joyent unfit to lead them? by MikeRT · · Score: 5, Informative

    You think? You treat a core contributor like this and then wonder why he steps down and leaves? The best part is that when they announced his departure they're like "yeah, uh we totally respect him and his amazing contributions now please respect our wishes and stop bringing up the fact that we are a bunch of SJW tools who treated a major contributor with less respect than Linus Torvalds treats people who intentionally crap all over his code base."

    I've shown this crap to coworkers who were interested in learning Node and their reaction was "W...T...F..." that's how they treat their community?

    1. Re:Joyent unfit to lead them? by MetalliQaZ · · Score: 5, Interesting

      Wow, after reading that blog post, I suddenly understand exactly why they're forking themselves away from Joyent. And to be honest, I'm now expecting that Io.js will become dominant over Node.js in time, which is the opposite of what I thought yesterday.

      Apparently Joyent doesn't want to focus on the product. 99% of people who depend on Node.js don't give a flying fart about what pronouns are used in COMMENTS in the library.

      --
      "Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
    2. Re:Joyent unfit to lead them? by JaredOfEuropa · · Score: 4, Interesting
      From the Joyent guy:

      [...] to reject a pull request that eliminates a gendered pronoun on the principle that pronouns should in fact be gendered would constitute a fireable offense for me and for Joyent. On the one hand, it seems ridiculous (absurd, perhaps) to fire someone over a pronoun -- but to characterize it that way would be a gross oversimplification: it's not the use of the gendered pronoun that's at issue (that's just sloppy), but rather the insistence that pronouns should in fact be gendered. To me, that insistence can only come from one place: that gender—specifically, masculinity—is inextricably linked to software, and that's not an attitude that Joyent tolerates.

      This is about replacing "he" with "they" somewhere. Noordhuis' single response in the comments section to this change was "Sorry, not interested in trivial changes like that.", and a flamewar that is as stupid as it is predictable ensues. Joyent then jumps to the conclusion not just that rejecting a trivial change like this constitutes an insistence on principle that pronouns should be gendered, but that such insistence springs from the notion that masculinity is inextricably linked to software. And this is a sacking offense? MikeRT called it right when he used the term "SJW tools". To me, this would at most be cause to remind the employee of whatever Diversity policies the company has in place.

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    3. Re:Joyent unfit to lead them? by MetalliQaZ · · Score: 5, Insightful

      You're blinded by your strong support of activism. The issue is the way that Joyent threw the guy under the bus. They said, in essence, "We would fire this guy if we could, but he's totally not an employee. We hate him as much as you do, so don't hate on us!" And they said it in a very public way. That's alienation. Oh, they forked it? Big surprise.

      If you actually looked at the merge request he rejected it for being a worthless change. He didn't invest any value in a change that had no functional improvements and didn't even make the documentation any clearer. It was just churn. He didn't reject it on the grounds that pronouns should be masculine.

      --
      "Here Lies Philip J. Fry, named for his uncle, to carry on his spirit"
    4. Re:Joyent unfit to lead them? by bigguy4u · · Score: 5, Informative

      He resisted the correction not because he was opposed to the content of the changes, but the way the change was applied. As later explained, one of the guidelines they had was to accumulate small doc changes until they had enough to prevent git-blame from becoming too convoluted, or at least that's what was being said. This was why the initial PR was rejected, and when somebody else merged it in after the rejection, the commit was undone due to contributor politics. It was never about the gender pronouns, but people conveniently disregarded anything stating otherwise and called the contributor sexist and other such things; joyent decided to join in and called him an "asshole", despite, again, this not being about gender pronouns, but the git history. The contributor later explained his position.

    5. Re:Joyent unfit to lead them? by stonecypher · · Score: 5, Informative

      Oh nonsense.

      to reject a pull request that eliminates a gendered pronoun on the principle that pronouns should in fact be gendered would constitute a fireable offense for me and for Joyent.

      Back here in the real world, this is how this sounds:

      "Ben decided that someone was making changes to the codebase that had no technical purpose, which served solely to push someone's weird social agenda and desperation to modify the language to suit them, as well as to refer to anything which went otherwise as sexist. Since this is pointless, and since Ben has been in communities where this created unnecessary shitstorms, Ben rejected the PR in the hope of preventing a bunch of drama-driven developers from wasting a year complaining about unimportant things. When Isaac decided to merge the PR, Ben felt slighted: he had been given the authority to make these decisions, and Isaac decided to make a social point that Ben would get trampled no matter what."

      That's all fine and good. One developer is being a neckbeard about not wanting to hear a cry of oppression in something that has nothing to do with social justice. The other developer is being a neckbeard about being all inclusive no matter the tone.

      Then you get to the point that adults are angry about.

      and if he had been, he wouldn't be as of this morning: to reject a pull request that eliminates a gendered pronoun on the principle that pronouns should in fact be gendered would constitute a fireable offense for me and for Joyent.

      That says "we value Ben so little that our disagreement over the nature of an unimportant, purely social justice related, non-technical PR would have caused us to fire him on the spot, instead of to have a discussion."

      That's *ridiculous*. Employers have an obligation to their employees to create safety and stability. There is no legitimate cause on God's green earth for that to be a fireable offense. Joyent's management are PR-oriented children, and that you're standing up for them is an embarrassment to the 'movement' you're trying to rationalize.

      I am a gay and trans ally.

      But nobody should get anything sterner over something like that than a stern talking to. That's *obscene*.

      --
      StoneCypher is Full of BS
    6. Re:Joyent unfit to lead them? by Zeromous · · Score: 5, Insightful

      They lost me when they said had he been a Joyent employee it would have been a firing offense. I say: give it up, She's dead Jim and you killed it by politicizing a commit. Fork it and forget it. goodbye.

      --
      ---Up Up Down Down Left Right Left Right B A START
    7. Re:Joyent unfit to lead them? by Anonymous Coward · · Score: 5, Informative

      Sorry, can't share your outrage. Using gender-neutral pronouns for documentation seems reasonable to me, especially if viewable by the public, and if that documentation is linked to your company. To refuse to correct gendered pronouns just seems perverse.

      In the English language, words like "he" and "him" are used in the contexts when the sex is masculine, neutral, or unknown. Words like "she" and "her" are only used when the sex is both known and known to be feminine. Let me repeat and bold this: "he" and "him" are the gender-neutral terms. The documentation was already gender-neutral. What is perverse is saying that somebody should be fired because you don't know second-grade English, as Bryan Cantrill did.

    8. Re:Joyent unfit to lead them? by Jesus_666 · · Score: 4, Informative

      The blog is useless. I read the Github discussion on the pull request and the revert. Here's what happened:

      1. A pull request containing only two very minor changes to comments in the source code was made.
      2. Mr. Noordhuis rejected the pull request with a terse "Sorry, not interested in trivial changes like that."
      3. A flamewar erupts about the appropriateness and neccessity of the singular "they". Mr. Noordhuis is not participating in the flamewar.
      4. The pull request is forced through while the flamewar rages on.
      5. Mr. Noordhuis reverts the forced landing on the grounds that it violated project policy. The revert immediately begins to accumulate a fair number of hostile comments.
      6. The flamewar intensifies. Allegations are made about Mr. Noordhuis's character.
      7. A joyent employee, acting in an official role and using Joyent's official blog, decided to write and publish a text about how Mr. Noordhuis is sexist and would've gotten fired from Joyent on the spot, indirectly calling Mr. Noordhuis an asshole in the process. Joyent, by not taking the text down, implicitly endorses it.
      8. Mr. Noordhuis posts into the discussion to point out that the rejection/revert had been made on purely procedural grounds. He simultaneously announces that he will leave the project, which I can fully understand.

      After that the flame war goes on. Some people actually point out that Joyent's behavior is highly unprofessional, which the Joyent employee disregards because "'Fired' isn't a gendered word that has larger social ramifications that careless use of pronouns does." So yes; according to Joyent, publicly calling someone so sexist that they would've been fired on the spot is less bad than using "he" in a gender-neutral role. (Bonus points for one woman in the discussion calling the whole thing a "witch burning". For the record, she was also the one person to offer a solution instead of flaming about pronouns.)

      If IBM and Oracle worked remotely like that they'd be up to their ears in wrongful termination suits. And libel suits. And, depending on whether insults are an actionable offense in the relevant jurisdiction, suits about that too.

      The sad thing is that early on someone offered a perfectly reasonable way of resolving the situation: Mandating the singular "they" in the project's coding guidelines and then floating changes to existing code until they can be mixed in with other refactoring commits. Of course it was completely ignored.


      (For the record, I am a proponent of singular-they and I still think that the term "social justice warriors" with all its negative connotations entirely applies here. Many of the people involved completely went off the rails as soon as the pull request was rejected and immediately assumed Mr. Noordhuis to be a moustache-twirling antifeminist villain.)

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
  3. Byebye Node.js. by Qbertino · · Score: 5, Interesting

    If these guys know how to play it right, Node.js is history. He had the same thing with the Mambo Fork Joomla. Hardly anyone remembers Mambo anymore, and Joomla is a leading project.

    I hope this new project knows how to manage things and do good marketing.
    Thumbs up. Let's see where this goes.

    --
    We suffer more in our imagination than in reality. - Seneca
    1. Re:Byebye Node.js. by Shatrat · · Score: 4, Funny

      If these PEOPLE know how to play it right, Node.js is history. HE/SHE had the same thing with the Mambo Fork Joomla. Hardly anyone (POSSIBLY HAVING A PENIS BUT POSSIBLY NOT) remembers Mambo anymore, and Joomla is a leading project.

      FTFY

      --
      09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  4. Re:Effort dilution by SQLGuru · · Score: 4, Insightful

    Very true. For "the common man" to know what direction to take, too many choices can be bad......especially when there is more similarity than differences and not enough experience to know which differences will be important to them in the future.

  5. Re:Effort dilution by Penguinisto · · Score: 4, Interesting

    The scourge of Open Source disguised as choice..

    I disagree over the degree of which this would be a problem - think of it more like the free market. Under ideal conditions, the best ideas with the broadest appeal tend to win, grow and evolve, while the worst ideas with little appeal tend to fade away relatively quickly.

    It also provides a very useful ejection seat of sorts in case of corporate asshattery (see also OpenOffice/Libre Office), patent follies, or worse. Also, consider this: Closed-Source/proprietary software can be just as prone to this kind of internal dissent as OSS, but you the end-user will never have a say in the results.

    Forking is awesome to have as an option - either as a threat or as an actuality. A company who knows that their shit could be forked will either behave themselves, or they will lose control of their product. IMHO that's a damned good thing.

    --
    Quo usque tandem abutere, Nimbus, patientia nostra?
  6. Re:take their money and run... real classy by Archangel+Michael · · Score: 4, Insightful

    Corporations need to understand that while they will get features they want, sometimes they need to address the needs of the whole community. Else, they will end up with no support. No support, but everything you want may be okay, but more likely no support will kill whatever it is that you wanted.

    --
    Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
  7. Re:difference? by Junta · · Score: 4, Informative

    People don't fork 'just because they can'. They fork because they are failing to get what they want out of the project. It remains to be seen if they are wasting their time.

    It could be like ethereal to wireshark, where the holder of the copyright has precisely *zero* development skin in the game.

    It could be like XFree86 to Xorg where both had some nominal capability to continue, but it becomes quickly apparent that the fork is where the development effort went.

    It could be like Wayland fork where the fork pretty much died (though the main project isn't seeing massive adoption either).

    Worst case would be something like the ffmpeg/libav fiasco, where both forks go and which one is available readily for a given distribution is almost more a matter of politics than technical merit, and yet they have significantly diverged.

    --
    XML is like violence. If it doesn't solve the problem, use more.
  8. Re:Effort dilution by RabidReindeer · · Score: 4, Interesting

    I disagree over the degree of which this would be a problem - think of it more like the free market. Under ideal conditions, the best ideas with the broadest appeal tend to win, grow and evolve, while the worst ideas with little appeal tend to fade away relatively quickly.

    That's fantasy. The best ideas often wither while mediocre - even bad ones - flourish. It also makes the foolish assumption that "best" conflates with "broadest appeal".

    MacDonalds didn't get where they were because their products were the best. Their milkshakes taste like library paste. They got there because once they'd achieved critical mass in the market - as the old saying goes: Nothing Succeeds Like Success. Once customers knew that they could obtain a consistent product from coast-to-coast, even though it was consistently second-rate, growth was assured.

    Or perhaps an example closer to home. The Commodore Amiga. The first mass-market computer to include Total Harmonic Distortion and Stereo Separation specs on the outside of the package. The first mass-market computer to come out-of-the-box with color graphics (accelerated), Hi-fi stereo sound and full pre-emptive real-time multi-tasking. Even most modern-day systems aren't real-time.

    This was the company that "succeeded in spite of itself". Demonstrating that incompetent government isn't the only way to kill competitiveness, Commodore fielded a superior product which could have been even more successful if they hadn't been cursed with incompetent management.

    But bad management or not, I'm really doubtful that they'd own the market today. The Wintel platform was already too well entrenched and "Nobody Ever Got Fired for buying IBM/Microsoft/Intel". Even Apple is just an also-ran. The competiton was inferior, but it was sufficient and these days only a few tattered remnants are all that remains of the Amiga.

  9. Re:Effort dilution by Kjella · · Score: 4, Insightful

    Don't forget that the PC totally owned the business market, spreadsheets were the killer application of the 80s and the Amiga's multimedia capabilities was totally irrelevant to that. In fact, graphics and sound cards were an add-on to PCs long, long after that. They could have made something similar to the Sony Playstation and become kings of the gaming market, but I doubt they ever had a shot at replacing the PC.

    At any rate, it's obvious that in many cases we have picked a non-optimal solution, but the switching costs are just too high. Things like driving on left vs right, power plugs, 50Hz vs 60Hz TV, imperial vs metric and so on. Or simply because of history or network effects, we use COBOL because we got 20 years of code written in COBOL. Or we're on Facebook because everyone else is on Facebook. Products are like genes, it's not the "best" genes that survive it's those that turn a profit and reproduce.

    --
    Live today, because you never know what tomorrow brings