Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vercel Service Markup

service-markup.vercel.app

Post reply on HN
Print view View original

31–40 of 109 posts

Re: Vercel Service Markup

#31

Post by throwaway4good »

msy wrote: post #24

Vercel raised $300m+ at the top of the market and paid over the odds to hire a ton of JS ecosystem luminaries. Those investors are going want to see a return, not just an eyewatering wage bill. Anyone building on top of their ecosystem is going to get fleeced, they have no other route to possibly justifing their valuation or ever providing a passable return on that capital. Everyone else should be preparing their pla…

Contrary to what we think of ourselves, developers are easily bought off and subject to influencer campaigns.

Re: Vercel Service Markup

#32

Post by huac »

I don't quite understand the convenience, R2 and the other services are already quite easy to use. I wrote a simple wrapper that exposes the same API: https://github.com/stillmatic/storage-wrapper/blob/main/stor...

The wrapper is pretty straightforward, I can see how it's a teensy bit simpler to have Vercel manage things for you, but it's not really much easier...

Re: Vercel Service Markup

#33

Post by 8n4vidtmkvmk »

beginnings wrote: post #20
dlisboa wrote: post #14

Earlier quoted context omitted.

There's a lot more to running your own server than that. I set up a Hetzner VPS just for play one weekend. I forgot all about it and came back a couple days later: it had already been compromised and was being used to mine crypto coin. All because I left something running (related to Docker) which I don't even remember starting. Hardening your servers, ensuring proper port exposure, ensuring upgrades and security pat…

Set up fail2ban then good luck to anyone to anyone trying your address, it's very simple. Ensuring upgrades and security patches is literally running sudo apt update and sudo apt upgrade. Should be a piece of cake for anyone who has been running Linux for a few years.

even that is not so trivial. you'll have downtime during the upgrade and it might not come back up again.

which is why i switched to kubernetes

Re: Vercel Service Markup

#34

Post by 8n4vidtmkvmk »

TobyTheDog123 wrote: post #8

This is a bit of a copy/paste from a comment I made in another thread like three weeks ago[1]: ####### I'm very much starting to distrust these huge companies with infinite product/feature lists and generic marketing-lingo websites. "Vercel is the platform for frontend developers, providing the speed and reliability innovators need to create at the moment of inspiration." Seriously? I want serverless providers that t…

hah. that was exactly my impression too. years ago, they showed a command like "next up" or something and boom your app is deployed. never used it. didn't even look into it, just assumed it would cost an arm and a leg because there's no way they wouldn't add a bunch of markup ontop of a basic vps

Re: Vercel Service Markup

#35

Post by pavlov »

throwaway4good wrote: post #31
msy wrote: post #24

Vercel raised $300m+ at the top of the market and paid over the odds to hire a ton of JS ecosystem luminaries. Those investors are going want to see a return, not just an eyewatering wage bill. Anyone building on top of their ecosystem is going to get fleeced, they have no other route to possibly justifing their valuation or ever providing a passable return on that capital. Everyone else should be preparing their pla…

Contrary to what we think of ourselves, developers are easily bought off and subject to influencer campaigns.

Marketing to developers is so effective specifically because developers imagine themselves immune to marketing.

Re: Vercel Service Markup

#36

Post by reducesuffering »

msy wrote: post #24

Vercel raised $300m+ at the top of the market and paid over the odds to hire a ton of JS ecosystem luminaries. Those investors are going want to see a return, not just an eyewatering wage bill. Anyone building on top of their ecosystem is going to get fleeced, they have no other route to possibly justifing their valuation or ever providing a passable return on that capital. Everyone else should be preparing their pla…

Letting Vercel handle developing half your infra for you. Expensive.

Paying twice the $300k engineers to develop your VC scale app in 2023 using HTML templates or Create React App. Priceless

Re: Vercel Service Markup

#37

Post by egeozcan »

msy wrote: post #24

Vercel raised $300m+ at the top of the market and paid over the odds to hire a ton of JS ecosystem luminaries. Those investors are going want to see a return, not just an eyewatering wage bill. Anyone building on top of their ecosystem is going to get fleeced, they have no other route to possibly justifing their valuation or ever providing a passable return on that capital. Everyone else should be preparing their pla…

> Everyone else should be preparing their plan b for what happens if they impode and Next.js, Turborepo etc development fractures or grinds to a halt.

Isn't next.js too big to fail? Currently we are trying to define a modern stack for our front-end, and I always thought next.js/react to be the next java -> Perhaps Solid.js is much better (IMHO it surely is) but I probably won't get fired for choosing next.

If not, what would be the alternative? I really don't want to restart with the hassle of configuring a js project from scratch. Done it already a thousand times, and that's a thousand times too many :)

Re: Vercel Service Markup

#38

Post by jrudolph »

The appeal of a no-ops workflow for basic frontend apps is there. We’ve got a bunch of static docs sites built with vuepress and docusaurus that are a great fit for this. Not that we can’t whip up a CDN with terraform and a CI/CD pipeline with preview environments, but my team would rather spend its energy on our core product.

However we’ve been badly burned by vercel, netlify and render.com switching their pricing models to user based instead of infrastructure based pricing. We’re migrating to AWS amplify right now, which also happens to be wonderfully integrated into our wider IT landscape with an AWS landing zone, automated internal chargeback etc. It’s 90% the same for our use case and charges only for infra at standard AWS rates.

At this point I’m starting to wonder why it isn’t more popular.

Re: Vercel Service Markup

#39

Post by chrisco255 »

egeozcan wrote: post #37
msy wrote: post #24

Vercel raised $300m+ at the top of the market and paid over the odds to hire a ton of JS ecosystem luminaries. Those investors are going want to see a return, not just an eyewatering wage bill. Anyone building on top of their ecosystem is going to get fleeced, they have no other route to possibly justifing their valuation or ever providing a passable return on that capital. Everyone else should be preparing their pla…

> Everyone else should be preparing their plan b for what happens if they impode and Next.js, Turborepo etc development fractures or grinds to a halt. Isn't next.js too big to fail? Currently we are trying to define a modern stack for our front-end, and I always thought next.js/react to be the next java -> Perhaps Solid.js is much better (IMHO it surely is) but I probably won't get fired for choosing next. If not, wh…

Next.js is open source, forkable, and self deployable.

Re: Vercel Service Markup

#40

Post by chrisco255 »

jrudolph wrote: post #38

The appeal of a no-ops workflow for basic frontend apps is there. We’ve got a bunch of static docs sites built with vuepress and docusaurus that are a great fit for this. Not that we can’t whip up a CDN with terraform and a CI/CD pipeline with preview environments, but my team would rather spend its energy on our core product. However we’ve been badly burned by vercel, netlify and render.com switching their pricing m…

Amplify is the most vendor-specific locked in stack you could possibly choose.

If you don't want to be burned by vendors changing the pricing model on you, don't choose a proprietary stack to build on.

Post reply on HN