HN user

Celeo

111 karma

github.com/celeo

Posts0
Comments26
View on HN
No posts found.

After having it on my TODO list for a long time, I've installed EndeavourOS on another m.2 drive on my desktop. With the advancements in gaming support on Linux over the last few years, over 80% of my daily tasks, work, and games are well-supported by Linux. I've been using Linux in VirtualBox or WSL for many years, but it's been a long time since I've ran Linux directly on hardware. I'm excited!

I'd certainly like to be in an environment that has the dedicated people to those roles that so often are either combined or eschewed entirely, but 16+ hours of meetings per sprint sounds incredibly draining.

There are many ways to do it, like you said. Over time, the most popular options have shifted as new support from the standard library arrived. How you handle the errors can boil down to whether or not you really care about what kind of error it is, or just if an error occurred.

Two popular crates for handing these situations are thiserror [1] and anyhow [2], for handling errors by type and handling all errors, respectively.

There are additional ways, like just returning a Box wrapper around the stdlib error type [3], or just unwrapping everything. It depends on what your program needs.

[1] https://crates.io/crates/thiserror

[2] https://crates.io/crates/anyhow

[3] https://play.rust-lang.org/?version=stable&mode=debug&editio...

Not really for people who have their shells configured to auto-(de)capitalize the name of a command or binary, but for those that don't, it's a departure from what's normal. It's easily solved through an alias or similar, but still: why introduce the impedance?