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)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.
Can you explain what you're thinking here? In what way(s) specifically? Thanks.
They tried to make a move on Android with Facebook Home but it crashed and burned.
Wanting to be able to continue building new products quickly and at scale is the reason we invest in infrastructure like this so heavily.
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.