Node.js and the Road Ahead

Re:Node.js and the Road Ahead by argonaut on Thursday January 16, 2014 @07:49PM (#7073567)

The "we/you can just fork it" argument really doesn't work out. And when it's used by maintainers to justify something, it's a total cop-out.

The fact is that forking it will fragment the community, confuse users, slow down adoption, and generally have negative effects for years and years. Even if everyone eventually moves to the fork (best-case scenario!), the ecosystem will have lost tremendous amounts of momentum.

[ Parent | on HN ]

Re:Node.js and the Road Ahead by steveklabnik on Thursday January 16, 2014 @08:02PM (#7073623)

> The "we/you can just fork it" argument really doesn't work out.

Worked pretty well for MySQL.

[ Parent | on HN ]

Re:Node.js and the Road Ahead by beaumartinez on Thursday January 16, 2014 @09:08PM (#7073862)

Not really, MariaDB has nowhere near the adoption levels MySQL has.

Even so, MySQL was one of the biggest gratis databases, and it happened to be bought by a company that specialized in selling established enterprise database software. There was concern RE the support a gratis database would have under such a company.

The situation that created MariaDB is very specific, and very different to the one Node.js is in.

[ Parent | on HN ]

Re:Node.js and the Road Ahead by mattmanser on Friday January 17, 2014 @08:16AM (#7075548)

LibreOffice then?

[ Parent | on HN ]

Re:Node.js and the Road Ahead by alecthomas on Friday January 17, 2014 @10:57AM (#7076400)

I think the XOrg fork from XFree86 is the best example I can think of.

[ Parent | on HN ]