I would be curious too. I think it comes down to the benefits are there and they're cheap enough that they may as well recommend a more secure approach.

Hey, author here. Pleasure to work on this article. I'd welcome strong opinions :-)

This is all great except it’s all in memory. To really fail safe you need to account for crashes and therefore need a persistent queue

Depending on your performance requirements extra milliseconds of roundtrip to the externalized queue may be too long of a wait. Or you may simply not care enough for an extra piece of infrastructure that you'd need to support, and maybe this is good enough. It's is all about trade offs, no solution fits all use cases.

its always about tradeoffs. one nice compromise position here is that the log is always consistent, so you don't need to wait at all if you don't mind losing the tail on a crash.

What if I'm from the UK and I am still wondering what to click?

Unless I'm being really dumb I don't see an image, all I see is this https://pasteboard.co/hxSXWlzyFepX.png

github have stopped the repo, was working earlier

The code walkthrough was excellent and very elegant

Was hoping for more of a high level technical explanation of how it differs from alternatives in the FAQ

Hopefully this feature request is now fulfilled

Ah thanks for letting me know, that's a very old project and I lost access to that domain because I missed the expiration emails.

Unfortunately, I didn’t take that photo

You don't need overengineered generative AI, just photoshop half of the left-looking and half of the right-looking photo together

Well I've done something now...