4 ms·

Can you give some examples of those "terrible bugs" you have experienced on a yearly basis? I have developed for iOS for the last 5 years, and I haven't ever e

Can you give some examples of those "terrible bugs" you have experienced on a yearly basis? I have developed for iOS for the last 5 years, and I haven't ever experienced those in UIKit. This year brought one single bug in UISegmentedControl, in a situation that doesn't happen often: https://forums.developer.apple.com/thread/122736 https://forums.developer.apple.com/thread/122736

LeoNatan25 7y ago
UINavigationController—https://twitter.com/LeoNatan/status/1168286477882728448 https://twitter.com/LeoNatan/status/1168286477882728448 UITabBarController—https://twitter.com/LeoNatan/status/1168286996915204097 https://twitter.com/LeoNatan/status/1168286996915204097 UIActivityViewController Various UIView layout issues Safe areas—https://twitter.com/LeoNatan/status/1179475940784721920 https://twitter.com/LeoNatan/status/1179475940784721920 UITableViewController—iOS 13's sheet presentation broke clearsSelectionOnViewWillAppear (https://twitter.com/LeoNatan/status/1137474148488364034 https://twitter.com/LeoNatan/status/1137474148488364034), for example, but it's often broken: https://twitter.com/Javi/status/644631570083483648 https://twitter.com/Javi/status/644631570083483648 SLComposeServiceViewController is completely broken on iOS 13
- cerberusss 7y ago
  You quoted a bug in 2015, then three in 2019. That's not on a yearly basis. Aren't your views colored by a bad iOS 13 launch? Because I do agree with you that iOS 13 seems bad (not my personal experience, from the general clamoring around us).
  - LeoNatan25 7y ago
    No. I maintain a pretty popular iOS open source project, as well as many low level projects for my job. It’s always unstable. Every year, new bugs pop up. Is it the end of the world? Probably not, but is it acceptable? It shouldn’t be. Before 10.15, I could run Mac software built 15 years ago. If AppKit developers can preserve backwards compatibility, so should UIKit developers.

LeoNatan25 7y ago

UINavigationController—https://twitter.com/LeoNatan/status/1168286477882728448 https://twitter.com/LeoNatan/status/1168286477882728448 UITabBarController—https://twitter.com/LeoNatan/status/1168286996915204097 https://twitter.com/LeoNatan/status/1168286996915204097 UIActivityViewController Various UIView layout issues Safe areas—https://twitter.com/LeoNatan/status/1179475940784721920 https://twitter.com/LeoNatan/status/1179475940784721920 UITableViewController—iOS 13's sheet presentation broke clearsSelectionOnViewWillAppear (https://twitter.com/LeoNatan/status/1137474148488364034 https://twitter.com/LeoNatan/status/1137474148488364034), for example, but it's often broken: https://twitter.com/Javi/status/644631570083483648 https://twitter.com/Javi/status/644631570083483648 SLComposeServiceViewController is completely broken on iOS 13

cerberusss 7y ago
You quoted a bug in 2015, then three in 2019. That's not on a yearly basis. Aren't your views colored by a bad iOS 13 launch? Because I do agree with you that iOS 13 seems bad (not my personal experience, from the general clamoring around us).
- LeoNatan25 7y ago
  No. I maintain a pretty popular iOS open source project, as well as many low level projects for my job. It’s always unstable. Every year, new bugs pop up. Is it the end of the world? Probably not, but is it acceptable? It shouldn’t be. Before 10.15, I could run Mac software built 15 years ago. If AppKit developers can preserve backwards compatibility, so should UIKit developers.