[tennex]

I like it. This post is the perfect level of detail for people obsessed about UX minutiae.

Personally, I'm not a huge Vercel fan (IMO: lots of hype, business model encourages developer ecosystem lock-in), but this post gave me more trust in the design/UX care that goes into their products (which is a core Vercel strength).

[MaxLeiter]

I am obviously bias as a Vercel employee, but I think we actually do a lot to avoid locking our users in. You can read more about our approach here: https://vercel.com/blog/vercel-the-anti-vendor-lock-in-cloud

If that doesn't alleviate your concerns or you disagree, I'd love to hear your thoughts about how we can improve

[tacker2000]

Are you serious? Your whole business model is built on locking in users and then selling them expensive hosting.

[MaxLeiter]

If you can point out how we actually lock you in, that would be more constructive than blanket accusations. I recommend reading the linked post

[9dev]

You accumulate web frameworks and maintainers similar to the winning strategy at Monopoly, until you have implicit control over entire ecosystems. Whether you actually seize that control or not doesn’t even matter, because you are in a position to do so—by strategic neglect, or increased attention to whatever project supports your current business goals best.

No single entity should have that much power, especially no venture-capital backed one.

[tacker2000]

No sorry, I'm not going to read your PR fluff.

You might want to look at the comments in this thread [1], to get a feeling of the "accusations", as you want to call it... I'm not "accusing" anything, I really couldn't care less, I don't use Vercel/Next.js and never will, but maybe you should read the linked thread, too see how people (at least on HN) see your company.

[1] https://news.ycombinator.com/item?id=45099922

[davidsainez]

I find the existence of opennext convincing proof of lock-in: https://blog.logrocket.com/opennext-next-js-portability/

Personally, I don’t bother with nextjs at all.

[MaxLeiter]

I think the fact that OpenNext can exist speaks to the opposite

A Next.js project can be deployed to a Docker image very easily [1]. If you want to use a provider that has their own infrastructure setup, then yes you need to do some work (that OpenNext does for you). But that's true of practically any framework deploying to a host that does more than just serve the docker container.

[1]: https://nextjs.org/docs/app/getting-started/deploying