Pure UI
rauchg.com
Pure UI
1–10 of 25 posts
Re: Pure UI
#2I'm not sure but this sounds like the writer has unknowingly stumbled upon react.
Re: Pure UI
#3I'm not sure but this sounds like the writer has unknowingly stumbled upon react.
[deleted]
Re: Pure UI
#4Timestamp: July 13, 2015
This should be noted in the title.
Re: Pure UI
#5I'm not sure but this sounds like the writer has unknowingly stumbled upon react.
Unknowingly? He mentions React by name.
This was written in 2015, when React was far less popular. Guillermo clearly decided to bet big on React after this- his company Zeit produces next.js, one of the nicer React frameworks out there.
(Can somebody add [2015] to the title?)
Re: Pure UI
#6I'm not sure but this sounds like the writer has unknowingly stumbled upon react.
Unknowingly? He mentions React by name. This was written in 2015, when React was far less popular. Guillermo clearly decided to bet big on React after this- his company Zeit produces next.js, one of the nicer React frameworks out there. (Can somebody add [2015] to the title?)
Also, the author is advocating a UI model that has pre-existed React, it was just popularised by React.
You could argue that Elm is actually closer to what the author is advocating.
Re: Pure UI
#7Earlier quoted context omitted.
Unknowingly? He mentions React by name. This was written in 2015, when React was far less popular. Guillermo clearly decided to bet big on React after this- his company Zeit produces next.js, one of the nicer React frameworks out there. (Can somebody add [2015] to the title?)
Also, the author is advocating a UI model that has pre-existed React, it was just popularised by React. You could argue that Elm is actually closer to what the author is advocating.
Totally. I would argue that React was successful not because of the declarative programming style that it enables, but because it integrates so easily into the imperative JS ecosystem.
Re: Pure UI
#8Earlier quoted context omitted.
Also, the author is advocating a UI model that has pre-existed React, it was just popularised by React. You could argue that Elm is actually closer to what the author is advocating.
Totally. I would argue that React was successful not because of the declarative programming style that it enables, but because it integrates so easily into the imperative JS ecosystem.
I would argue 'integrates so easily into the imperative JS ecosystem' is not a differentiating factor over all the other JS frameworks, so its declarative programming style is far more likely to be the reason it is popular (and in my experience/opinion, this is absolutely the case).
If you just meant popularity vs Elm however, then sure.
Re: Pure UI
#9Earlier quoted context omitted.
Unknowingly? He mentions React by name. This was written in 2015, when React was far less popular. Guillermo clearly decided to bet big on React after this- his company Zeit produces next.js, one of the nicer React frameworks out there. (Can somebody add [2015] to the title?)
Also, the author is advocating a UI model that has pre-existed React, it was just popularised by React. You could argue that Elm is actually closer to what the author is advocating.
Immediate mode UIs have been around forever, actually. They just need a bit of finesse to be made efficient.
Re: Pure UI
#10Earlier quoted context omitted.
Also, the author is advocating a UI model that has pre-existed React, it was just popularised by React. You could argue that Elm is actually closer to what the author is advocating.
Totally. I would argue that React was successful not because of the declarative programming style that it enables, but because it integrates so easily into the imperative JS ecosystem.
Because others "did not"? Other framework didn't need a new language to be usable.