Citing Aphyr's analysis of a pre-release version of Redis-Raft as though it applied to a shipped product is so disingenuous as to invalidate this whole post. The very next sentence after the one he quoted is
> We emphasize, again, that these are all internal development builds: Redis-Raft has no production users, so the real-world impact of these issues is negligible.
and of the 21 errors he found, 20 were already fixed before he published his review.
The main value I get from sqlalchemy is parsing the result into useful structures. Getting the two models out of a join, prefetching related objects, etc. Though I much prefer rust diesel’s approach of no lazy queries (prefetches returned as list[tuple[object, list[related_object]], though diesel had other issues for me). My policy with sqlachemy is to unwrap all results to that if I’m passing/returning them. No relationship access outside of the function making the query.
Yeah, same – mine gives Claude a proxy to the host's Docker socket that disallows mounting anything outside the dev dirs or starting a --privileged container, so it can run tests.
And for my iPod touch! I was prepared to keep using it around the house – it's so much lighter than a phone – but I was worried about leaving it logged into iCloud Keychain if it wasn't going to get this fix.
The "funniest" thing about this is that in any other context, this administration absolutely insists that everyone should be called only by their legal name, not any other name that they prefer because they think it better suits their identity.
> We emphasize, again, that these are all internal development builds: Redis-Raft has no production users, so the real-world impact of these issues is negligible.
and of the 21 errors he found, 20 were already fixed before he published his review.