Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Sure.

1. Last paragraph of that link you posted

2. https://github.com/vercel/next.js/issues/8851

3.https://github.com/vercel/next.js/issues/10713

4. Many similar discussions to this one here on hackernews.



sort by: page size:




Next.js Layouts RFC Discussion is Here > https://github.com/vercel/next.js/discussions/37136

I guess you’re talking about Vercel.com instead of Next.JS, right?



Lee from Vercel here. Happy to answer any questions :) If you have any suggestions for how we can improve Next.js, let me know!

Just for fun I wrote this prompt "vercel monopolizes nextjs by only allowing certain features on their platform such as"

ChatGPT4:

1. Incremental Static Regeneration (ISR): This feature allows developers to update static pages at runtime without having to rebuild the entire website. Vercel has optimized its platform to support ISR, making it an exclusive feature for Next.js applications deployed on Vercel.

2. Real-time Feedback: Vercel's platform provides real-time feedback during development, allowing developers to see the changes they make in their code instantly. This feature is exclusive to Vercel, making it a significant advantage for developers using Next.js on their platform.

3. Edge Functions: Vercel offers Edge Functions, which allow developers to run serverless functions at the edge of their network, providing low-latency responses to user requests. This feature is particularly useful for Next.js applications that require server-side rendering and is exclusive to Vercel's platform.

4. Preview Mode: Vercel's platform supports Next.js's Preview Mode, which allows developers to preview draft content changes without affecting the live site. This

-------------------------------------------------------

Claude v1.3

That is not correct. Vercel does not monopolize Next.js or limit features to their platform.

Next.js is an open source framework that can be deployed anywhere. Some key facts:

1. Next.js is MIT licensed and the source code is available on GitHub for anyone to use, modify, and deploy.

2. Next.js apps can be deployed on any hosting provider or infrastructure. This includes:

- Vercel (the creators of Next.js) - AWS - GCP - Azure - DigitalOcean - Heroku - Your own servers, etc.

3. All Next.js features work regardless of where you deploy. This includes:

- Static Generation (SSG) - Server Side Rendering (SSR) - Incremental Static Regeneration (ISR) - API Routes - Image Optimization - Font Optimization


"allows" as in "you can hack it to support that use case" [1].

Moreover, Nextjs's devs are increasingly ignoring that use case to the point where it is unclear if you'll hit a roadblock where you can't update anymore because the required amount of hacking is just too much to continue using it like that.

https://github.com/vercel/next.js/issues/5054


> If you're new here, I'm Lee. I work on Next.js. I've also made some courses about using Next.js before I joined Vercel.

This alone should be further up the post…


Still waiting for the long-promised *non*-Next.js examples, though:

https://github.com/vercel/examples/tree/main/edge-functions

:-/


I could, though it would be summarised in about one sentence: "NextJS and Vercel make everything stupidly easy."

Can you give examples of times NextJS was changed to solely benefit Vercel?

NextJS is an open-source framework under the MIT license, so if Vercel ever did anything to compromise NextJS, it could just be forked, but to my knowledge and experience with NextJS, they've provided and continue to provide an awesome framework/ecosystem around React.


I've been enjoying working with Next.js [1] in the last couple of years, and especially with a serverless architecture, deploying to Vercel [2].

I've got most of my projects working in this setup now, and so as I was starting to work on a couple of things more recently, I decided to pick one that I've had in production for a few months without issues, strip it to the bare essentials, and update all dependencies.

It's in GitHub at https://github.com/BrunoBernardino/nextjs-boilerplate-simple .

If people find these useful, I'll start a collection and release some with basic stuff like connecting to MongoDB, sending emails via Mailgun, passwordless user login, and more.

Let me know what would you like seeing!

I hope you enjoy it.

Thank you for your attention and kindness. I really appreciate it!

[1] https://nextjs.org

[2] https://vercel.com


I suppose. But it's totally viable to use Next.js without using anything from Vercel.

Their very first release was v1.0.0 [1]; four years later they are at v10. It's official, v10 is the new v1.0.

[1] https://github.com/vercel/next.js/releases?after=1.0.2


This looks like what Vercel is to Next.js

next

Legal | privacy