To your latter question, probably because there's no sensible conversion for some float values like INF and NaN. Same general reason f32 and f64 don't implement Ord. At least if you implement it yourself you can make those decisions consciously.

To be clear, I don't agree with all of the author's points, particularly their characterization of "woke culture", but there are elements of truth even there. Food for thought.

Ooh, I get it. Kind of shared hierarchical state. I wouldn't have thought about that in dynamic scope terms, but it's an apt comparison. At least in SwiftUI there seem to be data structures that allow you to reason about where your state is coming from, instead of just a stack trace!

I'd love to know how; my only brushes with dynamic scoping have been Perl and Emacs lisp, and it just seemed to make code harder to reason about. I suppose I could see a use-case with DI but debugging that scares me.

I still think it's wildly unethical for journalists to release PHI - it's just not illegal under HIPAA.

www.hhs.gov/hipaa/for-in...

That is simply not the case. The HIPAA Privacy Rule restricts "covered entities", and journalists are not covered entities under the law. Broadly speaking, only health care providers, health plans, health care clearing houses, and their associates are restricted by HIPAA. Reporters are not.

Have you ever spent a week trying to track down a memory stomp in C or C++ code? That's what initially attracted me to Rust - systems programming with memory safety sans GC.