91–100 of 175 posts
Earlier quoted context omitted.
Please, please stop using mono space for quotes. It’s hard to read on small screens. Just > is better.
It’s not hard. It’s actually impossible. I agree, just use >. If I worked for YC as a HN mod I would literally spend a bit of time every day to review as many mono space-using comments I could every day and edit them to use > instead.
We managed to centralize everything, email, git, even the web. I understand 99.99 looks fine, but is somewhat sad to see half the world without email.
Earlier quoted context omitted.
I think this is a false equivalency. If we're talking about "service unavailability", planes break all the time. Houses have to be vacated because of flooding, fire, insect infestation. Brakes do fail. Just like with software, we accept a certain level of risk in exchange for cost/convenience efficiencies (e.g. we don't want our planes to fall out of the sky, but we're okay with getting stranded in phoenix for 24 hou…
Also, brakes contribute to service unavailability. Brake pads need to be replaced on average every 50k miles, which takes the average driver 4 years. And let's say the average length of time your car is at the mechanic's to fix brakes is 3 days. That's 3 days of unavailability every 4 years just for brake pad replacements, or 99.8% availability (two nines!), just because of brake pad repairs. Add in all the other req…
https://inbox.google.com though programmed for termination looks unaffected here. Maybe worth a shot?
Earlier quoted context omitted.
From the first SRE book [1]: "The error budget stems from the observation that 100% is the wrong reliability target for basically everything (pacemakers and anti-lock brakes being notable exceptions). In general, for any software service or system, 100% is not the right reliability target because no user can tell the difference between a system being 100% available and 99.999% available. There are many other systems…
We don't tolerate houses collapsing out of nowhere, brakes failing over the course of normal usage and planes falling out of the sky during routine flights. But for some reason, we HAVE TO tolerate software crapping itself once a year? I don't accept this logic. This is just a sign of how sloppy the industry has become. This is the reason your phone becomes obsolete after 2 years, whereas your car can continue to run…
It's not a good metaphor, even if it looks intriguing at first sight.
Global does not mean "affecting absolutely everyone around the globe (or disc, for the flatearthers out there)". Affecting a "significant subset of users" that are spread around every continent is global and it shows it's not one specific DC, link, or ISP that was affected. The fact that you didn't experience the disruption means absolutely nothing and it's ridiculous to even suggest it does. Especially since there a…
>or disc, for the flatearthers out there I mean, seriously? :)
Earlier quoted context omitted.
It’s not hard. It’s actually impossible. I agree, just use >. If I worked for YC as a HN mod I would literally spend a bit of time every day to review as many mono space-using comments I could every day and edit them to use > instead.
Or write a bot to do it automatically everywhere
We managed to centralize everything, email, git, even the web. I understand 99.99 looks fine, but is somewhat sad to see half the world without email.
Earlier quoted context omitted.
Please, please stop using mono space for quotes. It’s hard to read on small screens. Just > is better.
Why not use italics instead? How does the ">" help? You can put it at the beginning of the paragraph, but lines get re-flowed so you can't put it at the beginning of lines.
https://inbox.google.com though programmed for termination looks unaffected here. Maybe worth a shot?