Very useful and inspiring information. I love these "deeper dives" as they give me ideas how to solve those "can't do dat" moments;...which I seem to encounter more often than I like. If I could, I would like to give more than 1 thumbs up.
Very nice. At the end you show different ways of extending through simple extensions, modifiers and extensions encapsulating view modifiers. You state quickly that the las one is the preferred swift way. And it makes sense. However which is the best/optimum from a performance memory footprint point of view?
I had this question too - what performance related cautions we must consider when you use such extensions; for example - what if we put a higher order function in a view extension? So, there might be some boundaries - like do's and don's; correct? May be an idea for another video.
I asked this question myself of other more senior devs when i was developing this video and there did not seem to be any indication that performance was an issue one way or the other, but using a ViewModifier seemed to be the preferred method.
@@StewartLynch Great video as always. Was there any reason given for why the ViewModifier approach was considered better. As you note, the two approaches look very much the same.
@@StewartLynch you're my best tutor, I don't trust others ( most of them on Utub are from India) , Please consider,, If anyone uploading an app to apple store, then software localization is a must, Please help the community by providing a great service, pointing out a way, a right way ( just like your enumb clip)
Very useful and inspiring information. I love these "deeper dives" as they give me ideas how to solve those "can't do dat" moments;...which I seem to encounter more often than I like. If I could, I would like to give more than 1 thumbs up.
Hey Stewart, sir, follow your video from my career first day. It is always helpful and motivating me to perform best.
Wow. Thanks for the feedback.
Love going through your lessons and landing on things like this in first 5 minutes that I know I will use! Thank you!
Great to hear!
As always, a great video Stewart. Learn something new today. Thank you.
Very nice, and Swifty indeed. Thanks Steward.
Thanks for listening
Thank you so much Stewart 👍🏻
Very nice.
At the end you show different ways of extending through simple extensions, modifiers and extensions encapsulating view modifiers. You state quickly that the las one is the preferred swift way. And it makes sense.
However which is the best/optimum from a performance memory footprint point of view?
I had this question too - what performance related cautions we must consider when you use such extensions; for example - what if we put a higher order function in a view extension? So, there might be some boundaries - like do's and don's; correct? May be an idea for another video.
I asked this question myself of other more senior devs when i was developing this video and there did not seem to be any indication that performance was an issue one way or the other, but using a ViewModifier seemed to be the preferred method.
I am not sure that there are any down sides to using extensions.
@@StewartLynch Great video as always. Was there any reason given for why the ViewModifier approach was considered better. As you note, the two approaches look very much the same.
I think just because that is how Apple does it.
Thank you Stewart….
Extensions are somewhat mandatory when using Core Data…
do you have any video tutoring how to localize the app ?
No. Sorry
@@StewartLynch well, could you consider making one , please
Never having done that myself, I am afraid that I might botch it. I think others have done ones though.
@@StewartLynch you're my best tutor, I don't trust others ( most of them on Utub are from India) , Please consider,,
If anyone uploading an app to apple store, then software localization is a must, Please help the community by providing a great service, pointing out a way, a right way ( just like your enumb clip)