Ky
banner
kynorthstar.me
Ky
@kynorthstar.me
'91 | Lead Swift Software Eng. | Infosec | Scientist | AI Expert | UI/UX Eng. | Optimist | Anarcho-Christian | Taíno | Polyam | Queer Elder | Plural | Non-Binary & Any Pronouns
KyNorthstar.me
ACAB, divide and conquer. Make them fight themselves from the inside. Cheer this on!
December 7, 2025 at 1:50 AM
Hell yeah 🤝🏽 welcome to the no-inheritance club
December 4, 2025 at 4:54 PM
Reposted by Ky
TFW you endlessly studied class inheritance in school only to gradually realize that inheritance is superfluous and all you ever needed, or ever should have studied, was interfaces.

I was learning some Rust last year, and it's the first language I've seen that finally gave up inheritance.
December 4, 2025 at 2:17 AM
I think I’m realizing that it rubbed me the wrong way BECAUSE `unwrap()` is not any special syntax...

dang it, this blog post is taking longer than I expected lol
November 20, 2025 at 7:45 AM
I'm drafting a blog post right now, that puts my thoughts much better. Excited to see how people react when I share it!
November 20, 2025 at 1:31 AM
seemingly, more experience see than that Cloudflare dev had lol
November 19, 2025 at 10:04 PM
The name not being scary, is really my primary issue here
November 19, 2025 at 9:26 PM
Thankfully it's foundational in Swift that exclamation points mean "crash" (or "invert a boolean", though I've seen most codebases prefer `== false` instead because of this).

Which is nice because that means someone who doesn't know this won't accidentally crash the program cuz they won't use it
November 19, 2025 at 8:40 PM
He did? 💀
November 19, 2025 at 7:21 PM
if only we understood what was the cause of this warming… It almost feels global at this point
November 19, 2025 at 7:21 PM
Which is what makes it safer! You have to explicitly take the steps to crash the program yourself, if you want it to crash
November 19, 2025 at 7:20 PM
Well, first of all, this is Result, not Option(al).

Second, Swift makes it very clear when something’s going to crash by requiring an `!` or saying things like “fatalError()”. Your program won't crash because you called any old method; it'll crash because you told it to crash.

No `!`s, no crash
November 19, 2025 at 7:20 PM
Cloudflare's use of Rust's `Result`'s `unwrap()` is what ultimately took down Cloudflare.

Rust has many ways to get the value or error in `Result`, including `expect()` and `unwrap()`, both of which crash the program if the `Result` contains an error.

Swift's `Result` has no crashing APIs at all
November 19, 2025 at 5:30 PM
King Soopers is charging me $50 for it, so...
October 21, 2025 at 7:26 PM
Could you elaborate on how this relates to associating an account with a website?
September 12, 2025 at 2:45 AM