I remember ext2 to ext3. Journaling was all the rage!

PEBKAC

Stupid long horses

Yeah, and not adapting accumulates the kind of tech debt that pays my bills when I have to come clean up. If everyone was doing their job I would be in a different like of work, a less profitable one for sure.

Nu-uh, I have it on good authority that rainbows were invented by a guy in a boat with some animals or something.

Millions of hundreds, some of them!

Convenience

Mooooom, I’ve been hacked!

It is, thanks for the entertainment.

Exactly my point. Wrong technology. If your operation takes more than 1s and you just accept it, you are not very good at your job. No worries, more job security for me!

I would recommend reading a few books, but given that you couldn’t even read my first post about when to use transactions, it’s futile.

Lol

Everyone is behind at least one NAT, the wifi router.

My ISP doesn’t know which os I’m using, I behind two NATs and a proxy…

Everyone I don’t agree with is a bot!

If your single operations take 80ms either it’s a toy app or someone didn’t do their job (unoptimized queries, wrong technology, wrong modeling, etc).

Again, not data integrity (Error correction) but consistency (aCid). Adding two milliseconds to a half a millisecond operation is by no means cheap…

“Pretty cheap” is very subjective…

As long as the database is acid restarts should not be a factor. Data integrity is not helped by transactions, you would need error correcting codes for that. Plus the effect on performance is quite notable on all dbs I’ve worked with.

I get that this is a joke, but…

… ackshually it should almost never be a transaction only when there’s absolutely no other option, because transactions kill your performance.

Which is the norm, not the exception. Really good devs (which I’m not) are capable of delivering clean, modular, readable and maintainable code under pressure, working in a team with other people, with unclear requirements.