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?

It’s not delayed. The other person who is seen in the broadcast must be asleep. I’m sorry that your superpower is so limited. Such a shame.

The other person has to be asleep and hears it as a whisper in their dream.

I can pause time in order to write as much code as I want without interruption.

Isn’t it part of some secret Pokémon lore that humans are Pokemon? Someone made a video on YouTube about it a few years ago.

I started doing this and have never looked back. We also keep the next loaf in the freezer, so we always have bread.

Exactly. The functions of the super trait are also required when implementing the child trait’s functions, as you would expect from inheritance.

Basically, you can generalize your trait types into their parent (super) traits for situations when functionality is specific to those supertrait objects.

As an example, if you have a trait CanBark and it is a super trait for the trait IsDog, you can coerce your references of &dyn IsDog into a &dyn CanBark. You can then work with other trait types that share a super trait.

trait CanBark {
    fn bark(&self);
}
trait IsSeal: CanBark { }
trait IsDog: CanBark { }

fn bark_as_group(barkers: &Vec<&dyn CanBark>) {
    for barker in barkers {
        barker.bark();
    }
}

let spot: &dyn IsDog = get_spot();
let seal: &dyn IsSeal = get_seal();
let barkers: Vec<&dyn CanBark> = Vec::new();
barkers.push(spot);  // coerced
barkers.push(seal);  // coerced
bark_as_group(&barkers);

At least, I hope this is possible now. If it’s purely “you can return a coerced type from a function”, that is less useful.

Wow, that trait feature is great. I’ve been eagerly waiting for that one for a long time. Thank you to everyone who made that possible.

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.

I had a coworker who would sometimes not create a method as being static to the class and would therefore need to create a default instance to call said method. “It’s domain-driven design.”

The price and quality are so hard to beat.

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 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 don’t know how some people find the time to do anything but help take care of mom and the baby. I was either sleeping or helping while trying to find time for food.

It was over a matter of honor, of course.