21–30 of 56 posts
It is too bad Facebook doesn't have their own platform like iOS or Android. It's becoming pretty clear that they have a much better handle on UI technology than Apple, Google, Microsoft, or anyone really. Them creating a logical functional UI API on top of messy imperative APIs is very helpful, but even better would be if that was not necessary.
I like the steady stream of innovative projects coming out of facebook as of late, but I can't help but feel like there's quite a bit of overlap in their initiatives. Just the fact that there's a footnote about how this isn't react-native illustrates my sentiments exactly.
it is natural and a good company strategy. Let several teams to produce competing designs that solve a similar problem with different tradeoffs. Eventually one will win inside the company. For example Google has many many competing data backend projects build on top of Big Table, emphasing different requirements.
I think it’s quite amazing what Facebook/Instagram are doing. They are creating a legacy that will hopefully inform what Apple and Google do with their frameworks too.
Earlier quoted context omitted.
You're right that there's some overlap: > It may surprise you to hear that the Components library I’m describing is not React Native, but a separate project. > Why the distinction? It’s simple: React Native hadn’t been invented yet when we rebuilt News Feed in Components. Everyone at Facebook is excited about the future of React Native, and it’s already been used to power both Mobile Ads Manager and Groups. > (from h…
Would be great to note this somewhere on the component kit site.
Interesting justification of their choice of Objective-C++ here: http://componentkit.org/docs/why-cpp.html Anyone else have an opinion on this? Seems unusual for a iOS framework, especially going forward, but the reasons sound sensible enough.
They're changing to Swift in the next version. (He mentions it at the end of the video)
This technology looks great. It is too bad Facebook doesn't have their own platform like iOS or Android. It's becoming pretty clear that they have a much better handle on UI technology than Apple, Google, Microsoft, or anyone really. Them creating a logical functional UI API on top of messy imperative APIs is very helpful, but even better would be if that was not necessary.
This technology looks great. It is too bad Facebook doesn't have their own platform like iOS or Android. It's becoming pretty clear that they have a much better handle on UI technology than Apple, Google, Microsoft, or anyone really. Them creating a logical functional UI API on top of messy imperative APIs is very helpful, but even better would be if that was not necessary.
This technology looks great. It is too bad Facebook doesn't have their own platform like iOS or Android. It's becoming pretty clear that they have a much better handle on UI technology than Apple, Google, Microsoft, or anyone really. Them creating a logical functional UI API on top of messy imperative APIs is very helpful, but even better would be if that was not necessary.
Can you explain what you're thinking here? In what way(s) specifically? Thanks.
This technology looks great. It is too bad Facebook doesn't have their own platform like iOS or Android. It's becoming pretty clear that they have a much better handle on UI technology than Apple, Google, Microsoft, or anyone really. Them creating a logical functional UI API on top of messy imperative APIs is very helpful, but even better would be if that was not necessary.
But without the "messy" imperative API, the functional UI cannot be built. This applies to all functional UI frameworks.
It's funny that one of React's core ideas is to ditch the now old functional/declarative paradigm that is template languages and allows you to use imperative JavaScript to directly build up a virtual DOM.
This technology looks great. It is too bad Facebook doesn't have their own platform like iOS or Android. It's becoming pretty clear that they have a much better handle on UI technology than Apple, Google, Microsoft, or anyone really. Them creating a logical functional UI API on top of messy imperative APIs is very helpful, but even better would be if that was not necessary.
> a logical functional UI API on top of messy imperative APIs But without the "messy" imperative API, the functional UI cannot be built. This applies to all functional UI frameworks. It's funny that one of React's core ideas is to ditch the now old functional/declarative paradigm that is template languages and allows you to use imperative JavaScript to directly build up a virtual DOM.
> It's funny that one of React's core ideas is to ditch the now old functional/declarative paradigm that is template languages and allows you to use imperative JavaScript to directly build up a virtual DOM.
Its agnostic about how you build up the virtual DOM, but it is common to it in a functional way, for example:
this.props.searchResults.map(this.renderSearchResult)