@beranger
I'd avoid blanket, cliched dismissals, such as "xxx sucks" in the same post wherein I chided an author for not elaborating on and backing up opinions regarding tangential points.
I'd make the following observation about forks. They mean potentially significant elements of a development team believe the project's priorities should change. If one agrees with the rationale for forking and one sees traction as the code is adapted to the new priorities, than one goes with the fork. If not, stay with the old code. There is the potential for NIH duplicative effort. That's undeniable. That doesn't seem to me as wasteful or pointless as religious flamewars between the forking and base project camps. Why do you care? It doesn't cost any more to run OpenOffice.org, LibreOffice, or both.
Discussion on:
Message 10 of 1
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
