Yes. See [0], and especially the very last link [1] in that comment (it's a very nice write-up on exactly how to do that).
So cool, thanks.
Go is designed to be easy to read and easy to write. err != nil is not hard to read. If you don't like the repetition, it simply isn't the language for you. I'm perfectly happy with how Go does it. I do not want the language morphing into another Rust.
I hated Scratch. I saw it as childish and simplistic. I wanted to play with the big boy stuff.
curl --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/Exein-io/pulsar/main/pulsar-install.sh | sh
So secure, I mean it's forcing https AND tls1.2 - maximum security! Especially when you just pipe a random script into shell.Also, no information on its authors, who audited the code, what makes it "secure" enough to warrant giving an administrative entitlement over my system. Hard pass.
If NIST really is up to no good on behalf of US intelligence agencies, it's reasonable to believe they'd be doing everything they can to prevent strong post-quantum crypto.
Also, here's an idea I had: let's say you wrapped a plaintext in three different encryption algorithms authored in adversarial countries. Even if you assume all three are backdoored by their creators, you'd have something that could only be unwrapped if the three adversarial countries worked together. Is there anything out there that does this?