Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

stackshare.io

Post reply on HN
Print view View original

31–40 of 81 posts

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

#31

Post by mudbutt »

hamstercat wrote: post #13

In my day work we're using Angular 2 (Angular 4 technically), and while I prefer React it's not necessarily bad, just not as good in my opinion. That being said, backward compatibility is crazy non-existant. I had a library that required me to update to the latest version, would have been a minor bump. It wouldn't work with my current version, but then I upgraded and other libraries started breaking because they woul…

Google abandons open source projects all the time, I don't see how that is a strong argument. Facebook actually uses React, IMO Angular 2+ was built for the sole purpose of consulting, thus more breaking changes and magic DSL.

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

#33

Post by [deleted] »

k__ wrote: post #30
platz wrote: post #28

Earlier quoted context omitted.

It is a proxy for how likely the library will continue to exist, and how likely you can hire folks that know these libraries, in several years

Point is, people want the same (what you said) but have entirely different reasons why they would get it from their framework of choice.

[deleted]

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

#34

Post by Vinnl »

dustingetz wrote: post #26
mihaela wrote: post #14

React is great but this: "I’m waiting for the day when the only way that you build UI, the only way you can build UI is with the React paradigm." is scary.

That's super interesting. I dont think React is the end state; it has a couple warts that are solved in research communities. TLDR React is not efficient enough, the performance requirements of next-gen apps of 2020s is going to break React because rendering is not incremental. These warts are basically places where React departs from pure functional programming to achieve ease of use. 1) Fundamental performance prob…

What makes you think 2020 apps are going to be significantly different from 2018 apps? Main difference I can think of is VR and WebAssembly, but the former is not likely to completely change the majority of websites in two years, and the latter is not restrained by React anyway.

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

#35

Post by platz »

k__ wrote: post #30
platz wrote: post #28

Earlier quoted context omitted.

It is a proxy for how likely the library will continue to exist, and how likely you can hire folks that know these libraries, in several years

Point is, people want the same (what you said) but have entirely different reasons why they would get it from their framework of choice.

Because their reasons are different, they are meaningless?

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

#36

Post by k__ »

platz wrote: post #35
k__ wrote: post #30

Earlier quoted context omitted.

Point is, people want the same (what you said) but have entirely different reasons why they would get it from their framework of choice.

Because their reasons are different, they are meaningless?

If one says A and someone else says !A they can't both be right.

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

#37

Post by dwaltrip »

dustingetz wrote: post #26
mihaela wrote: post #14

React is great but this: "I’m waiting for the day when the only way that you build UI, the only way you can build UI is with the React paradigm." is scary.

That's super interesting. I dont think React is the end state; it has a couple warts that are solved in research communities. TLDR React is not efficient enough, the performance requirements of next-gen apps of 2020s is going to break React because rendering is not incremental. These warts are basically places where React departs from pure functional programming to achieve ease of use. 1) Fundamental performance prob…

Does React with Mobx count as incremental? It only re-renders components when the data accessed by that component has changed.

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

#38

Post by tmat »

fartcannon wrote: post #12
tmat wrote: post #9

React has made me a happier developer and affords me a lifestyle to take care of my family very well. So I'm very thankful for everything that's taken place to bring React to where it is. I got the same feeling many many years ago when I made the switch from PHP > Rails. Edit: Why is this being down voted? shrug Must be 2 sad Ember devs... Badum PSSH

I think it's being down-voted because it sounds like a incontinence commercial.

lol, after a reread I concur.

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

#39

Post by platz »

k__ wrote: post #36
platz wrote: post #35

Earlier quoted context omitted.

Because their reasons are different, they are meaningless?

If one says A and someone else says !A they can't both be right.

Their positions are not mutually exclusive because their contexts/problems they are solving are different. So they are not saying A and !A. They are saying A and B

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

#40

Post by a_t48 »

k__ wrote: post #36
platz wrote: post #35

Earlier quoted context omitted.

Because their reasons are different, they are meaningless?

If one says A and someone else says !A they can't both be right.

They can be, if both A and !A are valid choices under different scenarios or values.
Post reply on HN