4 ms·

Joyent is accused of: 1. Fixating on platform stability over project evolution 2. Ignoring the community on project direction 3. Preserving public image over

Joyent is accused of: 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.

girvo 12y ago
> 1. Fixating on platform stability over project evolution 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.
- k__ 12y ago
  PHP? I had the feeling that much evolution happend from 1 to 5 but not much afterwards :\
  - mappu 12y ago
    5.3 is basically a whole new language. Development is pretty quick and regular ever since 5.4 and the new RFC process.
  - skrebbel 12y ago
    Have you at all been paying attention? PHP 5.6 has namespaces, closures, lambdas, generators, autoloaders, traits, function argument splats, sane array literals - basically everything the authors ever saw in good use, anywhere. 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.
    - k__ 12y ago
      Well, I switched from PHP to JavaScript, so, no lol. 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
  - girvo 12y ago
    PHP 5.6 and what Facebook are doing with HHVM/Hack are (in the latter case, literally) entirely new languages than PHP4 or even pre-5.3, and with the PSR community standards body, Composer/Packagist and the massive amounts of interoperation between libraries nowadays, it's actually enjoyable to code in again :)
- invisible 12y ago
  Unfortunately, I think node.js is still lacking in a lot of regards that a brief spurt of "willy-nilly" commits (plus some dictatorship-style thoughtfulness) would help. Many of the builtin modules are still "beta" and even core stable ones lack some features that require using unsupported/undocumented properties (it is not even clear why some of it is undocumented). 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.

girvo 12y ago

> 1. Fixating on platform stability over project evolution 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.

k__ 12y ago
PHP? I had the feeling that much evolution happend from 1 to 5 but not much afterwards :\
- mappu 12y ago
  5.3 is basically a whole new language. Development is pretty quick and regular ever since 5.4 and the new RFC process.
- skrebbel 12y ago
  Have you at all been paying attention? PHP 5.6 has namespaces, closures, lambdas, generators, autoloaders, traits, function argument splats, sane array literals - basically everything the authors ever saw in good use, anywhere. 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.
  - k__ 12y ago
    Well, I switched from PHP to JavaScript, so, no lol. 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
- girvo 12y ago
  PHP 5.6 and what Facebook are doing with HHVM/Hack are (in the latter case, literally) entirely new languages than PHP4 or even pre-5.3, and with the PSR community standards body, Composer/Packagist and the massive amounts of interoperation between libraries nowadays, it's actually enjoyable to code in again :)
invisible 12y ago
Unfortunately, I think node.js is still lacking in a lot of regards that a brief spurt of "willy-nilly" commits (plus some dictatorship-style thoughtfulness) would help. Many of the builtin modules are still "beta" and even core stable ones lack some features that require using unsupported/undocumented properties (it is not even clear why some of it is undocumented). 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.