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.
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.
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 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
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 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 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.
Learn more with my Swift, SwiftUI & UIKit courses at seanallen.teachable.com
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.
Already in the works :)
9:17
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.
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.
Great video sharing value contents, keep it on. Looking forward on April
Thanks, will do!
This episode is super informative. Thanks Sean!
Glad you enjoyed it!
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
Thanks Sorin! I'm having fun doing the show again. Good to be back.
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.
Glad you like it! I'm having a lot of fun doing the show again. As far as I know, I'm the only one doing this in the Swift space.
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'm curious to hear how it goes. The whole community will be in the same boat. It's going to be an interesting transition, that's for sure.
So cool, I liked about that idea to import the dependencies only once as much as we can, actually I also wrote an article in medium for it. 6:37
Glad you liked it :)
Clutch resources! Thank you✌
Thanks Dave!
Totally agree with healthy codebase!
Hey Sean, keep it up mate! Thanks for the Swift news.
Thanks, will do!
Thank you Sean!
No problem :)
You're a godsend, so much love for you and your hard work!
I appreciate that :)
Thanks Sean, you’re the greatest.
I appreciate that!
A lot of good stuff. Keep it up Bro!
Thanks! Will do!
❤🔥❤🔥
Where does this leave Combine. No mention about Combine is it dead? Sunk a lot of time learning it.
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.
Thank you so much SeanAllan for bringing swift news again 🤝 🎉.
Happy to!
What new aboit swiftui ..why is not still mature and ready for production
If you can support iOS 16 and above, SwiftUI is ready for production for the vast majority of apps.
🔥
Thanks Sean! Great episode
Glad you liked it!
nice video, thanks!
Glad you liked it!
Thank you Sean 👍🏻
Any time
You don't understand it... Then the article proceeds to start a sentence with And...
Good thing grammar isn't correlated to Swift Concurrency skills.