4 ms·

"It has a large developer community and enables excellent engineering velocity and performance"...

mattmanser 10y ago
Literally 3 years ago you could have said the same about Backbone. And 2 years ago you could have said the same thing about Angular. And now you can say it about React. Are we to expect the next article from Pinterest about [angular 2, vue, elm, etc.] in two years time?
- praneshp 10y ago
  Why is that wrong? Shouldn't you be on the best framework, especially when 2 years have passed?
  - mattmanser 10y ago
    It's attitudes like this that are getting us into this mess. If a framework's only been around for a year, which means nothing serious has been written in it, how can you know its limitations? It's appropriateness for large code bases?
- mercer 10y ago
  3 years ago React didn't exist. 2 year ago Angular didn't exist. Apparently there's still a lot of room for improvement, and much as I'd love for things to settle down soon, I've been very happy that I'm not stuck with jQuery or Backbone as the only tools in my belt!
  - RussianCow 10y ago
    > 3 years ago React didn't exist. 2 year ago Angular didn't exist. Not to nitpick, but React has been around since summer 2013, and Angular 1.0 was released on June 14, 2012, so these libraries have definitely existed for more than 3 years. That said, I think that plays even more to your point that there are 3+ years of positive changes to be gained from switching from Backbone to React.
    - mattmanser 10y ago
      So backbone hasn't been improved at all in 3 years? As that's basically what you're saying.
      - mercer 10y ago
        That's not necessarily what he's saying. If React was a paradigm shift (and I believe it was), Backbone can still be good and it's possible it improved in the interim. But it doesn't change that for many of us it's just not interesting anymore. What surprises me is that you're so uppity about 'defending' Backbone. Nobody is saying it's shit and anyone using it is an idiot. It's just that many of us prefer what came after. It warrants, at most, a discussion as to why this is the case, but I don't see how it's worth any kind of argument.
  - mattmanser 10y ago
    The hell are you talking about? https://news.ycombinator.com/item?id=6328685 https://news.ycombinator.com/item?id=6328685 3 years ago, angular.

Literally 3 years ago you could have said the same about Backbone. And 2 years ago you could have said the same thing about Angular. And now you can say it about React. Are we to expect the next article from Pinterest about [angular 2, vue, elm, etc.] in two years time?

praneshp 10y ago
Why is that wrong? Shouldn't you be on the best framework, especially when 2 years have passed?
- mattmanser 10y ago
  It's attitudes like this that are getting us into this mess. If a framework's only been around for a year, which means nothing serious has been written in it, how can you know its limitations? It's appropriateness for large code bases?
mercer 10y ago
3 years ago React didn't exist. 2 year ago Angular didn't exist. Apparently there's still a lot of room for improvement, and much as I'd love for things to settle down soon, I've been very happy that I'm not stuck with jQuery or Backbone as the only tools in my belt!
- RussianCow 10y ago
  > 3 years ago React didn't exist. 2 year ago Angular didn't exist. Not to nitpick, but React has been around since summer 2013, and Angular 1.0 was released on June 14, 2012, so these libraries have definitely existed for more than 3 years. That said, I think that plays even more to your point that there are 3+ years of positive changes to be gained from switching from Backbone to React.
  - mattmanser 10y ago
    So backbone hasn't been improved at all in 3 years? As that's basically what you're saying.
    - mercer 10y ago
      That's not necessarily what he's saying. If React was a paradigm shift (and I believe it was), Backbone can still be good and it's possible it improved in the interim. But it doesn't change that for many of us it's just not interesting anymore. What surprises me is that you're so uppity about 'defending' Backbone. Nobody is saying it's shit and anyone using it is an idiot. It's just that many of us prefer what came after. It warrants, at most, a discussion as to why this is the case, but I don't see how it's worth any kind of argument.
- mattmanser 10y ago
  The hell are you talking about? https://news.ycombinator.com/item?id=6328685 https://news.ycombinator.com/item?id=6328685 3 years ago, angular.