Live data from Hacker News

Magic UI: UI Library for Design Engineers

magicui.design

91–100 of 105 posts

Re: Magic UI: UI Library for Design Engineers

#91
post #57

It saddens me nobody builds similar libraries for Angular.

Yeah, for better or worse, the era of framework diversity is over. The industry has almost 100% converged on React.

Agreed. It's just so much easier to hire for React. It has become the lingua franca of client frameworks.

There are still many teams that choose to use something else. But experience in React is most easily transferrable. Even if I had a project in Vue, I would still look for React expertise.

Re: Magic UI: UI Library for Design Engineers

#93
post #89

Earlier quoted context omitted.

Yeah, for better or worse, the era of framework diversity is over. The industry has almost 100% converged on React.

That sounds false to me. When was this era and what exactly did it look like? React has been dominant for around a decade, but Angular and Vue still see wide usage and Svelte is somewhat on the rise. (Although retention/interest in Angular has been going down.)[1] Highly anticipating State of JS 2023 data though... [1] https://2022.stateofjs.com/en-US/libraries/front-end-framewo...

I'm judging by what I see teams choosing for new projects—both dev shops and corporate/internal devs. Even 5 years ago they might have debated Vue vs React, but there's not even a discussion anymore.

Re: Magic UI: UI Library for Design Engineers

#94
post #89

Earlier quoted context omitted.

That sounds false to me. When was this era and what exactly did it look like? React has been dominant for around a decade, but Angular and Vue still see wide usage and Svelte is somewhat on the rise. (Although retention/interest in Angular has been going down.)[1] Highly anticipating State of JS 2023 data though... [1] https://2022.stateofjs.com/en-US/libraries/front-end-framewo...

I'm judging by what I see teams choosing for new projects—both dev shops and corporate/internal devs. Even 5 years ago they might have debated Vue vs React, but there's not even a discussion anymore.

Sure, but how many teams are you observing? My company is split between Vue and React for different projects, and while greenfield new ones are getting React, Vue is not being deprecated here.

Re: Magic UI: UI Library for Design Engineers

#95
post #94

Earlier quoted context omitted.

I'm judging by what I see teams choosing for new projects—both dev shops and corporate/internal devs. Even 5 years ago they might have debated Vue vs React, but there's not even a discussion anymore.

Sure, but how many teams are you observing? My company is split between Vue and React for different projects, and while greenfield new ones are getting React, Vue is not being deprecated here.

Just a few teams per year—extremely anecdotal. But it sounds like your company is in the same boat, with new projects going to React.

Re: Magic UI: UI Library for Design Engineers

#96
post #74

Setting aside the slowness, tho I am not a designer, these all strike me as just visual noise. I think animated borders, animated shiny text, animated meteor backgrounds today are no better than an early 2000s page with animated elements. It doesn't help communicate, it just attracts the eye until one learns to tune it out. And it kinda tells me that we're not really learning to build better stuff over the decades. W…

I agree that a lot of these components are more distracting than useful. I do like the animated border around buttons, though; that would be very useful to draw the eye towards the "default" option on a page, as long as it was the only one.

This is the thing many of these shouldn't be used just willy nilly, things like the chaser around the border of a container, is awesome as a notification of a change for instance, or the button effect same thing, i'd hate a site that used these nonstop running, but something thats triggered by an event happening is much nicer.

That said, WTF is with all these "libraries" thats basically just collections of shit from codepen stacked in 1 place that they thought was cool, shit most of these don't even have cohesion from one to the other really besides... "cool motion"

Re: Magic UI: UI Library for Design Engineers

#97

These days, every self-respecting library must provide Figma components.

This is a bad generalization - developers should be obligated to provide design artifacts? Then, why can’t I generalize that self respecting designers must provide React code?

Re: Magic UI: UI Library for Design Engineers

#100
post #94

Earlier quoted context omitted.

I'm judging by what I see teams choosing for new projects—both dev shops and corporate/internal devs. Even 5 years ago they might have debated Vue vs React, but there's not even a discussion anymore.

Sure, but how many teams are you observing? My company is split between Vue and React for different projects, and while greenfield new ones are getting React, Vue is not being deprecated here.

I'm building the front ends for a few projects in Vue right now, it's quite pleasant!

It's easy to work with, there's nice router and internationalization packages, ready made components with PrimeVue (though PrimeReact and PrimeNG are nice too; as well as other component libraries), PrimeFlex and Pinia for state management is wonderfully simple and scales pretty far. There's devtools for most browsers, the toolchain isn't super complex and while the ecosystem could be bigger, it's not inadequate either.

Post reply on HN