3 ms·

> It tooks years to sort that out. Yep, maturing takes time - duh.

• sametmax 8y ago
  Maturing is good. Marketting beta products as solutions to the problems you have right now isn't. This problem doesn't exist in the PHP, Python or Ruby communities. We get incremental improvements, sometimes a few innovative contenders show up, we evaluate it, then a winner appear, generally under a year. With JS it's: - a new wild pokemon appears ! - quick, everybody make 200 new pokeball models and throw them at it - spend 3 years sorting said pokeballs, while the pokemon disapears
  • nicoburns 8y ago
    > quick, everybody make 200 new pokeball models and throw them at it I mean, it's not like this is forced upon you. You're free to continue to use Backbone or Knockout or Ember if you want to. Angular 1.x has been replaced with Angular 2 (and I think the Angular team was rightly criticised by how they managed this transition), but most other popular frameworks are still around. Of course, for new projects you may want to pick a newer framework if you believe it offers significant improvements over what came before. For me, React was clearly in this category. And yes, there are lot of people who chase the latest shiny thing, even if it is new and unproven. But that doesn't mean there aren't also stable, proven stacks.
    • sametmax 8y ago
      Nobody lives in a vacuum, and there are many reasons for not being able to choose the techs you will have to work with. In fact, the main reason is that there is no current other client side web language than Javascript. We don't use JS because it's great. It's a badly designed languages, and half of the stack we use are hacks to make it usable. We use it because there is nothing else.