I'm still waiting for a component economy that could keep up with e.g. Delphi's VCL. Right now, it's either big UI frameworks or stuff you've got a hard time integrating (e.g. they download half the internet, require 28 properties to connect/style). Pure rendering model (i.e. independence from data) alone doesn't cut it.
Other than framing it in the language of React/FRP, is this substantially different from template engines? Templates are functions from parameters to markup/UI; they're just written in (usually custom) markup languages instead of Javascript. If a template isn't a pure function of its parameters, then surely you're doing it wrong?<p>PS: I've used several template engines which have an "inheritance" feature, which <i>might</i> refute my point. I never used such features, as they seemed to be shoehorning cargo cult OOP into situations where it's not appropriate. On the other hand, having one template <i>include</i> another for some sub-component acts exactly like one function calling another.
Just a heads up, the <a href="http://primercss.io/buttons/" rel="nofollow">http://primercss.io/buttons/</a> link is broken for me.