Side note: The article in that last toot is by the Castle Game Engine project, a game engine entirely in #ObjectPascal.
At first glance, their docs look to be very clearly written and approachable.
Also, they're written in #AsciiDoc, stored in a Git repo and turned into a static site. And you all know I love me a bit of AsciiDoc.
Thumbs up from me!
Coming to fosdem this year? you use #gnupg? Want to sign your key? Good news, I'm organizing a key signing party (https://en.wikipedia.org/wiki/Key_signing_party).
details are at https://ludovic.hirlimann.net/2024/01/key-signing-party-at-fosdem-2024.html
please boost or share, so people come and attend.
#privacy #email #security #gpg
@alerque Actually (and this is literal fact) before I did one day cargo install bat
, I had an alias for along the lines of cat <file> | vim -R -
sort of thing so it was literally just way to shortcut that and not much else.
The way Rust community looks at a “change” is sort of “this would nicer way to do this”. The way kernel community looks at a “change” is more like “we have this alarming situation that we need to absolutely deal with right here an right now or data centers or whatnot will be doomed”.
And even my fav language C is in the end for me an opcode generator, not more or less. Rust is yet another opcode generator with static analysis built-in. I just vote for the tech first and totally disregard “language level” kind of merits. What works the stuff that goes best to the cores best WFM me best in the end :-)