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

41–50 of 81 posts

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

#41

Post by danso »

> The guy that actually originally came up with idea for React, Jordan Walke, came from the ads team. He was like, "making a change on this product is terrifying, like potentially lose a day of revenue because you’ve missed a semicolon or something." He had felt the ads pain and then he convinced them after building this thing on nights and weekends to work on it full time for a little while. As he was working on this framework full time he built a type ahead component and had rolled that out I think in maybe a little News Feed unit but never a full application. Instagram was like the first full application...

Given how big of a part React plays in so many stacks and applications, React's origin sort of ironic considering one of the most famous criticisms of today's Silicon Valley -- "“The best minds of my generation are thinking about how to make people click ads" -- also comes from a former member of Facebook's Ads team, Jeff Hammerbacher.

https://quoteinvestigator.com/2017/06/12/click/

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

#43

Post by polskibus »

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.

Winapi and windows forms in .net. message loop for UI programming is a very very old pattern. It was just reinvented for web and JS. I don't know if people that created react actually ever used Windows message loop.

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

#44

Post by brlewis »

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

I don't think it necessarily is. I know you're saying this because a language or library from a big company is likely to be dropped, but occasionally one will last a long time like Sun's Java. Just because it originates from an individual like PHP did doesn't mean for sure that it will continue to exist a long time and you'll be able to hire people.

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

#45

Post by ma2rten »

dsjoerg wrote: post #6

"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

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

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

#46

Post by danschumann »

k__ wrote: post #15
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…

"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.

The appeal to authority is a logical fallacy and isn't a real reason to use something. I use react because I like it and enjoy it, sure I have reasons behind my enjoyment, like modularity, cohesion, proactive rendering, expressive states, but mainly it feels good because there isn't as much mental translating: what the code looks like vs what the page will look like.

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

#48

Post by rhizome »

ryanmarsh wrote: post #21
fartcannon wrote: post #12

Earlier quoted context omitted.

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

Name checks out

FYI, "fart cannon" is a kind of automotive muffler.

https://www.youtube.com/watch?v=5gLX-P5oQUM

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

#49

Post by peterhunt »

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.

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

#50

Post by platz »

brlewis wrote: post #44
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

I don't think it necessarily is. I know you're saying this because a language or library from a big company is likely to be dropped, but occasionally one will last a long time like Sun's Java. Just because it originates from an individual like PHP did doesn't mean for sure that it will continue to exist a long time and you'll be able to hire people.

I think you completely misinterpreted my comment
Post reply on HN