Yeah, I assumed there would be progress. Here’s hoping the next time there’s a wave of registrations, the users stick around.
Yeah, I assumed there would be progress. Here’s hoping the next time there’s a wave of registrations, the users stick around.
it’s on us the fediverse for really failing to communicate the value of instances as well as making them easy
A bunch of people came over to Mastodon when Elon bought Twitter, but they left because it was missing features. The big ones I saw were
Life goes on past thirty five. I knew that was the case, but my plans and goals only went as far as then.
Kinda like when you graduate uni and you realize that there’s still more stuff to do.
I thought those were for only when shit is seriously wrong and execution can’t continue in the current state.
That’s how it starts. Nice and simple. Everyone understands.
Until
some resource was in a bad state
and you decide you want to recover from that situation, but you don’t want to refactor all your code.
Suddenly, catching exceptions and rerunning seems like a good idea. With that normalized, you wonder what else you can recover from.
Then you head down the rabbit hole of recovering from different things at different times with different types of exception.
Then it turns into confusing flow control.
The whole Result<ReturnValue,Error> thing from Rust is a nice alternative.
I remember getting these for games. They were awesome, but they never fit my keyboard.
Poverty and pressure to commit pension fraud were shown to be excellent indicators of reaching ages 100+ in a way that is the opposite of rational expectations’.
Cat nip is non-negotiable.
And we smell your piss bottles
🤫
And it’s definitely “multi”
I think ShareDrop does that.
I wouldn’t go back, if I were you.
Yeah. I’ve avoided that shit since it leaked out. And here I am behind the curve.
Thank you for explaining that. I’ve got a lot to think about now.
Cuck chair?
Oh yeah, I forgot about quote tweets.