llambda

V unq gur evtug nafjre znal gvzrf ohg snvyrq gb pbafvqre gur cbffvovyvgl bs nygreangr sbezf.

While I understand your point is likely that sidewalks would come before later advancements (like support for bikes) I want to make it clear that bikes do not belong on sidewalks.

If you ride a bike please ride it in the street with other vehicles. This is the law in some jurisdictions (such as where I live) but frequently ignored.

Failure to do this poses a serious risk to pedestrians. Please do not use sidewalks as an alternative road.

Well, no.

That assumes that offspring follow their parents' ideology directly. While many may, some will not.

What we've seen over time is a defection from e.g. religious right upbringing, especially as offspring move into denser urban areas.

I'm coming around to building everything for a VPS from the outset. There's a lot of upside to VPSes, such as:

1. Can be purchased as a fixed cost, usually at a rate that's much cheaper than on-demand pricing, and especially serverless--this tends to only get better with time as competition keeps prices low

2. It's "just" a Unix/Windows/Mac box, so the issues with runtime constraints you mention are bounded differently (and often more favorably); serverless is also just a box, but the constraints tend to be more onerous and limiting and it's not usually accessible in the same way

3. With containers, it's trivial to move between providers, so the hardware itself becomes fungible

4. On containers, I'm having a great time shipping Docker Compose configs--this works really well for the scale of application I'm targeting while avoiding the dreaded complexity of e.g. k8s

5. There's decades of high quality tooling already built and battle tested which makes operating VPSes much easier; the fact you can SSH into the machine, for instance, has huge leverage as an solo person working on independent products

Going forward, I'm planning to skip edge compute altogether unless there's a really compelling reason to want it. I should also mention that when a VPS is paired with a CDN, you can layer on bits of "edge compute" where it's warranted; or, you know, use it to cache static assets close to your users. :)

All-in-all it's kind of a funny return to where I started ~20 years or so ago with web development.

This is incredible. If I understand the thread, that >$22,000 surprise bill was not forgiven by Vercel and the most they're willing to do is offer a 25% discount.

Is Vercel a business or a scam masquerading as a tech company?

If a company needs to stoop to this level of billing shenanigans to make money, I have my doubts...

Actually I reached out to you asking for a comment which I could add to the article, not for your technical support.

I was surprised and I have to admit a bit dismayed to watch you throw yourself into the fray on a Sunday. The technical issues, which in fact persist, are at this point an aside to the way Vercel has handled this issue.

I'm currently stuck in their support hell and have been told:

1. My issue is not real

2. Okay, your issue is real, but because I'm not paying $$$ we're going to ignore you

3. I should do free work for Vercel and poll their community forums to see how widespread the issue is

4. Their support is only trained to handle frontend issues and because this is an issue with their CDN it's expected that they'll respond incompetently

5. They'll escalate with their CDN team and respond in one week (that was over a month ago, no follow up whatsoever)

It's hard to take Vercel seriously. As a toy, it's probably fine. But I'll ultimately move this project off of their CDN product as soon as it reaches costly volume.