[HN Gopher] Difference Between Implicit and Explicit Animations ... ___________________________________________________________________ Difference Between Implicit and Explicit Animations in SwiftUI Author : leopug Score : 54 points Date : 2023-07-09 16:16 UTC (6 hours ago) (HTM) web link (holyswift.app) (TXT) w3m dump (holyswift.app) | agluszak wrote: | No, I don't want to join your newsletter, please stop asking | already | | (Context: an annoying popoup appears once you've scrolled down a | few lines) | troupo wrote: | What about the consent form that has individual preferences for | over 200 vendors with no way to opt-out of data collection in | bulk? | BalinKing wrote: | From the guidelines: | | > Please don't complain about tangential annoyances--e.g. | article or website formats, name collisions, or back-button | breakage. They're too common to be interesting. | FlyingSnake wrote: | Your snarky comment doesn't belong to a sanguine forum like HN. | | If someone's being gracious enough to share their hard work | with the rest of us, we should appreciate it, especially on HN. | | The popup shows up only when you scroll down to the bottom at | the end of the article. | flohofwoe wrote: | I not only got a dark pattern cookie consent popup, but also | the newsletter popup after just scrolling a few lines down. | That was enough for me to close the page, sorry. | 1123581321 wrote: | That's still not an experience people want to read about. | SebJansen wrote: | don't shoot the messenger | voussoir wrote: | Yes, I do want to read about that, because it tells me | that this is an article I do not want to click on. | | As a reader I do not want to contribute to the analytics | and click count of a website that uses these engagement | tactics. | ruuda wrote: | The page works perfectly fine without javascript enabled. | ardit33 wrote: | Awesome article. SwiftUI is still 'not there yet'. It makes the | easier things, much easier compared to UIKit. But, as soon as you | get to more advanced views, it shows its immaturity. | | I know Apple is pushing it, and at some point it will be the | default UI framework for iOS (it is for Vision Pro), but it has | long way to go to the maturity that UIKit has. | | For 'small apps', and for simple views SwiftUI is great. For more | complicated interactions, UIKit is still the better framework. | flohofwoe wrote: | If the new macOS settings panel is indicative of SwiftUIs | overall qualities, I really hope it wont be the future (eg if | even Apple themselves can't get such a trivial thing like a | settings panel right, I don't even know what the point of | SwiftUI is after so many years in development) | SebastianKra wrote: | I don't get why people have zeroed in on the Settings app. | Outside of some very specific sections, it's fine. | | Meanwhile, the Home app can't be closed when viewing an | accessory because they made it a modal, the Music app | sometimes can't be searched because the search field looses | focus on every keypress, and the AppStore may crash outright. | wpm wrote: | Because I need the Settings app to work. I'm not choosing | burger toppings, I'm often in there to troubleshoot. I | can't have an app that straight up lies to me about my | network or refuses to respond to button presses I know it | saw (WiFi "Details..." button won't show anything if you've | already pressed it and closed it that session, have to quit | and relaunch). | | SwiftUIs text rendering also looks like ass, but that also | could be the result of the choice of grey on grey the | design B-team in charge of the redesign chose for text | boxes. | | I do agree though that the Home app is far worse. It sucks | on iOS and they just copy pasted it over, and that UI with | a mouse cursor is just painful and ugly. Unredeemable | software. | wlesieutre wrote: | _> SwiftUIs text rendering also looks like ass, but that | also could be the result of the choice of grey on grey | the design B-team in charge of the redesign chose for | text boxes._ | | Are you on a high DPI monitor? macOS stopped doing | subpixel antialiasing a few versions ago. It's not great | for non-retina screens, but Apple seems to think everyone | should have stopped using those by now. | mk12 wrote: | The Settings app is inexcusably bad. On my M1 Pro MBP there | is reliably 500-1000ms delay between clicking a section and | waiting for it to appear. | shilgapira wrote: | That was true in a significant number of preference pages | in the old Settings.app as well. It's probably the same | code paths under the hood of the new UI. | robertoandred wrote: | The Music app is just iTunes, not a new swift ui app | ardit33 wrote: | Yup... I liked the old one much better. | | My guess, over time, they will fix the issues, but that's the | typical hickups of a framework that is still too immature. | | It took Swift (the language) about 6-7 years to mature up. I | think the language became 'mature' only around version 5.5. | Whoever used it earlier, got to hit all kinds of weird issues | and instabilities. | | SwiftUI, will have a similar arch. My opinion is that it is | about 2-3 years to be mature enough, to replace UIKit | altogether. | novok wrote: | In iOS 2 UIKit was far more 'mature' of a framework than | SwiftUI was, and it wasn't full of missing stair steps like | basic navigation pushes working without it being a whole | irritating song and dance, lazy loading table cells & | navigation views, being able to hide the tab bar when you | push a screen on one tab with things like | "hidesBottomBarWhenPushed", etc. | | Overall I think SwiftUI when released, and even today in | some corners, is a general overall theme of incompleteness | with features available in iOS 2's UIKit. | | Did early iOS have it's irritating parts? For sure, but | they were there for performance reasons mostly and it | wasn't an 'incomplete' framework like SwiftUI is. | cvwright wrote: | Overall I really like SwiftUI. As a total iOS newbie when | it was new, I don't think I would have bothered if the | only option was to slog through UIKit. | | But all the complaints about its incompleteness are spot- | on. How did they think it was ok to launch without basic | stuff like NavigationStack? Standard Apple "piss on my | head and tell me it's raining". | PossiblyKyle wrote: | SwiftData integration (and notably the Observable macro) seems | like a huge step in the right direction for it. The problem | we've found is that integrating SwiftUI in existing UIKit apps | that also rely on stuff like RxSwift isn't easy. So far it's | only good at brand new presentations for us. Another thing is | that a lot of the great new features are locked behind iOS | targets that are plainly too new to be realistic for products | mpweiher wrote: | The genius of AppKit in particular was that it made the easy | things easy, often trivial or automatic, and the advanced | things straightforward. | | Almost every other technology I've ever seen for making things | easier hits a wall once you're outside a usually very narrow | path. ___________________________________________________________________ (page generated 2023-07-09 23:00 UTC)