[MortyWaves]

Nuxt has always been a strange tool that doesn’t really fit well into any good use case, unless your only experience is Vue and Nuxt.

Hard to see the real reason for Vercel to do this. The pessimist in me wonders if perhaps they are hoping to influence how Vue is developed in the same way they now influence how React is developed after hiring several React team members.

But even that doesn’t seem that likely considering the relatively tiny Vue market share and microscopic still Nuxt market share.

I also consider its “community” to be a strange place too. It’s on Discord, and a couple of years ago common internet abbreviations were considered ban worthy rule-breaking offences.

Even the word “lmao” would get you an instant warning from a bot. The framework itself and its oddball community were enough poor experiences for me to stop using it pretty quickly.

[pier25]

> doesn’t really fit well into any good use case

I agree.

If you want an SPA just use Vue's official router. It's getting better now thanks to Eduardo working on file-based router, data loaders, Pinia colada, etc.

If you want a static site or MPA, Astro really seems like a better choice than Nuxt.

https://uvr.esm.is/

https://pinia-colada.esm.dev/

[etchalon]

There is no universe in which Astro is a better choice than Nuxt for Vue-based MPA, SSG or SPA with SSR situations.

[pier25]

No universe, huh?

https://imgur.com/MxSrgj1

[etchalon]

I have no idea what you think that graph is showing or how its relevant.

[pier25]

You don't think having a significantly better CWV score is relevant?

[etchalon]

I think plain text has the best possible CWV score yet is also deficient as an alternative for Nuxt if you're dealing with Vue-based MPAs, SSG or SPAs with SSR.

[threetonesun]

Get Nuxt people paying to deploy on Vercel and over time force the user base to Next and React would be my guess.

[_bent]

It's an aquihire

[yieldcrv]

> Hard to see the real reason for Vercel to do this.

Next supremacy is very obvious

Kills all those Linkedin threads about moving away from Next. Kills the indecision for what employment-seeking devs need to optimize for. Makes those job descriptions less all over the place and even more Next focused

[eclipxe]

That doesn't make any sense at all. Vercel wins either way if you choose Next, Nuxt, or Svelte. Seems obvious - why would they care if you use Next vs. Nuxt now?

[bakugo]

> Vercel wins either way if you choose Next, Nuxt, or Svelte. Seems obvious - why would they care if you use Next vs. Nuxt now?

Because maintaining three projects is more expensive than maintaining one. It's within their best interests to quietly extinguish any alternatives in favor of the one that most closely matches their vision.

[eclipxe]

I actually love Nuxt. If you want all the fullstackness of Next, but without having to deal with React, it's perfect.

[etchalon]

The "without having to deal with React" bit is crazy important.

I also think, even if Nuxt supported React, its overall architecture is just better than Next's.

Everything just seems to plug together better.

[qn9n]

That and the dev tools are a massive upgrade.

[etchalon]

What?

Nuxt is the only "out-of-box-everything-works" framework for Vue.

So yes, if you use Vue, you use Nuxt.