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

We Need To Talk About Vercel

maxcountryman.com

Post reply on HN
Print view View original

81–90 of 161 posts

Re: We Need To Talk About Vercel

#81

Post by benjaminwootton »

leerob wrote: post #30
flimsypremise wrote: post #28

My sense of Vercel (mostly from working with NextJS) is that they are more interested in appearing to support an open source framework while making their product as difficult to interoperate with other technologies as possible in an attempt to lock users into their platform and hopefully pay for it.

Hey, I'm on the team at Vercel. What could we do better? Open to your feedback. Our platform integrates with 30+ frameworks ( https://vercel.com/docs/frameworks ), we directly fund the development of Next.js and Svelte, and we sponsor Nuxt, Astro, Solid, and more.

I was and am a big fan of Vercel but I hated that billing situation a few days ago. You shouldn’t need your post to blow up on social media for support to acknowledge a billing error.

Re: We Need To Talk About Vercel

#82

Post by re-thc »

ranguna wrote: post #76
locustous wrote: post #46

Earlier quoted context omitted.

Hetzner is cheaper unless you are serving a sizable asset with R2. R2 costs per call. That cost is more than most web bundle size assets will be at Hetzner egress pricing.

Didn't know hetzner had a fully managed global caching solution, nice.

Any links to it? Can't find 1 on the website.

Re: We Need To Talk About Vercel

#83

Post by re-thc »

jacooper wrote: post #25
ilrwbwrkhv wrote: post #8

If anyone needs a CDN, please use BunnyCDN. I have tried almost every other major CDN and it just blows everything else out of the water. Regarding Vercel, they do have quite poor support so it doesn't feel rock solid and dependable. They are a great start though, but then ideally you should just switch to bare metal on Hetzner or something when you are earning serious money from your business.

Honestly nothing compares to bandwidth free expenses with cloudflare especially with cloudflare R2. Also having different pricing for every region is very annoying.

Cloudflare isn't 100% free unless it's only the US. Non business accounts get re-routed on major ISPs in quite a few countries. Quite an upfront cost.

Re: We Need To Talk About Vercel

#84

Post by Etheryte »

leerob wrote: post #24
pier25 wrote: post #23

Does any CDN support stale-while-revalidate? I know Cloudflare doesn't. I thought Vercel did but apparently not.

Vercel does: https://news.ycombinator.com/item?id=35508529

You don't need to go linking to your marketing comment in every possible subthread for damage control, it isn't nice to spam.

Re: We Need To Talk About Vercel

#85

Post by sshine »

Aeolun wrote: post #62
Kevcmk wrote: post #60

Earlier quoted context omitted.

Which one, the go ahead and "define your own custom loader"? You mean re-implement the image export that is sitting right there in their express server... from scratch? Hah. NextJS won't let you export their optimized images in a static site export because they want _everything_ running through their Express server. Why's that great for them? Because they get to charge you for image bandwidth and image optimization.…

To be fair, you can optimize images yourself, or just not optimize them at all.

Or use a web framework that gives you optimised images that aren’t vendor-locked.

The point is that the library artificially limits capability because it benefits a particular vendor model, not the user.

Re: We Need To Talk About Vercel

#86

Post by andrewingram »

re-thc wrote: post #79
philsnow wrote: post #63

Earlier quoted context omitted.

> they have effectively acquihired React (Zuck's mistake). no moat? I honestly don't even know what are you saying, is it that Vercel hiring the React folks makes Vercel untouchable somehow? I see a complete disconnect between the two things. If anything, the "acquihire" could well lead to those React folks doing a job search because Vercel doesn't have a high switching-away-from cost and keeps dropping the ball PR-w…

There is some merit to it. Maybe not that comment but on Vercel React in general. Even React new docs are promoting NextJs vs something neutral.

The vast majority of React’s core team still works for Meta, and I think the sentiment that a small handful of “famous” hires amounts to acqui-hiring the team is frankly a little insulting to the rest of them.

Re: We Need To Talk About Vercel

#87

Post by porker »

ilrwbwrkhv wrote: post #8

If anyone needs a CDN, please use BunnyCDN. I have tried almost every other major CDN and it just blows everything else out of the water. Regarding Vercel, they do have quite poor support so it doesn't feel rock solid and dependable. They are a great start though, but then ideally you should just switch to bare metal on Hetzner or something when you are earning serious money from your business.

Better than Fastly?

Re: We Need To Talk About Vercel

#88

Post by mkl95 »

I don't dislike Vercel specifically, but I dislike opaque businesses that masquerade as open source champions. Also, I wish fewer devs were OK with "advanced frontend stuff" being such a leaky abstraction.

Re: We Need To Talk About Vercel

#89

Post by lungeloslx »

random_rants wrote: post #77

What the hell. You have a page with a 150 jobs and a form. You basically don't need anything more than an html editor. We need to talk about how we do software architecture and technology choices today. In the time you played around with CDN stuff you easily could build a company listing, fixed your footer and header links, thinking about a pricing, build an apply-form, fixed/build job notifications, ...

While I may myself not have a complex setup for something that looks so simple on the surface, I think people here need to stop assuming they know everyone’s purpose for building software.

Maybe the author intentionally set things up so they can have a low stakes system to learn about these technologies and improve their knowledge. This post is about Vercel and their poor practices. Let’s stay on topic and actually ask the author why such a complex setup instead of assuming you know and speaking off the cuff with criticism

Re: We Need To Talk About Vercel

#90

Post by pcthrowaway »

detaro wrote: post #44
Kevcmk wrote: post #38

Vercel is deceitful. The Image/img fiasco really pulled the covers off for vercel for me. I have migrated all my work off of the platform. NextJS’ lint strategically dissuades you from using the img tag in favor of the NextJS Image component. If you make the mistake of heeding this advice and migrating to it, you can’t use static site generation—which means you are stuck using their hosting. Here’s one of the most PR…

Lol, silently* replacing the original request with the company response instead of documenting it in the docs is certainly a move. Nice to have all the thumbs-up and heart reactions on the "sorry we don't do it", for sure. Love the " We'd love to hear your feedback " and then locking the discussion too. Not having the feature is one thing, but why not properly document that and the (by now existing) workarounds? * ye…

Ugh.. that is sneaky
Post reply on HN