Live data from Hacker News

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

stackshare.io

71–80 of 81 posts

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

#71
post #70

Earlier quoted context omitted.

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.

These are all DOM-based UI frameworks. Perhaps it's because that's where all the action is at but I wouldn't be surprised if it were driven, for a large part, by the underlying platform.

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

#72

Earlier quoted context omitted.

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.

Not the loop. JSX way of declaring UI structure.

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

#73
post #70

Earlier quoted context omitted.

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.

Most of those keep the html separate even many are tightly coupled.

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

#74
post #62

Earlier quoted context omitted.

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

Yes, it is poor taste, unnecessarily insulting, and assumes 'we' == 'US'. "Worth calling out"? Nope. That puts unnecessary emphasis on it, and creates unnecessary discussion. Either the comment should be upvoted or downvoted. Readers are mature enough to decide that. I tend to downvote any complaints or discussion about moderation (including this one by myself if I could) because it is boring/offtopic read. YMMV.

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

#75
post #70

Earlier quoted context omitted.

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.

I'm pretty sure it's this + 1-way data binding + data as the driver of everything + javascript as the _only_ language to describe the ui. Because those elements make for a simpler way to build UIs and I totally agree with this point of view

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

#76

Earlier quoted context omitted.

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.

Not the loop. JSX way of declaring UI structure.

Do you mean like XAML and WPF ? https://msdn.microsoft.com/pl-pl/library/ms752059(v=vs.110)....

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

#77
post #74

Earlier quoted context omitted.

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.

Yes, it is poor taste, unnecessarily insulting, and assumes 'we' == 'US'. "Worth calling out"? Nope. That puts unnecessary emphasis on it, and creates unnecessary discussion. Either the comment should be upvoted or downvoted. Readers are mature enough to decide that. I tend to downvote any complaints or discussion about moderation (including this one by myself if I could) because it is boring/offtopic read. YMMV.

Not gonna downvote you. I am from the US, and am deeply ambivalent about the nuclear bombing of Hiroshima and Nagasaki. It may have ended the war sooner; it definitely killed hundreds of thousands of Japanese people. Not many of the European Allies said much at the time. That's war.

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

#78

Earlier quoted context omitted.

Not the loop. JSX way of declaring UI structure.

Do you mean like XAML and WPF ? https://msdn.microsoft.com/pl-pl/library/ms752059(v=vs.110)....

I suppose so. But i do like reactjs declarative style rather code behind. Something which Flutter does as well.

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

#79

Earlier quoted context omitted.

Not the loop. JSX way of declaring UI structure.

Do you mean like XAML and WPF ? https://msdn.microsoft.com/pl-pl/library/ms752059(v=vs.110)....

XAML is a template, it hooks into a controller via bindings. You could compare it to Angular maybe.

In React a view is a function of state:

    const Header = ({ color, children }) => {children}
    
    // Gets transpiled into:
    const Header = ({ color, children }) => createElement('h1', { style: { color } }, children)
    
    hello
A large part of my career was about XAML/WPF/SL. I know it took me a year or more to really understand it deeply, being able to extend and do everything i wanted. I came to the same state 60 minutes into React. The pattern behind it does make many things easier. And that is an understatement. I believe that's also the main reason Microsoft itself is betting on React for cross platform and native apps as well as extension eco systems:

https://github.com/Microsoft/react-native-windows

https://github.com/Microsoft/reactxp

https://developer.microsoft.com/en-us/fabric

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

#80
post #34

Earlier quoted context omitted.

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.

"2020s" e.g. 2028

Apps are like moores law; every 1.5 years the sophistication doubles.

Post reply on HN