As a fullstack TypeScript developer (5years exp), every time I watch content in Swift and the Apple ecosystem. I want to throw everything away and switch over. Everything feels so smooth and well thought. God, I would like to switch so bad!
The grass is always greener.... The reality is that iOS development has its pros and cons. SwiftUI is good for simple to intermediate things, but you can hit roadblocks really quickly. Even supposedly simple things can be very difficult. And difficult things can actually be impossible, forcing you to revert to using UIKit. Swift itself has evolved (devolved?) in to a kitchen sink of comp-sci ideas. An engineer's playground, with keyword explosion and an IDE that barely works at times. And of course, you are always behind the Apple 8ball. It's no picnic.
@@w0mblemania Yeah true, but it's so much pain to create high-quality apps using other technologies like React Native. It's not a smooth experience at all to have local first app, sync between all devices, great UI that works out of the box, access to all device power/features..... And many other things. What I like about Apple is that everything is unified and uses the same framework, language, paradigm...It's ok to have SwiftUI for simple cases and UIKit for complex things. Other platforms don't event have that. Everything is done by the community or the developer. It's so bad
![[LIVE] : ONE ลุมพินี 89 | คู่เอก "ยอดไอคิว vs คิริลล์"](http://i.ytimg.com/vi/Z3vYkHJ_5Ig/mqdefault.jpg)
Good basic explanation. Thank you.
Great introduction and explanation to the topic, thanks 👌
This was very useful, thanks.
I'd certainly like to know more about iCloud support for user documents.
Valeu!
As a fullstack TypeScript developer (5years exp), every time I watch content in Swift and the Apple ecosystem. I want to throw everything away and switch over.
Everything feels so smooth and well thought.
God, I would like to switch so bad!
The grass is always greener....
The reality is that iOS development has its pros and cons.
SwiftUI is good for simple to intermediate things, but you can hit roadblocks really quickly. Even supposedly simple things can be very difficult. And difficult things can actually be impossible, forcing you to revert to using UIKit.
Swift itself has evolved (devolved?) in to a kitchen sink of comp-sci ideas. An engineer's playground, with keyword explosion and an IDE that barely works at times.
And of course, you are always behind the Apple 8ball.
It's no picnic.
@@w0mblemania Yeah true, but it's so much pain to create high-quality apps using other technologies like React Native. It's not a smooth experience at all to have local first app, sync between all devices, great UI that works out of the box, access to all device power/features..... And many other things. What I like about Apple is that everything is unified and uses the same framework, language, paradigm...It's ok to have SwiftUI for simple cases and UIKit for complex things. Other platforms don't event have that. Everything is done by the community or the developer. It's so bad