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

61–70 of 81 posts

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

#61

Post by potta_coffee »

platz wrote: post #28
k__ wrote: post #15

Earlier quoted context omitted.

"The main reason I've heard for using Angular 2 at my work is that it's made by Google" I say I used React, because it's made by Facebook. They say they use Angular, because it's made by Google. Others say, they use Ember or Vue, because it ISN'T made by a single big corp. In the end these reasons are often meaningless and don't have any effect on the users in their whole lifetime.

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

Except Google pulled a fast one with the Angular 1/2 transition. This is exactly why I'm not using Angular anymore.

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

#62

Post by fizwhiz »

username223 wrote: post #59
yonasb wrote: post #52

Earlier quoted context omitted.

I was just reflecting on this. If you agree that React is a net positive for software development (efficiency, creating complicated UIs faster), then you can make the case that Ads on Facebook have indirectly helped a lot of engineers and thus companies. They had a problem, a piece of technology was created to solve it, and then released to the world, and now many others are able to solve problems using the same tech…

It's sort of like the Manhattan Project writ small. Back then we roasted a few hundred thousand Japanese people, and we may still extinguish life on our planet, but we ended up with some pretty sweet tech. Now we're cynically monitoring and manipulating billions of people, but we may end up with easier ways to create complicated web pages.

> Back then we roasted a few hundred thousand Japanese people

Unbelievable. Flagged.

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

#63

Post by ern »

bdcravens wrote: post #24
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…

> In my day work we're using Angular 2 (Angular 4 technically) Angular 2+ is "Angular"; Angular 1.x is "AngularJS"

As an aside the “it’s just Angular” thing doesn’t work for me when I Google for things...results come up with a mix of AngularJS and Angular2+ results. Searching for “angular2” rather than “angular” seems to work a lot better.

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

#65

Post by bdcravens »

ern wrote: post #63
bdcravens wrote: post #24

Earlier quoted context omitted.

> In my day work we're using Angular 2 (Angular 4 technically) Angular 2+ is "Angular"; Angular 1.x is "AngularJS"

As an aside the “it’s just Angular” thing doesn’t work for me when I Google for things...results come up with a mix of AngularJS and Angular2+ results. Searching for “angular2” rather than “angular” seems to work a lot better.

That's true. Paired with "go", can we dwell on the irony that Google has come up with the worst names for programming projects when it comes to searching for them?

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

#66

Post by rollinDyno »

fizwhiz wrote: post #62
username223 wrote: post #59

Earlier quoted context omitted.

It's sort of like the Manhattan Project writ small. Back then we roasted a few hundred thousand Japanese people, and we may still extinguish life on our planet, but we ended up with some pretty sweet tech. Now we're cynically monitoring and manipulating billions of people, but we may end up with easier ways to create complicated web pages.

> Back then we roasted a few hundred thousand Japanese people Unbelievable. Flagged.

Why is this comment being downvoted? Can't anyone else see the poor taste in words? I'm not sure it deserves to be flagged but definitely worth calling out.

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

#67

Post by hellofunk »

platz wrote: post #29
hellofunk wrote: post #19

Earlier quoted context omitted.

Why is that scary? React's paradigm has changed how UIs are built in many different platforms. And you don't have to use React directly to enjoy its paradigm since other libraries and technologies have appeared that follow the same approach.

You haven't seen how paradigms change yet, have you

Your comment is unclear.

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

#68

Post by swyx »

hesarenu wrote: post #25
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.

I would actually like to see React paradigm used more in native development.

are you referring to his comment about Electron? because React Native is a thing

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

#69

Post by ergo14 »

Bahamut wrote: post #22
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…

Having used both, they both have their strengths and weaknesses - I know both Angular and React is being used by my employer, a top 5 tech BigCo that is not Google (although I have heard there is a little React in Google floating around currently). I’m not sure why this myth about Google not using Angular keeps propagating - I have heard it powers over 70% of Google’s frontends straight from multiple members of the A…

Actually it seems that Google uses both Angular 1.x, 2.x and Polymer. However it seems their newer projects use Polymer, Youtube, Google Allo, Google Music. CodeLabs and others seem to go Polymer route.

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

#70

Post by dbbk »

peterhunt wrote: post #49
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.

To be clear, I didn't mean that I want React-the-library baked into every platform. I do think that React-the-mental-model is superior to, say, Cocoa-the-mental-model, and by baking this model into the underlying layers of the stack we'd stand to see a lot of performance gains. Just my 2 cents though.

Surely you're really just talking about component-oriented design, which basically every framework has now converged on - React, Angular, Ember, Vue, Riot, Polymer, etc.
Post reply on HN