• 0 posts
  • 78 comments
Joined 3 years ago
Cake day: July 1st, 2023
  • 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!

  • Also it is literally the best language for refactoring. Omg. Anything is available – macros that fold up so tight you can’t see it’s arse, compile type type witnesses for safe access to partial objects, fuckin’ automatic restructuring of auto-generated code, at compile time, to regex hack in the easy fix for a hard problem. It just so flexible, and you can either use that to prevent bugs by making things stricter, or enable incredible things by doing mad unsafe shit (that’s still safe, because you still have the compiler). Wow. What a language.

  • Yeah, every so often there’s an article like this and tbh it always seems to boil down to ‘i couldn’t get a job in it’ lol. Scala isn’t Java or Go, it’s never gonna have as many open roles as those sorts of languages. Doesn’t feel to me like it’s dying – all the libs I depend on have been available for scala 3 for at least a couple of years now, all the ones that aren’t already so feature complete as to warrant ‘stable’ status get regular updates. Kinda don’t like ppl trash talking my favourite language NGL lol 😂