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

41–50 of 83 posts

Re: NuxtLabs is joining Vercel

#41

Post by toddmorey »

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…

I hope so! The Nuxt adapters and provider pattern are amazing! Its truly impressive how well done it all is and how portable Nuxt is and how other projects have been able to use a lot of the same OSS tech you've created to get portability from the jump.

The portability story for Vercel's own Nextjs is a disaster.

Re: NuxtLabs is joining Vercel

#43

Post by 9dev »

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.

That’s awful. Vercel has pretty much a monopoly on the hybrid framework space now, and it’s going to ruin everything. NEVER did a monopoly do any good to anyone but its holder.

Props to Vercel, I guess. Enjoy your champagne. Increased the share holder value, job well done! Clap, clap.

Re: NuxtLabs is joining Vercel

#44

Post by 9dev »

strickjb9 wrote: post #31

I'm baffled by the doom-and-gloom reactions here. Nuxt remains what it's always been: the best convention-over-configuration framework in existence. It's built on Vue which is opinionated as hell, and you get all the benefits of that. The "vendor lock-in" concerns are frankly overblown. At the end of the day Nuxt produces artifacts you can deploy anywhere - AWS, Cloudflare, your own infrastructure, or yes, Vercel. Th…

Everything you say is now subject to change due to strategic decisions by a single entity that owns almost all horses in the race. The things you take for granted now can disappear tomorrow, no matter how many times they pinky promise not to.

Nuxt is great, but Chromium is great too. Yet, Google has become the driving force behind changes to the web platform, for better or worse. That’s not a desirable situation, and certainly not the only one: it’s not like there’s only a single company out there able to fund open source software. I desperately hope we, collectively, will figure out a better financing model in the future.

Re: NuxtLabs is joining Vercel

#47

Post by tomrod »

9dev wrote: post #43
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.

That’s awful. Vercel has pretty much a monopoly on the hybrid framework space now, and it’s going to ruin everything. NEVER did a monopoly do any good to anyone but its holder. Props to Vercel, I guess. Enjoy your champagne. Increased the share holder value, job well done! Clap, clap.

Moat's not deep, this doesn't make it much better.

Re: NuxtLabs is joining Vercel

#48

Post by etchalon »

kelthuzad wrote: post #37
etchalon wrote: post #23

Earlier quoted context omitted.

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"

From a cursory reading of Astro's docs their model/philosophy seems to be more like "fast by default." So their philosophy is to start with zero client-side javascript, even when one is using components from javascript-heavy frameworks like React or Vue. Interactivity is apparently something one has to explicitly opt-in to by adding a client:* directive, rather than it being the default. The migration guide states, "…

I think you're fundamentally missing the difference between these two frameworks.

Re: NuxtLabs is joining Vercel

#49

Post by etchalon »

pier25 wrote: post #32
etchalon wrote: post #21

Earlier quoted context omitted.

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

No universe, huh? https://imgur.com/MxSrgj1

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