Re:A React implementation of Spectrum, Adobe’s design system
by crubier on Thursday July 23, 2020 @03:34AM
(#23925044)
I disagree. So far NO other UI library/framework than react offered the “interface as a function of state” paradigm. All others (Svelte, Vue partially) are based on templates with their ad-hoc syntax for ifs and maps/loops and so on. This is a non starter for me. I will consider other things than react, as long as they use this concept of interface as a function of state. This is non negociable for me at this point.
[ Parent
| on HN ]
Re:A React implementation of Spectrum, Adobe’s design system
by dbbk on Thursday July 23, 2020 @08:30AM
(#23926585)
Can you clarify what you mean by "interface as a function of state"? All the templated-frameworks still fit this definition... they are reactive to the state of your component. In fact, they are more performant than React because their template syntax provides static analysis, so the app can be optimised at compile time.
Re:A React implementation of Spectrum, Adobe’s design system
by tantaman on Friday July 24, 2020 @09:55AM
(#23939509)
also, it is pretty amazing what you can do without a framework and how simple your code can be if you code in an "interface as a function of state" style.
example: https://github.com/tantaman/fk-your-frameworks-todomvc
Re:A React implementation of Spectrum, Adobe’s design system
by tantaman on Friday July 24, 2020 @09:51AM
(#23939467)
Svelte is technically "interface as a function of state"
But I do agree, custom template syntax is a non-starter.