Unless somethkng changed in the last few years, SSDs are much much faster.
Respect the burrito.
Unless somethkng changed in the last few years, SSDs are much much faster.
That’s true. I did learn a lot, but the idea of setting it all up again gives me anxiety.
I self host my email. It was hard work to set up. 0/10. Would not come again.
Good to see a list not containing just the obvious stuff.
I’ve read about a third of this list, and the others sound good.
The only one I’m not sure about is flatland.
Never heard of this language, but you’d be surprised how hard it is to write a correct and portable shell script.
Personally, I’d break out python once the script gets larger than a few lines, or rust if I want something more proper.
What the hell is this? Half way down the page it becomes a crypto advert…
Not a fan of Ruby, but the things they outline here are pretty good for testing just about any language.
I maintain a fork of llvm and a JIT runtime written in Rust where we’ve employed some of these same techniques. E.g. caching llvm builds, running things in parallel…
Any sufficiently complex, well tested, system has the potential for long CI times. It’s not something unique to Ruby or dynamic languages.
I was thinking the same.
I’m not saying it sucks. I’m saying it can be less straight-forward than conventional languages, even for experienced programmers.
The borrow checker is fantastic, but there’s no doubt that it requires a new way of thinking if you’ve never seen Rust before.
In case, like me, you were wondering what this has to do with ssh:
openssh does not directly use liblzma. However debian and several other distributions patch openssh to support systemd notification, and libsystemd does depend on lzma.
With ftps, can you use a self-signed cert? If so, how does it verify the cert? Do you have to upload the public key, or does it cache it on first use?
When using reolink in a self-hosted setting:
Thanks
That’s not right.
Try and write a mutable doubly linked list in Rust and you will find that it’s problematic for the borrow checker.
Search online and you will find solutions that work around this using ‘RefCell’ (to delegate mutable borrows to runtime), or raw pointers with ‘unsafe’.
It’s hard to get those kinds of data structures through the borrow checker.
Try writing a doubly linked list.
I agree for the most part, but writing data structures with shared mutable state can be a total pain in Rust.
I use C, C++ and Rust in my dayjob.
I don’t like C++, but I disagree with your statement.
C++ has:
It’s obviously still not a fully memory safe language, but it has some perks over C. I’d still much rather be using rust (most of the time).
I use dictd-client on openbsd. CLI app that talks to dict.org
Why what?
Avoid a route straight through what is known as…
Still good. One day…