4 ms·

I'm not really sure where the comment on Vercel platform lock-in is coming from. Personally I've deployed Next apps on Cloudflare Pages/Netlify, and I have mult

I'm not really sure where the comment on Vercel platform lock-in is coming from. Personally I've deployed Next apps on Cloudflare Pages/Netlify, and I have multiple Next apps at work are all deployed via AWS codebuild or Github Actions (all hosted on AWS). The process is very straightforward and requires little to no extra steps when compared to Vercel.

BoorishBears 3y ago
It's coming from the fact Next.js is all in on serverless, but the reference implementation for deploying it in a serverless environment is closed-source. It's certainly possible you just don't use any of the features they're pushing in that direction, but I mean, they literally dropped basic Request compat just to enable serverless runtimes, and you can't use an img tag without being warned to use their Image Optimization feature, which has no open implementations... Pretty much, most of the energy being spent on Next.js development is towards serverless deploys which use a build format that has to be reverse engineered by outside parties.
- k4rli 3y ago
  How is the implementation not open? They have it all on Github.
  - BoorishBears 3y ago
    No they don't, hence projects like https://open-next.js.org/ https://open-next.js.org/ and the multitude of stories of 3rd party serverless offerings being half-broken. They also keep breaking at time goes on since they're playing catch up on the build output: https://www.reddit.com/r/nextjs/comments/1685dyr/avoid_aws_amplify_at_all_cost_its_fraud/ https://www.reddit.com/r/nextjs/comments/1685dyr/avoid_aws_a... https://www.reddit.com/r/nextjs/comments/160ui01/is_aws_amplify_good_for_hosting_nextjs/ https://www.reddit.com/r/nextjs/comments/160ui01/is_aws_ampl... https://betterprogramming.pub/beware-of-next-js-on-aws-amplify-5a1286db2a6a https://betterprogramming.pub/beware-of-next-js-on-aws-ampli... _ To actually use the build output format, you need an implementation that Vercel does not open source. Compare that to Remix which maintains an open reference implementation for their adapter format, which in turn makes supporting additional platforms incredibly simple.
- 5Qn8mNbc2FNCiVV 3y ago
  It's not all in on serverless and saying so is spreading misinformation. You can use (almost) all their backend features as if it's a single server (which it is in the end) and you can also use their image tag when self-hosting and it processes the images for you. If you're annoyed and don't want to use their image tag, then disable the linting rule. However after having used it for a large scale e-commerce store I'm gonna be honest: It works damn good and not paying for Cloudinary or something along those lines is really nice There are SOME questionable choices like the middleware only being compatible with an edge runtime that can't be turned off, but apart from that one it really is like any other SSR framework.... Edit: added an almost because well, middleware is pretty bad-ish

BoorishBears 3y ago

It's coming from the fact Next.js is all in on serverless, but the reference implementation for deploying it in a serverless environment is closed-source. It's certainly possible you just don't use any of the features they're pushing in that direction, but I mean, they literally dropped basic Request compat just to enable serverless runtimes, and you can't use an img tag without being warned to use their Image Optimization feature, which has no open implementations... Pretty much, most of the energy being spent on Next.js development is towards serverless deploys which use a build format that has to be reverse engineered by outside parties.

k4rli 3y ago
How is the implementation not open? They have it all on Github.
- BoorishBears 3y ago
  No they don't, hence projects like https://open-next.js.org/ https://open-next.js.org/ and the multitude of stories of 3rd party serverless offerings being half-broken. They also keep breaking at time goes on since they're playing catch up on the build output: https://www.reddit.com/r/nextjs/comments/1685dyr/avoid_aws_amplify_at_all_cost_its_fraud/ https://www.reddit.com/r/nextjs/comments/1685dyr/avoid_aws_a... https://www.reddit.com/r/nextjs/comments/160ui01/is_aws_amplify_good_for_hosting_nextjs/ https://www.reddit.com/r/nextjs/comments/160ui01/is_aws_ampl... https://betterprogramming.pub/beware-of-next-js-on-aws-amplify-5a1286db2a6a https://betterprogramming.pub/beware-of-next-js-on-aws-ampli... _ To actually use the build output format, you need an implementation that Vercel does not open source. Compare that to Remix which maintains an open reference implementation for their adapter format, which in turn makes supporting additional platforms incredibly simple.
5Qn8mNbc2FNCiVV 3y ago
It's not all in on serverless and saying so is spreading misinformation. You can use (almost) all their backend features as if it's a single server (which it is in the end) and you can also use their image tag when self-hosting and it processes the images for you. If you're annoyed and don't want to use their image tag, then disable the linting rule. However after having used it for a large scale e-commerce store I'm gonna be honest: It works damn good and not paying for Cloudinary or something along those lines is really nice There are SOME questionable choices like the middleware only being compatible with an edge runtime that can't be turned off, but apart from that one it really is like any other SSR framework.... Edit: added an almost because well, middleware is pretty bad-ish