4 ms·

The fact I can just run `vercel` on many frontend projects, and it just works without having to think about iam, policies, service accounts, s3 configuration, c

• akira2501 2y ago
  > on many frontend projects, and it just works without having to think about iam, policies, service accounts, s3 configuration, cloudfront. Sure, but if you're going to use it on "many" projects, then just learning these things once and building an appropriate abstraction layer for them pays for itself very quickly. The premium for the "vercel flavored" wrapper around these necessary components is way too high.
  • gitgud 2y ago
    > then just learning these things once and building an appropriate abstraction layer for them pays for itself very quickly No point building an abstraction, if none of your projects make money… it’s wiser to focus on building something people will pay for
    • akira2501 2y ago
      > if none of your projects make money If your plan is for none of them to /ever/ make money, then this is logical. If your hope is that one of them somehow does make money, you'll probably want your code to be flexible enough to be moved to a platform that won't destroy your profit margin over pay-as-you-go billing. At which point, the investment of effort will have paid for itself. There's the problems you currently have, then there's the problems you want to have.
    • meiraleal 2y ago
      Ironically, people would pay for it as a cheaper alternative to Vercel. Next step they would just need to capture some famous open source project.