Getting back from holiday in a few hours and the weather is cold? Turn the heating on from your app before you get back. Wow. Life changing. Don’t have a use case for most things being connected but thermostat really isn’t that crazy IMO.

Good for you babes, but I wouldn’t trust you to wipe your arse if you can’t even keep data consistent

Jesus fucking Christ man, not everyone’s use cases are your use cases. Get some real world experience. If you don’t know the kinda shit you have to actually do, it’s easy, but sometimes the show’s just gotta go on

deleted by creator

Lol what an absurd take. A transaction is a sequence of operations, not a single one, so even small tables can meet that threshold with enough query logic. I guess you’re unfamiliar with medium to large datasets, but it’s not uncommon to use the aggregate functions that SQL provides in real world situations, and on large tables that can easily reasonably exceed 1s. Toy my arse. Go play with yourself

Although this is no surprise tbh because apparently you don’t understand why transactions are even necessary. Benchmarks shmenchmarks. Whether it works is more important.

I do not apologise for the downvote because this is smug shit only a junior would say

But adding it to an 80ms operation is. If your operation is 0.5ms it’s either a read on a small table, or maybe a single write – transaction isolation wouldn’t even be relevant there. You’re right that I did mean consistency rather that integrity though, slip of the terminology, but not really worth quibbling over. The point I meant was that I like my data to make sense, a funny quirk of mine.

Well it depends how much data integrity is worth to you, and how your system works. Every write in postgres is already a transaction - when you can get away with simple crud stuff, often there’s nothing to do, you have transactionality already. Transaction isolation levels are where db operation costs might change under concurrent conflicting writes but you can tune that by ensuring single-writer-per-partition or whatever in your server logic and it might add a ms or two. OTOH if you have heavy contestation it can be much more expensive. The performance implications are complicated but can certainly kept to a fraction of overall cost depending on your workload!

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.

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?

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

Is that Jen? It looks a lot like her but I suck at facial recognition

I’d disagree with that argument and draw an analogy with the short reactive pathways triggered by e.g. that thing where you tap a knee with a hammer and it jerks; I don’t think the reaction loop there counts as a sense, and only when you add in the CNS and perception of it does it even connect to one. But it’s hardly a cut’n’dried argument and I’m sure there’s a lot left to plausibly disagree on here

What’s a tree’s brain in this analogy?

deleted by creator

https://blog.giovanh.com/blog/2025/10/14/a-hack-is-not-enough/ this article makes a sadly excellent point in response to you here. Fair warning: it’s long. But even if you dip out early I assume you’ll get the point being made

Samesies