Govern Node Right(nodegovernance.io) |
Govern Node Right(nodegovernance.io) |
If the fork did nothing else, that would still be a huge leap forward.
https://groups.google.com/forum/#!topic/nodejs/lWo0MbHZ6Tc
Edit: just noticed a delicious bit of prescience from isaacs in the thread:
Right. And if Joyent is a douche, they're going to find
themselves empty-handed, as the node community will find a
new champion.Forks are highly dangerous and fragment communities. Massive BC breaks kill adoption of new versions.
If you want nicer functions, add a new, parallel API.
(Speaking as a former PHP internals contributor.)
If you want safety, add a nice upgrade path so people can actually start using it easily on their existing codebases.
Tag the old API as potentially dangerous/unsafe/deprecated/ugly and warn (or error out if you can opt into a strict mode per-file) so people can upgrade incrementally without waiting for all their dependencies to first (who won't because they have no upgraded users), and without breaking all their tests in one mega-commit.
This has been one of my 'shower' (think about in the shower) projects for quite a while :).
One day I might even take a stab at it.
One big mistake Microsoft made was breaking compatibility with VB6 and VB.NET. What happens to all those people who spent years developing VB6 applications?
If you took PHP and refactored everything and cleaned up the bad bits, it'd be a new language and not PHP. You'd be starting over from scratch and competing with all the other hot and trendy languages fighting for users.
I honestly think a better way would be to write a library that acts as a wrapper/translation layer to the non-intuitive commands that exist in PHP (thinking about it, I'm sure one probably already exists).