Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NuxtLabs is joining Vercel

nuxtlabs.com

Post reply on HN
Print view View original

21–30 of 83 posts

Re: NuxtLabs is joining Vercel

#21

Post by etchalon »

pier25 wrote: post #9
MortyWaves wrote: post #4

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 consider…

> 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/

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

Re: NuxtLabs is joining Vercel

#22

Post by ayhanfuat »

"Vue is currently the only mainstream framework that remains independent. (i.e. not dominantly owned / backed by a single corporation" Evan You https://x.com/jpschroeder/status/1762764818254016513/photo/1

I know Nuxt is not Vue itself, and I'm not saying Vue is no longer independent — but I do think it's worth remembering that independence is something highly valued in the Vue community.

Re: NuxtLabs is joining Vercel

#23

Post by etchalon »

kelthuzad wrote: post #17
jt_b wrote: post #14

Earlier quoted context omitted.

Astro is nice, but its a different model than Nuxt, more suited to static sites.

I'm just reading the docs and it seems more capable than that: https://docs.astro.build/en/concepts/islands/#server-islands I have also just discovered a dedicated section for the migration from Nuxt to Astro: >Key Similarities between Nuxt and Astro Nuxt and Astro share some similarities that will help you migrate your project: - Astro projects can also be SSG or SSR with page level prerendering. - Astro uses file-b…

It's only "more capable" in the sense that yes, ultimately, it's JavaScript and you can do a lot with JavaScript.

But Astro's model is "generate markup once, serve statically".

Nuxt's model is "Server-Side JavaScript"

Re: NuxtLabs is joining Vercel

#24

Post by danielroe »

Nuxt maintainer here.

there's lots to say here, but from my point of view, Vercel's backing Nuxt largely _because_ of our open vision.

our open approach isn't an optional extra. it's a core value we all share on the team - and indeed, I think, is as close to a core value of the web as I know.

we've pioneered cross-framework adapters and the provider pattern in all we build and there is no way we are changing direction or vision.

nuxt remains an independent framework, like svelte. the fact that a number of us on the team are employed to work full time on OSS is _great_ news for OSS sustainability.

Re: NuxtLabs is joining Vercel

#25

Post by softfalcon »

joshdavham wrote: post #18

Pretty incredible that now Next.js, Svelte/kit and Nuxt will be under Vercel. This could be a great thing as now all of these devs are much better supported in their work, but I’d be lying if I didn’t say that this situation makes me quite nervous.

Embrace, extend, extinguish…

Tale as old as… well, the 60’s… but still, it’s an old tale.

Re: NuxtLabs is joining Vercel

#26

Post by etchalon »

codybontecou wrote: post #16
impulser_ wrote: post #10

Earlier quoted context omitted.

Vercel isn't a competitor to Nuxt. Vercel benefits from allowing any frontend framework to be deployed on their service. All you have to look at is Svelte, which Vercel hired all the developer of, and that turned out to be a great thing. Svelte and SvelteKit are better than ever and nothing they have done since has shown to be forced by Vercel.

Vercel benefits from moving as much of the logic to the server (their paid services) as possible.

Vercel benefits from not letting other, better, cheaper architectures like Cloudflare Workers get better treatment than them from popular framework authors.

Re: NuxtLabs is joining Vercel

#27

Post by eclipxe »

MortyWaves wrote: post #4

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 consider…

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

Re: NuxtLabs is joining Vercel

#28

Post by eclipxe »

yieldcrv wrote: post #13
MortyWaves wrote: post #4

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 consider…

> 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

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?

Re: NuxtLabs is joining Vercel

#30

Post by eclipxe »

danielroe wrote: post #24

Nuxt maintainer here. there's lots to say here, but from my point of view, Vercel's backing Nuxt largely _because_ of our open vision. our open approach isn't an optional extra. it's a core value we all share on the team - and indeed, I think, is as close to a core value of the web as I know. we've pioneered cross-framework adapters and the provider pattern in all we build and there is no way we are changing directio…

Huge fan of Nuxt and your work, excited for this!
Post reply on HN