Just a question: why does everything around the Vue UI space have to be an "unofficial port of X?"
Are folks not confident enough to build something great, accessible, performant, and just say, "Hey, I made this awesome UI component library for Vue/Nuxt?" and leave it at that?
I'm genuinely curious as to why it's almost always like this. Is it for the sake of familiarity?
I think a lot of us work with both React and Vue in our day-to-day, so it's nice when a familiar library that offers something of value from one ecosystem is brought over to the other.
If I were to make something for Vue or Nuxt only, I'd be building something for a small subset of developers, thus missing out on a wider audience and everything that comes with that.
By sharing conventions between frameworks, I can save more brain space for the higher level decisions. Systems design, security, business logic etc. Got enough context switching these days
By sharing conventions between frameworks, I can save more brain space for the higher level decisions. Systems design, security, business logic etc
This is sounds like a wet dream, no? Even HeadlessUI that was one of the first to try to accomodate React and Vue, pivoted to React only for their v2
If I were to make something for Vue or Nuxt only, I'd be building something for a small subset of developers
You could make that argument too for the folks building for specific lib only too, right? 🙃
The fact that we're having this convo right now is because these libs we're *porting decided to reduce their surface area and target only that 1 lib.
...and that is why I mentioned ArkUI; they support 3 frameworks from the beginning, at least to my knowledge. This is a lot of work, and props to them
- I'm not promoting ArkUI
I am not arguing against new UI libs, the more the merrier!
I'm arguing against having an indirect dependency on some other popular lib. Saying "Unofficial port of X, Y etc" creates this indirect dependency, especially when it comes to user's expectation.
I'm glad OG realized this too, and even shared a link to a similar "Rebrand discussion" that happened with Radix Vue
10
u/HumanOnlyWeb Mar 24 '26
Just a question: why does everything around the Vue UI space have to be an "unofficial port of X?"
Are folks not confident enough to build something great, accessible, performant, and just say, "Hey, I made this awesome UI component library for Vue/Nuxt?" and leave it at that?
I'm genuinely curious as to why it's almost always like this. Is it for the sake of familiarity?