HN is a pretty simple, efficient monolithic web application. Some updates might need a restart. It's OK for some web requests to fail during that time. HN isn't life critical with sixtuple nine uptime requirements.

Tbh like 99% of web apps aren’t critical - most of them are for buying something or providing infrastructure to make it easier to buy something anyway. It’s fine if your online shop is down for a few minutes (of course the business won’t see it like that but it’s true)

B&H is doing fine financially and brings their webstore down for each and every Sabbath, even if that happens to be a Black Friday.

https://news.ycombinator.com/item?id=12183263

A sales site being down might lose you a sale. But the simplicity might save you so muh more than that loses you. And often the complexion of high availability infrastructure results in more downtime than it prevents.

For stuff like HN, I like the peek behind the scenes it provides. It's all just software written by some humans and way too often people take themselves and their shitty software way too serious.

Steam, +130 million users, biggest gamming store, multi billion dolar company, is offline every week for a few minutes.

99.999999 is so overated.

It could probably be done with a simple if statement, but I'm guessing that dang enjoys the tradition of doing it manually every year.

I feel like this obsession with zero downtime has gotten a bit silly. Sure, for some things it's damn near required (though I imagine that's fewer things than most people think), but it 100% does not matter even a little bit if HN is unavailable for 10 seconds or so.

I'd rather restart once (ok, twice) a year than keep that code around in production.

It only affects traffic for about 10 seconds.

I’m quite certain you can approach it in any convenient manner

Outcome-billing makes absolute sense! In every case where I have used an LLM to work on a software project, I have been frustrated by the process and end up educating the thing myself. The outcome is that it has learned from me, so I need a place to send my consulting bill.

:)

And standardised within an empire.

> ... you gain binary independence in any medium that understands utf8

Nice work! But if you want something like this in production, base64 only increases the size by 33%.

While providing zero visibility into the contents. I know. Tradeoffs.

Give it a couple days for 18.7.3 to show up (I’m trying this myself) or download the ipsw for ios 18.7.3 and use a computer to install.

I don't believe an IPSW for 18.7.3 was released except for devices that couldn't upgrade to iOS 26. I believe this is done to prevent downgrades.

Apple doesn’t provide IPSWs once the next major version has launched. OTA is the only option.

You can also join the iOS 18 public beta to get the update.

How do you do that? And do you need an AppleID to do so?

If you have the tolerance for betas, indeed

Someone above said that the 18.7.3 you can install as beta is in fact the production build. Disable beta access after that update.

Correct, both are the same build (22H217). BetaWiki has this build labeled as both the RC and the actual release: https://betawiki.net/wiki/IOS_18

I have never seen anyone argue for a ‘switch’ version.

    switch (v) {
     case: 0,2,4,8,…:
       return EVEN;
     case: 1,3,5,7,…:
       return ODD;
     default:
       return IDK;
    }

Slightly less code to generate.

you forgot the logic to strip the final digit and assign it to v.

processing the whole number is absurd

I think the idea is to fill in the ellipses with even/odd numbers, up to 4B.

You know, to save the performance cost of processing the input as a string, and chomping off all but the last character.

Converting to decimal is just as absurd.

All you need is the final binary digit, which incidentally is the most optimal codegen, `v & 1`.

Look at Mr. Rocket Scientist over here...

Likewise, the prince

I think this API makes more sense from another standpoint as well.

You don’t want developers trying to rely on client-only sanitization for user input submitted to the server. Sanitizing while setting a user-face UI makes sense.

Sounds like you have no motivation and want to coast along. You can only do that in software with the right skills. You have to develop skill - you know, “grow.”

If you like stagnant work, you have to find a company requiring that kind of work. Probably not in the software industry.