How Facebook's Instagram Acquisition Led to the Open Sourcing of React.js

Re:How Facebook's Instagram Acquisition Led to the Open Sour... by dsjoerg on Saturday November 18, 2017 @08:27AM (#15728866)

"and that’s why you don’t get an Angular 2 scenario with React because the people paying the price are the people actually making the breaking changes"

Amen

[ Parent | on HN ]

Re:How Facebook's Instagram Acquisition Led to the Open Sour... by jacobr on Saturday November 18, 2017 @11:56AM (#15729718)

This is also the case with Ember, built by contributors from corporations actually using Ember in production.

It's not just Angular, many libraries seem to be written by people without a significant investment in their own library. It might be to promote their own education material, their personal brand, or just for fun. That's fine of course, but the projects will probably not be as stable.

[ Parent | on HN ]

Re:How Facebook's Instagram Acquisition Led to the Open Sour... by ma2rten on Saturday November 18, 2017 @04:10PM (#15730710)

Angular is actually part of the Ads team at Google which is also it's biggest user, since AdsWords is written in Angular.

[ Parent | on HN ]

Re:How Facebook's Instagram Acquisition Led to the Open Sour... by amigoingtodie on Saturday November 18, 2017 @09:51AM (#15729134)

This is why you should eat your own dogfood, right?

[ Parent | on HN ]

Re:How Facebook's Instagram Acquisition Led to the Open Sour... by jaredsohn on Saturday November 18, 2017 @11:59AM (#15729733)

This is why you should give a preference to projects where they eat their own dogfood.

[ Parent | on HN ]

Re:How Facebook's Instagram Acquisition Led to the Open Sour... by collectively on Saturday November 18, 2017 @07:54PM (#15731626)

That’s actually true of angular 2 as well, so the quote is just false. Angular 2’s dysfunction has little to do with dogfooding.

[ Parent | on HN ]