4 ms·
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 bette
by i_s 12y ago
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.
- volaski 12y agoI think it's not because who's better or worse, but because of how their interest is aligned with focusing on this problem than Apple.
- deleted 12y ago[deleted]
- cgcardona 12y ago> It's becoming pretty clear that they have a much better handle on UI technology than Apple, Google, Microsoft, or anyone really. Can you explain what you're thinking here? In what way(s) specifically? Thanks.
- eddieplan9 12y ago> 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.
- i_s 12y agoImperative coding may be useful to for implementing the API, but that does not mean it is necessary to expose an imperative API to developers. For example, in the browser, W3C and the browser vendors could have exposed a React-like API, implemented via an imperative internal C++ API, but instead they just gave us the DOM. I'm not saying that to complain, just to illustrate that how an API is implemented doesn't have to dictate the API you expose. > 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)
- augustl 12y agoI don't think that's true. Under the mutable UI trees, 60 times a second the entire UI is rendered from scratch in the OpenGL (or similar) layer. It seems to me it would be possible to completely skip that part by making a new React-like OpenGL renderer.
- jiyinyiyong 12y agoI agree with that idea. In my view I think Skia method calls are like assembly and virtual DOM is like a high level programming language. So I decided to try one https://github.com/Quamolit/ https://github.com/Quamolit/ my original idea was to write in React way but generates operations that can be finished with Canvas API. I found it quite hard to finish such a project though. Browser vendor are more likely doing the job of abstracting out hardware and OS powers so people can utilize. There's still much more effect to be done to create an FRP-like(functional reactive programming) system that everybody is happy with.
- jedrek 12y agoIt might very well be that only having two user-facing products is what allows them to concentrate on their UI to this degree.
- tomelliott 12y agoQuite the opposite. Wanting to be able to continue building new products quickly and at scale is the reason we invest in infrastructure like this so heavily.
- smackfu 12y ago>It is too bad Facebook doesn't have their own platform like iOS or Android They tried to make a move on Android with Facebook Home but it crashed and burned.