# Copy pwd into clipboard using pbcopy
alias cpwd="pwd | tr -d '\n' | pbcopy && echo 'pwd copied into clipboard'"

# grep search the current directory
function lg() {
  ls -alt | grep $1
}

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.

Can anyone explain what this means to me like I’m 5?

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.

I’ve found that one of the best things to do when making a library for something that is going to have a web interface is to first have it work in the terminal. You can much more quickly play around with the design and fix issues there instead of having to work with a more complex web interface.

You just create a simple menu system, like input("1: Feature A\n2: Feature B\n>") and just start trying out all of the different scenarios and workflows.

“Maintainable code and common patterns? But I prefer code-golfing my if-statements into one, long sequence of characters.” -coworker standing atop the Dunning-Kruger peak

I hate that it came to this, after so many Rust devs left, but all I can say is “Good.”

It happened to a friend who wasn’t passing in the proper types into their stored procedures, all strings, and “null” (not case sensitive) conflicted with actual null values. Everything in the web interface were strings, and so was null.

For some people it takes this mistake before they learn to always care about the data types you’re passing in.

I love the async closure update and the if-let scoping fix.

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.

I prefer to just throw the state into a database. Each table has their own “repository” type that knows how to save/load models and then I have “manager” types that use “repository” types to compose larger, feature-specific domain models.

I usually just use Sqlite for it’s simplicity but I’m not opposed to Postgres via Docker.

I’m surprised this doesn’t already exist.

After many years of using SO, I’ve started using ChatGPT for all of my programming questions and have not looked back once. For my usual “I know X is possible, but how do I do that in Y language” questions, it’s been a dream using ChatGPT.

In Rust, using the Option and Result types make the general flow of the application much easier to organize, make modular, and reuse.

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.”

Is that a water dispenser? I need something like that.

That’s something I haven’t heard before about the memory safety. In what ways is it not memory-safe?