News for hackers. Stuff that matters.
Re:React v16.3.0: New lifecycles and context API by swalsh on Thursday March 29, 2018 @05:55PM (#16711429)
In the unlikely scenario of Facebook's demise, how do you think the maintenance of React would transpire? Do you think some other tech company would snatch up the design leads, and pick up the torch? Would it go into its own independent organization?
Re:React v16.3.0: New lifecycles and context API by hoodoof on Thursday March 29, 2018 @07:07PM (#16712058)
There is no demise coming for Facebook.

They'll clean up, grandma, aunty and the school mothers will continue posting and they never even knew there was an issue.

People will soon forget.

Re:React v16.3.0: New lifecycles and context API by chrischen on Thursday March 29, 2018 @11:51PM (#16713551)
Eventually grandma will cease to exist.
Re:React v16.3.0: New lifecycles and context API by navls on Thursday March 29, 2018 @07:57PM (#16712368)
> Will MySpace ever lose its monopoly? [2007]

https://www.theguardian.com/technology/2007/feb/08/business....

Re:React v16.3.0: New lifecycles and context API by hashbig on Friday March 30, 2018 @01:31AM (#16713901)
People that keep comparing FB to Myspace simply don't understand scale.

Having 2 billion users is not a 1000x better than having 2 million ones. It's more like a million times. The network effect compounds non-linearly.

Facebook (the company) is here to stay. Even if the product is gone, they own 2 other multibillion dollar social networks: Instagram and WhatsApp.

Re:React v16.3.0: New lifecycles and context API by Bahamut on Thursday March 29, 2018 @09:38PM (#16712933)
FB is on a whole different level in terms of revenue (and profitability) and users.

While it may be possible that FB fails, there’s not a whole lot of symptoms apparent that it will, unlike MySpace.

Re:React v16.3.0: New lifecycles and context API by matte_black on Thursday March 29, 2018 @07:03PM (#16712023)
React could easily spin off into its own org funded by donations.
Re:React v16.3.0: New lifecycles and context API by plopz on Thursday March 29, 2018 @07:56PM (#16712359)
There are a bunch of react-compatible virtual dom alternatives like preact and inferno that I imagine people would switch to.
Re:React v16.3.0: New lifecycles and context API by hysan on Thursday March 29, 2018 @06:11PM (#16711559)
My bet would be on someone like Expo taking up the reigns and putting in place a way for the community to keep it going.
Re:React v16.3.0: New lifecycles and context API by myth_drannon on Thursday March 29, 2018 @09:17PM (#16712822)
I think developers will stop using ReactJS long before FB is gone. Look at angular, backbone, JQuery, Adobe Flex and so many others. It's just a framework....
Re:React v16.3.0: New lifecycles and context API by adam_sohn on Thursday March 29, 2018 @09:36PM (#16712920)
Angular 5 is very popular now. Big teams with data intensive administration dashboards are choosing it over React.
Re:React v16.3.0: New lifecycles and context API by aioprisan on Thursday March 29, 2018 @09:56PM (#16713031)
I don't buy it. Vue is eating Angular's lunch, with React leading. https://medium.jonasbandi.net/angular-vs-react-popularity-ea...
Re:React v16.3.0: New lifecycles and context API by cztomsik on Saturday March 31, 2018 @10:31AM (#16723431)
Vue is great, I love it for my personal projects and it's also fairly common in PHP world but that's it. Angular is very popular in Java world and it works really great if you need a lot of forms. These people usually don't have time talking about it. React is popular everywhere else, especially among bloggers who usually fail to explain why exactly is React better choice.
Re:React v16.3.0: New lifecycles and context API by plexicle on Friday March 30, 2018 @01:42AM (#16713945)
I don't buy that. I actually see Angular being USED in big corporate environments. I hear from friends about how their team is USING it.

I hear people TALK a lot about Vue. Nothing against it, I enjoyed my little hobby project in it. But way more people talk about using Vue than actually using it. In no way is it "eating Angular's lunch". This is coming from someone quite critical of Angular.