Dave.

I found with my QNAP NAS that even just sitting the case on a piece of styrofoam made it considerably quieter. A lot of vibration gets transmitted through the feet and whatever it sits on gets turned into a sounding board.

Waiting patiently for the arrival of my pebble time 2 with its moderate array of features and its 21+ day battery life.

I was talking more about unwrap causing a panic rather than calling the actual panic macro directly. Rust forces the programmer to deal with bad or ambiguous results, and what that is exactly is entirely decided by the function you are calling. If a function decides to return None when (system timer mod 2 == 0), then you’d better check for None in your code. Edit: otherwise your code is ending now with a panic, as opposed to your code merrily trotting down the path of undefined behaviour and a segfault or similar later on.

Once you get to a point where we are doing the actual panic, well, that is starting to just be semantics.

causing the program to crash if it actually was an error, restoring the more unsafe behavior of other languages.

Wellllll it’s more of an abrupt exit rather than a crash, which is still better than eg. silently accessing beyond the end of an array, or ending up with a pointer to nowhere when you thought you had a sane memory reference.

“Why do people do X, when in my opinion if you disregard the two top reasons for doing X, it’s pointless? Prove to me that it would be better!?”

I shall begrudgingly consider it then, with much begrudgement.

But it’s three more letters. No deal.