r1veRRR
@r1veRRR@feddit.de
- Comment on CFCs 8 months ago:
But that isn’t true anymore, right? Renewables are now way cheaper per produced Watt. And still, we’re stuck with people pretending that’s not true.
- Comment on Gamers enraged at Ubisoft for injecting ads into the middle of video games 11 months ago:
Wasn’t that Blizzard/Riot?
- Comment on Is there something better than SQL? 1 year ago:
I’d recommend everyone check out prql-lang.org. It’s SQL, but readable and writable in a sane way.
And no, SQL is NOT readable or writable for anything involving more than a single join.
- Comment on Is there something better than SQL? 1 year ago:
SQL is horrible as a language to read or write. There’s a million different variants, because it lacks so many basic things. And when used in other code, you generally end up string concatinating one language in another language, with all the HORRIBLE bugs something like that brings about.
Imagine Backend People said we should just write adhoc Javascript for the frontend by concatinating the “correct” code in the backend.
- Comment on Is there something better than SQL? 1 year ago:
Without a DSL for writing SQL, any sufficiently complex program will end up with string concatinating all over the place. Basically, writing a language with ZERO checks or highlighting or anything. That’s asking for trouble.
But coming from Java, I agree that some ORMs go way too far.
- Comment on Zero to Hero in 1 hour 1 year ago:
Kubernetes is so easy! Unless you’re insane enough to have any state at all in your app. But who does that?
- Comment on Why should I use rust (as a Go enthusiast)? 1 year ago:
Ironically, I learned Rust first, and later looked at Go. I found a lot of the syntax needlessly “different”. That being said, it’s still a decent language. Point being, a lot of the weirdness subsides once you understand why it’s there.
Personally, I don’t actually care about the lifecycle and memory management stuff. What I like about Rust is:
- An enforced error type that is very convenient to use with the ? operator. No more err != nil spam, but same amount of safety
- ADTs with a host of wonderful features, like exhaustive match statements. Go enums are horrendously basic, let’s be honest
- NO NIL!! Non existence is expressed with an Option type that, like the error type, comes with many conveniences
- Generics from the start, meaning you don’t have older code that throws away type safety anywhere
- Traits/Interfaces can be implemented for foreign/external types and types can implement external interfaces (duh)
- Great tooling, good formatting tools, good LSP, that kind of stuff. Golang has that too
Why learn Rust? For the same reason everyone should learn different languages. To learn new concepts and see new perspectives on old problems. It’ll make you a better developer even in your previous languages.
- Comment on Golang be like 1 year ago:
It’s better than “invisible” exceptions, but it’s still the worst “better” version. The best solution is some version of the good old Result monad. Rust has the BEST error handling (at least in the languages i know). You must handle Errors, BUT they are just values, AND there’s a easy, non-verbose way of passing on the error (the ? operator).