Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
K-Hole16817dWe're bound to ask... What was the issue with SwiftUI that made you turn back?
@100110111 You can write wrappers for it, yes, but if you wanted to use complex UIKit transitions you always had to completely bypass SwiftUI and access the underlying UIHostingController (this is a UIKit view controller that lets you insert SwiftUI Views in it), which is literally defeating the purpose of SwiftUI. When I had to abandon my project, almost half of my code was UIKit. The time and effort that it would take to maintain the fucking code is not worth it in the slightest.
kiki1705417d@OmerFlame I really really really like that logic of “I’ve chosen SwiftUI -> half of my UI is already UIKit -> I need to quit SwiftUI”. A lot, and I mean A LOT of my ex-colleagues who were at very high positions and of course were talking about themselves as an engineers never really made wise decisions like this solely because of their ego. Even if there is really a need to switch, they’re all like “I chose X, means we should use X no matter what”, that’s the mindset I see really often. This is why you’re a real engineer and they are not.
@kiki holy shit, I make better decisions.
Damn. This is actually the first time that someone told me “you are an actual software engineer who makes better decisions than most of the industry”. That’s a serious shock to the system, really.
Also, implementing interactive popovers, stock Apple transitions and weird bugs and glitches and crashes is actually WAAAAY easier than SwiftUI. I am staying and never leaving.