1. Fixating on platform stability over project evolution
2. Ignoring the community on project direction
3. Preserving public image over project committers
4. Being a total square
NOTE: I am against the fork.
1. Fixating on platform stability over project evolution
2. Ignoring the community on project direction
3. Preserving public image over project committers
4. Being a total square
NOTE: I am against the fork.
That's... hardly a bad thing, in my humble opinion. The other language I use at work, PHP, is a case-study in what happens when you "evolve" a project willy-nilly with little regard to platform stability. Nowadays, it's better, because the community has become more involved in the process, so I can see what #2 and #3 are Bad Things™ however.
I use node.js in production so I'm not knocking it outright but you quickly understand the plights if you try to do anything with node that scales well.
I had the feeling that much evolution happend from 1 to 5 but not much afterwards :\
There is hardly any difference between PHP 4 and 5, except internals. The only real big difference between PHP 3 and PHP 4 is a different class syntax.
I thought the class system was improved with 5 and was unusable with 4. At least that was what I read. I started with ... PHP 5.2