101–110 of 144 posts
I really wish this had been Fly or Supabase. I’ve used Neon and it is much less performant and often times completely non responsive. My company already uses Cloudflare so the rest isn’t a big change for us.
Earlier quoted context omitted.
Classic VC-backed B2B play. The trick, however, is finding a "wedge" people actually want on its own. Unfortunately that seems to be easier said than done.
There’s a lot of magic with Vercel, but I think the true “wedge” was clear to many people: DX. The trick was really the execution, which they nailed. They realized early that there was a whole class of developers out there, many of them quite talented, who couldn’t stand SSH’ing into Linux boxes, configuring htaccess files, installing SSL certificates, etc. Many of these developers also worked at big companies, and h…
Earlier quoted context omitted.
I want to disagree but thanks be to the lack of agreed definitions I will agree.
i was being intentionally stupid, but based on this pricing I'm forced to think that Vercel et al. are just praying on junior/inexperienced devs. This is like a 4x premium (maybe more) over AWS, and that is already a huge premium.
Deploys Go app containers. Pick a cloud. Use whatever they offer.
Deploys static JS to cdn
Calls it a day.
I really do not understand these tools. Who is using them?
I’ve built and worked on apps used by millions of people. Really don’t understand where the benefit is or if people are just over complicating basic things to extract money from chump developers?
> Simultaneously, as the world moves away from monolithic architectures to composable ones It's been the opposite for me. Back around 2015-2016 I was very excited about cloud functions, serverless, etc, but these past years I've gone back to mostly running VMs with regular persistent apps. Complexity has gone down considerably and there's zero lock in. With Docker I have full control over the platform and can run the…
Either way, I'm back on the monolith train and probably won't look back for a while.
I looked into serverless postgres offerings a few months ago and came to realize that while it is possible, it doesn't appear that we have figured out how to develop with it as well as we have with traditional postgres. ORMs are fairly incompatible with serverless postgres, and schema migrations are difficult to handle because you have an unknown number of asynchronously updated copies of your code spread around the…
I had the same experience. I have a Next.js app and Postgres DB I host on a server-ful PaaS. I hosted the same app on Vercel with Neon DB and the app was significantly slower. The first time Neon is connected, it will be slow so I was prepared for that. Consequent reloads and using the app normally was slow too. Maybe integrating Neon directly with Vercel will fix these issues. I just don’t see the value prop to use…
Earlier quoted context omitted.
This is also my concern. If the happy path is Serverless/Edge (on Vercel) with React Server Components I'm in for a big rewrite. I'm holding off any new investments in the Next.js ecosystem until the dust settles or a more community focused and stable alternative arises.
What are the leading alternatives? I know about RemixJS, but not too up to date on others and how each of these compare against each other.
My impression on Remix is fairly solid, but it doesn’t have quite the “just write and deploy” appeal that Vercel’s done quite a good job with, and they’re somewhat trailing behind Next.js in terms of tracking newer React features (which, in practical terms, doesn’t matter much, since even beta Next.js features tend to ship in a very alpha state of quality).
That said, if you’re willing to sweat a bit on getting something deployed, Remix delivers a pretty good experience overall.
> Simultaneously, as the world moves away from monolithic architectures to composable ones It's been the opposite for me. Back around 2015-2016 I was very excited about cloud functions, serverless, etc, but these past years I've gone back to mostly running VMs with regular persistent apps. Complexity has gone down considerably and there's zero lock in. With Docker I have full control over the platform and can run the…
I'm right with you. This stuff was exciting like ~5 years ago. I did several projects with Firebase functions as well as Lambda. Randomly on a few of my projects, the functions don't work anymore. Although I haven't touched it in like 4 years. Either way, I'm back on the monolith train and probably won't look back for a while.
Yeah that happened to me like a year or two ago. Google changed something on the platform running my functions and my app stopped working without any notice.