Hey Sean, I think the user default requirements coming up on May 1 of 2024 is going to collect a lot of people and I think you should make a video on it. It confuses me to be nice for someone to just break it all down into a 10 minute video.
i just love this show, i swear. i know other friends and collaborators who work as ios devs, and we all reference your videos. it's insane and amazing. keep it up, m'lord! with haste! *unsheathes his sword as he starts riding on his horse towards the sunset *horse sounds
Perhaps a more helpful way of thinking about the one import rule is that everything in your system should rely on abstractions with low coupling and high cohesion. That's why they are usually some kind of service or manager or singleton or whatever. Since an abstraction could cross multiple files under a group, where each imports the same package, one import may be confusing. I can see people having humongous source files just to comply with the rule :-) Your analytics example is perfect. I imagine it could get rather large and complex, yet from the perspective of the rest of your code, it's one abstraction.
I lost a year trying to use swift concurrency only to realize it was not working the way I thought it did. Rust enforces safety and it did not take more than a week to “get” how it works. I look forward to turning on the swift checking.
I just wanna tell you, Sean how much I love these news videos! Are you the only person that does this? Or are there other people I should subscribe to for News, also, thank you very much.
I believe Combine is basically dead. Apple hasn't updated it in a while and it appears Swift Concurrency is filling it's spot. There may be some niche cases where Combine is the right tool, but I don't believe it will be a big part of Apple development moving forward.
the people working on version naming are super dumb. they just have to do 5.9 then move to 6.0. they need to taught a basic math knowledge. If they need to do this.
