The main one that jumped out to me was a scroll issue on iOS when using multiple fingers. I just looked it up to share a link and it may be fixed? It's the mentality of "Eh, we might fix it one day" that is the bulk of why I didn't stick with Flutter. A bug this annoying lingering for as long as it did said volumes to me.

Possibly fixed: https://9to5google.com/2023/12/28/google-fixes-flutter-infamous-scrolling-bug/

I wanted to get into Flutter but it seems like there are some bugs that are either unfixable or that they have actively decided not to fix. I didn't want to end up wasting my time building on such a foundation, but it's definitely nice for certain projects that fit within the supported functionality.

This was a great blog post. I love Rust and Bevy, but I can definitely see why you made the switch.

The primary issue with your decision to use Rust/Bevy, for me, was that you were taking on the task of getting others to work in a difficult language for novice developers. I would never suggest Rust as someone's first language, coupling that with a regularly-changing library like Bevy.

I would love to know what the pros and cons were between Unity and Godot. If you were going to switch to C# anyway, Godot seems like the next logic choice to me, so I'm curious about what your team's evaluation was for that engine.

When I learned Python I thought that not having a statically typed language was the way to go, but then it just became an issue when I was trying to ensure that everything was at least something like what I was expecting. Going back to statically typed languages even harder with Rust has been a dream. I love it.

For me it all depends on how often a project changes. If it's constantly in flux, I don't bother remembering any of it because I might not be the last one who touched it. The more you try to remember everything, the more wrong you become due to the successive work of your coworkers.

I've had mine on vibrate for years. Texting doesn't trigger it, only calls. It's been great. I look at my phone only when I'm ready to look at it.

This was a good blog post. I particularly appreciated the statement about the validate and parse function comparison: "Both of these functions check the same thing, but parseNonEmpty gives the caller access to the information it learned, while validateNonEmpty just throws it away."

I don't know how to get everyone I know to really understand this. Every time I bring it up in conversation, the other person just puts their hands up and explains that they're powerless to address it, so it's not even worth talking about. I don't know how to respond to the apathy.

You can just pinch the end of a banana to start peeling it. The effort required is far less than trying to overcome the ripping force of the stem.

I love how the solution didn't involve changing the prefix to "mcaffee_". Now users don't know who to blame. Great. That's so nice of them.

Your team needs to have a coding standards meeting where you can describe the pros and cons of each approach. You guys shouldn't be wasting time during PR reviews on the same argument. When that happens to me, it just feels like such a waste of time.

As someone who learned a lot from C++ and that now loves Rust, this annoys me.