Trying to my hardest to understand what the advantages are. This just seems more cumbersome and messy, e.g. keeping an array of observers. I’m sure and believe this probably is the future, but it just hasn’t clicked yet why this is better. Would love to see a direct comparison of implementing something with and without combine, then walk and talk through why each component of doing it via combine is better.
Yes, We could easily handle button taps just by creating variable with type as Function. and just by calling cell.onButtonTapped = { [weak self] in print("tapped" )}. I didn't get why should I migrate to combine to add these additional boilerplate codes
Agreed. The argument for them appears to be "we don't like closures, so… lets make a new API which has two closures and also requires an extra local property". Why bother?
honestly been waiting for someone to do a "basic" tutorial on Combine... after watching this video I will still be waiting. I appreciate anyone's effort to teach information for free so thank you. Unfortunately, this isn't basic. The assumption is knowing nothing about combine and then you code like a person should know what Cancellable and Sink are without explaining it and why/how they get used. I am as lost watching this as I am with the paid courses from Mohammad Azam or Ray Wenderlich. Sigh. Appreciate the effort though.
This is a basic tutorial, a table view with buttons which print something to the console is like the "hello world" task of the iOS programming. There is no need to understand every single method / operator in depth, just analyze the example code and you can get the idea of it
Waiting for. Waiting for not playground explanation and examples, waiting for real project examples)) for example how to subscribe or observe (I still can’t understand what for what) some ui elements, if change something in VC1 it will be affected on VC2. In general I have task that I have to update data in my music app. PlayerVC will be dismissed but I want still update artImage, song name, artistName to be updated in ListVC when music has changed.
2 questions - 1. Whats the purpose of making a AnyCancellable object and using sink, when we can do that using normal closures. 2. Whats the purpose of using Passthrough object in a cell, when again this can be achieved by a normal closure. Am I missing something or this is just a closure with new syntactic sugar?
yes same for me, feeling confused, Future is nothing but @escaping in closure and Passthrough what ever shit that is, is again similar to what we do using closure completionhandlers, no idea why I should be using this
Actually I have expected more from Combine as reactive framework, Rx handles data easier and the code is more neat. And you don't have to actually reload data when you're using Rx while you need to do it while using Combine. Can we have a video comparing both frameworks with pros and cons? Your videos are always easy to explain so I would appreciate more contents about Rx frameworks on how to handle variables instead of tableviews or collectionviews. Thanks.
We could easily handle button taps just by creating variable with type as Function. and just by calling cell.onButtonTapped = { [weak self] in print("tapped" )}. I didn't understand why should I migrate to combine to add these additional boilerplate codes.
I like how you use combine for the server call but i'd rather use a weak ref closure for the tap as a var instead for cell so i don't have to create that extra array of observables for each cell. just a weak closure that passes back a string value would be less overhead. This if fine just my pref
Yess i really interest in combine, actually i didnt really well knowledge about delegate pattern also, but that generic things and .store .sink is interesting also. maybe i will learn about delegate pattern, then get back here to learn that combine for rxswift if im not mistaken, thankyou so muchh
I have learnt basic Swift and done GCD and Operations Queue not touched UI yet but i have been ordered to complete basics of Combine Framework and I am not getting anything in this as well as any other video. Can anyone guide what should i learn first, like what should be the order of learning. I don't even know what is viewcontroller in Swift, but i am confused weather I should learn viewController directly or is there something that i should know in prior to this.
Thank you for this video. It is very helpful. I have a doubt that why we should use combine instead of delegate or closure approach. What problem of delegation and closure is solved by combine. passthrough object seems like a closure but with extra functionality. if we think it in reverse order that is delegate or closure is solution of complexity of combine then it is right.
1) Can we use PassthroughSubject to Bool isSelected of CellView? Is it possible to assign Model object to action instead of String and print value of Object with indexPath?
10: 15 - Can we have more about memory leaks? I often use self.myModel = result or self.myModel.append(result), then self.collectionView.reloadData or tblView.reloadData. I never used [weak self]. What does it give? Thank you🙏
Man … i cant stand your tone … and the contents is not much better .. i’m gonna perhaps go ahead and forget you exist… and no worries, i did go ahead and told yt to go ahead and stop to go ahead and suggest your vids 🙂
If you like my teaching style, I've started creating my own courses here that you may like! courses.iosacademy.io/
@@AvantjerTube hey Jerry, I appreciate the feedback. Ill keep in mind to slow down as I create more content. All the best.
Please do more videos about Combine framework ❤️
Will do
Excellent video. Love that this is explained in a real world scenario rather than playgrounds, which I find harder to understand.
Trying to my hardest to understand what the advantages are. This just seems more cumbersome and messy, e.g. keeping an array of observers. I’m sure and believe this probably is the future, but it just hasn’t clicked yet why this is better.
Would love to see a direct comparison of implementing something with and without combine, then walk and talk through why each component of doing it via combine is better.
Yes, We could easily handle button taps just by creating variable with type as Function. and just by calling cell.onButtonTapped = { [weak self] in print("tapped" )}. I didn't get why should I migrate to combine to add these additional boilerplate codes
imperative vs declarative
Agreed. The argument for them appears to be "we don't like closures, so… lets make a new API which has two closures and also requires an extra local property". Why bother?
honestly been waiting for someone to do a "basic" tutorial on Combine... after watching this video I will still be waiting. I appreciate anyone's effort to teach information for free so thank you. Unfortunately, this isn't basic.
The assumption is knowing nothing about combine and then you code like a person should know what Cancellable and Sink are without explaining it and why/how they get used.
I am as lost watching this as I am with the paid courses from Mohammad Azam or Ray Wenderlich. Sigh.
Appreciate the effort though.
thanks for the feedback
This is a basic tutorial, a table view with buttons which print something to the console is like the "hello world" task of the iOS programming. There is no need to understand every single method / operator in depth, just analyze the example code and you can get the idea of it
I lost him too there :P
If you feel hard understanding this, then you need a carrier shift
You put the cell on the same page as the ViewController? He's a madman I say. A MADMAN!!!
thanks for the nice and easy to understand intro!
Youre welcome
Waiting for. Waiting for not playground explanation and examples, waiting for real project examples)) for example how to subscribe or observe (I still can’t understand what for what) some ui elements, if change something in VC1 it will be affected on VC2. In general I have task that I have to update data in my music app. PlayerVC will be dismissed but I want still update artImage, song name, artistName to be updated in ListVC when music has changed.
I like the way you say "cell"
Haha thanks
best video about combine, easy and clear, thank you
Glad it was helpful!
waiting for this video for a long time.❤️
Hope to see more videos about Combine Framework.
Coming soon
you sound like the guy from new boston tutorials. Awesome tuts btw, that deserves a thumbs up
Thanks!
There is some crazy shit going on here
Please do more sir, you are the best
Thanks
You rock dude. Keep going!
Thank you!
2 questions -
1. Whats the purpose of making a AnyCancellable object and using sink, when we can do that using normal closures.
2. Whats the purpose of using Passthrough object in a cell, when again this can be achieved by a normal closure.
Am I missing something or this is just a closure with new syntactic sugar?
yes same for me, feeling confused, Future is nothing but @escaping in closure and Passthrough what ever shit that is, is again similar to what we do using closure completionhandlers, no idea why I should be using this
Yes, would love to see more Combine examples! Thank you!
Always love his tutorials, he helped us to digest and organize Combine concepts in understandable and demonstrable manner.
Waiting for video like this...❤️
Get pumped
Please do more Reactive Programming!
Awesome Video
Thanks!
I love the explanations. Really helpful!
Thank you!
Thank you
Youre welcome
Waiting for your awesome explanation Man 😍❤️
Thanks
I’ve just realized that there aren’t videos on main frameworks for Swift on TH-cam. You can be the first one to make 😊
Did the new Observable framework substitute combine ?
Actually I have expected more from Combine as reactive framework, Rx handles data easier and the code is more neat.
And you don't have to actually reload data when you're using Rx while you need to do it while using Combine.
Can we have a video comparing both frameworks with pros and cons?
Your videos are always easy to explain so I would appreciate more contents about Rx frameworks on how to handle variables instead of tableviews or collectionviews.
Thanks.
We could easily handle button taps just by creating variable with type as Function. and just by calling cell.onButtonTapped = { [weak self] in print("tapped" )}. I didn't understand why should I migrate to combine to add these additional boilerplate codes.
I like how you use combine for the server call but i'd rather use a weak ref closure for the tap as a var instead for cell so i don't have to create that extra array of observables for each cell. just a weak closure that passes back a string value would be less overhead. This if fine just my pref
also since this is a tutorial on combine i get it. just throwin in 2 cents years later :-)
In a 4th minute, what did you type for a shortcut for a func? Thanks
Yess i really interest in combine, actually i didnt really well knowledge about delegate pattern also, but that generic things and .store .sink is interesting also. maybe i will learn about delegate pattern, then get back here to learn that combine for rxswift if im not mistaken, thankyou so muchh
your welcome
Where can I get the code for this example ?
I have learnt basic Swift and done GCD and Operations Queue not touched UI yet but i have been ordered to complete basics of Combine Framework and I am not getting anything in this as well as any other video. Can anyone guide what should i learn first, like what should be the order of learning. I don't even know what is viewcontroller in Swift, but i am confused weather I should learn viewController directly or is there something that i should know in prior to this.
Show some api data handler without future just with anypublisher generic please.
Added to list
Do we need combine after async/await coming?
They offer different features
@iOSAcademy bro, the link to the source code is wrong and I also wasn't able to find it in your Git repo. Could u pls add it?
I’m waiting for the equivalent: RxSwift.
Coming soon
Me 2 bro
@@motexdevelopers1123 RxSwift is one of the most demanded skill for iOS developer jobs.
@@rev_kous9275 sure btw its work with under ios versions combine just for 13+
@@motexdevelopers1123 Also, MVVM pattern suits best for reactive programming.
i love your new mic Afraz. what's the make?
Thanks, its a yeti
Thank you for this video. It is very helpful. I have a doubt that why we should use combine instead of delegate or closure approach. What problem of delegation and closure is solved by combine. passthrough object seems like a closure but with extra functionality. if we think it in reverse order that is delegate or closure is solution of complexity of combine then it is right.
Please organize the videos to playlist
Will do
1) Can we use PassthroughSubject to Bool isSelected of CellView? Is it possible to assign Model object to action instead of String and print value of Object with indexPath?
10: 15 - Can we have more about memory leaks? I often use self.myModel = result or self.myModel.append(result), then self.collectionView.reloadData or tblView.reloadData. I never used [weak self]. What does it give? Thank you🙏
Read about scenarios when memory leaks happen, you will know.
Skip the boiler plate th-cam.com/video/hbY1KTI0g70/w-d-xo.html
Thanks for the feedback
you didn't really explain what any of these combine subscribers do or how they work..
Combine is cool, but UIKit, dude! :D it's 2021, come on!
Haha thanks
I’m sorry, where tf are “the basics”? It’s just a dump of new terms, none explained… I know less after watching this.
I appreciate the effort but this is not a good video. 80% of the video is typing some UIKit code...and the combine part is not really well explained.
to be honest, i don't understand what you're saying at all
Thanks for the feedback
Don't bother. Not really a useful intro to Combine. Half the video is spent on typing UIKit code. On top of this sink is not even explained.
Man … i cant stand your tone … and the contents is not much better .. i’m gonna perhaps go ahead and forget you exist… and no worries, i did go ahead and told yt to go ahead and stop to go ahead and suggest your vids 🙂
thank you
You're welcome