Live data from Hacker News

Vercel Service Markup

service-markup.vercel.app

51–60 of 109 posts

Re: Vercel Service Markup

#51
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…

> 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 :)

This is the key. For small apps, it's far more effective to pay the premium to not deal with any DevOps. Once an app gets bigger, it'll make sense to spend more time optimizing cost.

I feel like Vercel is the new Heroku circa 2015. I'm hoping it won't follow Heroku's trajectory, but who knows.

Re: Vercel Service Markup

#52

What's the feasibility of replicating Vercel's services and architecture? Without supply side limitations, resellers generally become reduced to commodities over time. This is especially likely with high margin markups, which seems to be the case with Vercel. Is the integration of Next.js on Vercel really that superior to other platforms?

its the marketing

Re: Vercel Service Markup

#53

Earlier quoted context omitted.

> 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.

Those are necessary but not sufficient conditions to having a healthy community which actually continues developing such forks, likely for free if the main company backing the original product goes away. I don't know why people think OSS is a panacea to community development, lots of things are OSS and have few to no contributors.

Re: Vercel Service Markup

#54

This is why I'm bear-ish on Next.JS as a framework. Vercel has some super cool features for Next.Js that are easy to integrate into your app, but is that de-incentivizing Next.JS to implement them in an open way? Vercel is a hyper for-profit and closed platform, is that blocking innovation on Next.JS as an "open-source" framework?

Not really. Next.js is built on Node.js + React (both of which are also open source).

The services Vercel offers have to do with deployment mainly. That's never going to be something a back end or front end framework will help you with directly.

App hosting and deployment has always been a secondary concern. Choice of database, caching, queuing service, etc has also always been a secondary concern apart from a backend/frontend framework.

Re: Vercel Service Markup

#55
post #21

Earlier quoted context omitted.

What percentage of projects ever need that scale? Is it not something crazy like 95% of startups fail? A lot of the successful ones will be in niche categories as well that just don't have scale problems like major social media and tech companies.

Even then most VPS providers offer a load balancer and you can add multiple VPS. It's not so black and white on 1 server vs infinite scaling. There are midpoints.

Can I do that with something like a digital ocean droplet?

Re: Vercel Service Markup

#56
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…

Phoenix LiveView and Elixir and just run it on a server, like Fly.io

Re: Vercel Service Markup

#57

Earlier quoted context omitted.

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

Those are necessary but not sufficient conditions to having a healthy community which actually continues developing such forks, likely for free if the main company backing the original product goes away. I don't know why people think OSS is a panacea to community development, lots of things are OSS and have few to no contributors.

Honestly even the previous stable edition of Next.js before server components would be fine to peg to.

But history has shown that when a framework or backend was sufficiently popular that people did indeed step in to support it. It happened with Node.js itself (which Next is built on) a while back with what was then called io.js, before io.js eventually re-merged with Node.js after the organizational kinks were worked out.

Re: Vercel Service Markup

#58

How does Neon compare with planetscale for free dB hosting? I know fly also has free dB's, but it really isn't a managed dB service.

Neon CEO here.

Much much better :)

On a serious note, Neon is Postgres and Planetscale is MySQL. Neon has 100% compat with Postgres and Planetscale supports most but not all MySQL. Neon has unlimited storage a single node compute. Planetscale is scale out architecture on top of Vitess.

Neon scales to 0 and more cost effective b/c the architecture.

Re: Vercel Service Markup

#59
nextjs is sick and I've always been vercel-hesitant. this is probably an app-specific dilemma that should be solved with spreadsheets to compare costs based on your very specific needs.

Re: Vercel Service Markup

#60
post #21

Earlier quoted context omitted.

What percentage of projects ever need that scale? Is it not something crazy like 95% of startups fail? A lot of the successful ones will be in niche categories as well that just don't have scale problems like major social media and tech companies.

Even then most VPS providers offer a load balancer and you can add multiple VPS. It's not so black and white on 1 server vs infinite scaling. There are midpoints.

Yes, but the second you grow beyond one server the complexity of keeping both in sync, sharding the database, etc etc etc, makes it way more simple to just write a worker and let another company handle it.
Post reply on HN