![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8f2046ae-5d2e-495f-b467-f7b14ccb4152.png)
For real, friends in discord were aghast at this, and I’m thinking “bro I’ve heard you tell your kids to shut the fuck up.”
For real, friends in discord were aghast at this, and I’m thinking “bro I’ve heard you tell your kids to shut the fuck up.”
Both. It allowed/forced me to explicitly handle edge cases I wasn’t thinking about. That means the error doesn’t happen at run time, but at compile time (or while writing!) so technically speaking the errors didn’t go away, they moved to in my face rather than “maybe in the future.”
Most of the time the remedy was to explicitly catch whatever happened and nicely explain what happened, vs looking at empty production logs because logging is turned down.
It’s certainly a preference, but for me, I’d rather argue with the compiler all day long and push a bulletproof release than quickly ship something I thought was good and be embarrassed.
Anecdotally I converted a python app to rust and suddenly had no more runtime errors. It’s utter bliss.
I had to rewind three times cause I swore I kept missing something important that made that significant or something. Needless to say I was glued to the screen until the credits rolled.
I’ve been stuck in Winter’s Heart for months, maybe even approaching a year now. I might finish it by the time i have grandkids.
FWIW Ryobi’s battery has been the same format since the 90s which removed any doubt I had about continuing to buy the brand.
Awesome update.
On iOS, after adding lemmy.ml to the homescreen as a PWA from Safari, I can’t log in because the keyboard doesn’t pop up when tapping the username or password fields.
It literally happens every Olympics and people lose their mind every time. Same with “funny shooting stance” memes.