A React implementation of Spectrum, Adobe’s design system • Hacker News Board

Re: A React implementation of Spectrum, Adobe’s design system

#71

Post by _f9cu » Thu, Jul 23, 2020, 5:29 PM UTC

still_grokking wrote: post #31

still_grokking wrote: post #17

Earlier quoted context omitted.

That's only an "issue" of all that "modern" stuff. Many, many years ago I've used Dojo[1] and it's component lib Dijit. It had all that complex widgets in the toolbox. With all the "advantage" stuff like ARIA and internalization. Or you could use Ext, if you could pay it. But than all this "modern 'component' stuff" came form nowhere and you've been back to stone age, where you didn't have even the most basic compone…

It's funny to see facts down-voted by an usually well informed and rational public. :-D Still, facts are facts, no matter how sloppy the wording I've chose. I didn't mean to diminish the effort put into that one incarnation of those so called design systems. I've only mentioned that it's (like all others of the "modern" ones I've seen until now) light years behind what you could have got 10+ years ago. If I would lik…

Down votes are fun. A good sign of being right and others being wrong. :)

Re: A React implementation of Spectrum, Adobe’s design system

#72

Post by harel » Fri, Jul 24, 2020, 12:02 AM UTC

solidasparagus wrote: post #39

still_grokking wrote: post #31

Earlier quoted context omitted.

It's funny to see facts down-voted by an usually well informed and rational public. :-D Still, facts are facts, no matter how sloppy the wording I've chose. I didn't mean to diminish the effort put into that one incarnation of those so called design systems. I've only mentioned that it's (like all others of the "modern" ones I've seen until now) light years behind what you could have got 10+ years ago. If I would lik…

At least for me I find it very hard to believe your rosy story about Dojo. Are you telling me that 15 years ago you were using a framework that had out-of-the-box support for internationalization that is comparable to what we have today?

Actually he's right. I did work with Dojo many years ago. It was very complete, but I found it clunky and slow for my use case. I rewrote the entire app in ExtJS. At the time, this was the most polished toolkit around. If your project was not open source you had to pay for it, but it was worth it. It had every single thing you can think of and it was all working very well, i18n included. However, it was an all-in proposition, and felt like coding a Java Swing application in some way.

Having said that, I don't miss it and I very much like the way things are now.

Re: A React implementation of Spectrum, Adobe’s design system

#73

Post by tantaman » Fri, Jul 24, 2020, 1:51 PM UTC

crubier wrote: post #62

tantaman wrote: post #32

Not sure if its because I've been using React for the last 6 years and I've "fallen out of love" or it is actually starting to show its age but... React, which was once the greatest thing to happen to UI frameworks, now looks like a very leaky abstraction. The prevalence of `useMemo` and `useCallback` to get around perf issues, `useEffect` to try to interact with event systems outside of React, and `useRef` to save t…

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.

Svelte is technically "interface as a function of state"

But I do agree, custom template syntax is a non-starter.

Re: A React implementation of Spectrum, Adobe’s design system

#74

Post by tantaman » Fri, Jul 24, 2020, 1:55 PM UTC

crubier wrote: post #62

tantaman wrote: post #32

Not sure if its because I've been using React for the last 6 years and I've "fallen out of love" or it is actually starting to show its age but... React, which was once the greatest thing to happen to UI frameworks, now looks like a very leaky abstraction. The prevalence of `useMemo` and `useCallback` to get around perf issues, `useEffect` to try to interact with event systems outside of React, and `useRef` to save t…

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.

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