Ask HN: Subtle Vercel Vendor Lock?
Basically I have a NextJS 13 project, with typescript, using pages (not the app directory, which would exacerbate this more), and using the bun runtime.
I reuse a lot of skeletons from my prior personal projects and so I have dependencies to update and various things to wrestle with every 6 months or so.
After getting it building on my local environment, I try to deploy to Netlify and there are so many OTHER build issues. Some were valid and worth fixing, others were just an overly strict linter, but then it finally compiled and all the layouts were messed up! Finally I just said screw it and decided to deploy on vercel and it worked out of the box. On both platforms I deploy straight from a github repository, so it is extremely easy to migrate.
At first I was deterred about re-pointing the domain name to another platform, but this actually only took 1 minute. DNS propogation is very fast these days.
Anyway. The ease of using vercel did worry me this time, as it isn't actually so easily passportable to another platform the way it is developed. If I used the latest "app" directory feature of Next Js for project structure, Netlify would have tripped over itself even more. I would like to applaud Vercel for keeping things so seamless, and the coordination with bun and the cross drift to all the major services, but as the Next maintainers too this does concern me.
There are other providers out there, I hear people are really liking Fly.io lately
Just curious what others think!