111–120 of 144 posts
Earlier quoted context omitted.
Cloudflare own and run the services they’re offering whereas it looks like Vercal storage is just other people’s services rebranded
Users don't care about that.
I'm wondering why vercel chose upstash vs cloudflare kv store? I've worked on very large deployments of cloudflare workers + kv store and the performance is amazing (and pricing). It would seem to me that upstash would add hops/latency vs cloudflare kv store?
No serious company is ever going to use these criminally expensive software, so it's quite clear what their target market is. Unfortunately, they have such a strong hold of the Twitter and Youtube space with their army of cringey influencers.
This company does nothing but a disservice to the next generation of web developers. Really a shame.
Am I the only Luddite who 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?
It limiting your options can be a good thing, people can just ship instead of being stuck in analysis paralysis forever.
I also found it quite nice entry point for newbie developers. I’ve been donating my time to help out new developers, and learning deployment (it isn’t ”basic” for complete newbies) on top of everything can be daunting. Vercel lets them deploy for free and effortlessly so that they can show off what they’ve learned.
That being said, I personally wouldn’t touch Vercel for any serious work either.
Earlier quoted context omitted.
Does this mean I have to potentially deal with two vendors when there is an outage? Awesome!
That's their secret, Cap. You've always had to deal with multiple vendors when there's an outage. Vercel has never made it a secret that they're standing on the shoulders of Tier 1 Cloud giants for their hosting backend.
> 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 really can't stand this company and it's business model. It preys on inexperienced engineers, locks them into an ecosystem of SaaS products that abstracts away important concepts they should learn, and charges an absolutely absurd premium while doing it. No serious company is ever going to use these criminally expensive software, so it's quite clear what their target market is. Unfortunately, they have such a stron…
Am I the only Luddite who 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?
Yes their DX is technically “over complicating basic things to extract money from chump developers” but it lets users just write code and automate away everything else with couple of click. It limiting your options can be a good thing, people can just ship instead of being stuck in analysis paralysis forever. I also found it quite nice entry point for newbie developers. I’ve been donating my time to help out new deve…
Am I the only Luddite who 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?
Earlier quoted context omitted.
This is why at Xata we have developed our own ORM-like SDK for TypeScript and we store migration files in the repo. The SDK is very lightweight so it runs in any serverless runtime. It also means we can create DB branches on the fly for each PR, with whatever schema is in the repo, and when the PR is merged, the `main` branch gets migrated automatically.
I don't quite follow, but I totally believe that solutions to these problems can be made and maybe your solution really does work well. The issue is that solutions here are not standard yet and thus there will not be much collective knowledge to draw upon. I'd much rather ask engineers to fix age-old RDBMS issues than novel ones that are unsearchable with solutions whose repercussions are not yet known. There's also…
I definitely understand this. One step at a time, but I think we can move incrementally to a workflow that is much better that what we have today, especially around the DB schema migrations. There's also no reason for this to not work for RDBMS, in fact we're based on Postgres ourselves.