I sped up the Tapestry timeline by over 350% by getting rid of SwiftUI. Increasingly of the opinion that SwiftUI was a huge mistake. There are parts of it that are good and have increased iteration time immensely, but the costs.... oh the costs...
0 Boosts
0 Likes
@bigzaphod I always wonder though, if that partly is because much of it is really build on top of other existing layers like UIKit and if a fresh "raw" SwiftUI maybe would be much quicker
@yannikbloscheck I wonder that too because I don't think the *idea* of it is necessarily bad. I do question if it should ever have been built on Swift the way it was, though, either. But the other bigger problem is how often you simply cannot do what you need to do in SwiftUI because of the declarative nature. If it's something Apple didn't anticipate, then all hell breaks loose.
@bigzaphod Yeah, that can be extremly infuritating. Some things that should be very simple can be extremly difficult. But other than Apple having strong opinions and not caring enough about customisation that maybe also has slightly to do with needing to wrangle UIKit behaviour behind the scenes without exposing it.
@bigzaphod Kept digging a deeper hole by using SwiftUI for an infinite canvas… retrospect is painful.
@bigzaphod I imagine it being something like this. 💀
@bigzaphod I could’ve told you that.
@paul you probably did.
@bigzaphod all appreciated though
@bigzaphod I love the speed!!!!
@bigzaphod Good man. Rest in pieces, SwiftUI.