Ask HN: Risk of Vendor Lock-In with Next.js

1 pointsStefanWestfal2y ago2 comments

I appreciate the new features that Next.js is rolling out, such as the app router. However, I'm curious if there's a risk of future features working exclusively, or at least best, when hosted on Vercel. This could be a strategic move by Vercel, creating vendor lock-in to get people to host on their platform. On the other hand, it might not pose any issues, and Next.js may perform well on other platforms after overcoming initial obstacles. Do you believe that choosing Next.js could lead to vendor lock-in in the mid-to-long term?

2 comments

flagged242y ago

I think app router and react server components optimize for serverless/edge. That optimization comes at a cost that I think is best visible in this GitHub issue: https://github.com/vercel/next.js/discussions/42732

As someone who runs Next.js with a custom server setup on a VPS, I think the haydays of Next.js are behind us. I'm looking to simplify my frontend stack. I love how stable my Node.js backend is and want the same for my frontend.

fintechie2y ago

You can bet that their ultimate goal is increasing the number of customers... Personally I've grown tired of riding the hype du jour, this whole saga of server/client components reminds me of Meteor.js. We keep going in circles.

j / k navigate · click thread line to collapse

Ask HN: Risk of Vendor Lock-In with Next.js

1 pointsStefanWestfal2y ago2 comments

2 comments

flagged242y ago

fintechie2y ago

j / k navigate · click thread line to collapse