Restarts in a server between dB updates that in a sane world would be txns I meant (e.g update A, crash so don't update B). Anyway, in postgres they're pretty cheap in the absence of actual conflict -- more expensive if you have actual cinflicts, obvs.
Yeah but majoras mask earned that right
Actually transactions can be a secomd-layer safety-net for single-responsibility writers to ensure rollback on eg restarts and consistency on loadbalancer redecisions without having much of an impact on performance, and data integrity is usually quite important.
Because the fall of an empire holds deep almost mythic significance and we seek it.
But it won't work that way this time.
What's even cracrazier is knowing that with modernerer technology they have the same ethical assumptions as previously but with more targets and less precision!
Oh hey I do this in jwts too.
I need to encode a lot of permissions
Don't ask
I thought land of the free and home of the brave was Scotland
Have you tried disabling all local Trojans and seeing if that helps?
They absolutely do give wrong answers, as in this classic meme that's way off because of floating point: 
I have never understood how a dev can be comfortable pasting a valid jtw Auth token into a random website to decode it, when there are several very good cli tools that will do this for you locally, faster, and much more securely
One huge advantage of a rolling distro is that generally only one thing can break at a time :)
In return they get an actually secure messing app they can use without having to support it themselves. Which is pretty big.