I always see such negative responses when HN brings up software bloat ("why is your static site measured in megabytes").

Now that we have an abundance of compute and most people run devices more powerful than the devices that put man on the moon, it's easier than ever to make app bloat, especially when using a framework like Electron or React Native.

People take it personally when you say they write poor quality software, but it's not a personal attack, it's an observation of modern software practices.

And I'm guilty of this, mainly because I work for companies that prioritize speed of development over quality of software, and I suspect most developers are in this trap.

Merely reducing external dependencies causes people to come out in rashes.

A large proportion of “developers” enjoy build vs buy arguments far too much.

“We” are the ones making the architecture and the technical specs of these services. Taking care for it to still work when your favourite FAANGMC is down seems like something we can help with.

Or _you_ aren't down, but a third-party you depend on is (auth0, payment gateway, what have you), and you invested a lot of time and effort into being reliable, but it was all for less than nothing, because your website loads but customers can't purchase, and they associate the problem with you, not with the AWS outage.

Right. Whereas if we get whacked with a random DDoS, that's my fault.

Unfortunately Anubis doesn't help where my pipe to the internet isn't fat enough to just eat up all the bandwidth that the attacker has available. Renting tens of terabits of capacity isn't cheap and DDoS attacks nowadays are in the scale of that. BunnyCDN's DDoS protection is unfortunately too basic to filter out anything that's ever so slightly more sophisticated. Cloudflare's flexibility in terms of custom rulesets and their global pre-trained rulesets (based on attacks they've seen in the past) is imo just unbeatable at this time.

bunny.net is not reachable for me too... really funny

https://imgur.com/a/8gh3hOb

Why do people on a technical website suggest this? It's literally the same snake oil as Cloudflare. Both have an endgame of total web DRM; they want to make sure users "aren't bots". Each time the DRM is cracked, they will increase its complexity of the "verifier". You will be running arbitrary code in your big 4 browser to ensure you're running a certified big 4 browser, with 10 trillion man hours of development, on an certified OS.

That was possible when a DDos was usually still an occasional attack by a bad actor.

Most time I get ddosed now it's either Facebook directly, Something something Azure or any random AI.

So accept that your customers won't be able to use your services whenever some russian teenager is bored? Yeah, good luck with justifying that choice.

99.999% availability is around 5 minutes or so of downtime per year.

> Providers need to be more aware of their global impact in outages

So you think the problem is they aren't "aware"?

> 30 minutes of downtime

> this is tenable as long as these services are reliable

do you hear yourself, this is supposed to be a distributed CDN. imagine if HTTP had 30 minutes of downtime a year.

and judging by the HN post age, we're now past minute 60 of this incident.

> especially for AWS

CF can be just as difficult if not more to migrate off of especially when using things like durable objects