What amazes me is that scrolling has never really been an issue in any native app? And yet here we are in 2023, with a native framework built for modern devices (where scrolling is the main interaction) that... inherits the worst behaviors of web of all things?
30k lines of SwiftUI in production later
11–20 of 124 posts
Re: 30k lines of SwiftUI in production later
#12Re: 30k lines of SwiftUI in production later
#13I also fell in love with swift when I had to learn it trying metal. it just succs how you have to use xcode with it.
What's wrong with Xcode? Is it the usual "iPhone is preparing for development" type of annoyances? Is it the bugs that sometimes prevent you from compiling? Or is it something more fundamental like even when everything works fine you don't like it?
The second, also yes.
The third, also, also yes.
Re: 30k lines of SwiftUI in production later
#14Earlier quoted context omitted.
What's wrong with Xcode? Is it the usual "iPhone is preparing for development" type of annoyances? Is it the bugs that sometimes prevent you from compiling? Or is it something more fundamental like even when everything works fine you don't like it?
The first, yes. The second, also yes. The third, also, also yes.
Re: 30k lines of SwiftUI in production later
#15I also fell in love with swift when I had to learn it trying metal. it just succs how you have to use xcode with it.
What's wrong with Xcode? Is it the usual "iPhone is preparing for development" type of annoyances? Is it the bugs that sometimes prevent you from compiling? Or is it something more fundamental like even when everything works fine you don't like it?
Re: 30k lines of SwiftUI in production later
#161) Don't watch too much state with Observable/EvironmentObject. When any watched property changes EVERYTHING RELOADS every time.
2) ScrollView.scrollTo is bugged with ForEach.
3) TextField and keyboard-interactions can be slow and buggy.
Re: 30k lines of SwiftUI in production later
#17Of course if the problem is with the core of your application like the scrolling example in the article, this is not going to help you much.
Re: 30k lines of SwiftUI in production later
#18Apple (and Next) have been iterating on AppKit for three decades. The UIKit fork of AppKit for iOS is a decade and a half old.
Expecting the same level of polish in SwiftUI after three years is a bit overoptimistic.
Apple has said that SwiftUI is "where the puck is going" so you can expect that they will keep on iterating on it for many years to come.
Re: 30k lines of SwiftUI in production later
#19Earlier quoted context omitted.
The first, yes. The second, also yes. The third, also, also yes.
Okay, can you give some details on what's wrong for you? Like what is the better way to do it?
It has all sorts of bugs and weird fail cases.
Honestly you should just search the internet for testimonials because anyone who uses Xcode can create a list of issues rather than rehash them all here in response.
Re: 30k lines of SwiftUI in production later
#20I mean, i had hoped that with a declarative UI apple would at least create some kind of path to web or android renderering, making at least part of the code reusable somewhere. But no, still 100% lockin. Which to me is a HUGE missed opportunity.