grodld.bsky.social
iOS Engineer @ freelance, very bad kart racer.
125 posts
28 followers
28 following
Regular Contributor
Active Commenter
comment in response to
post
Haha will shoot you a DM when I come across the next one š
comment in response to
post
I can share some of my code if you want to see some problematic stuff
comment in response to
post
The where { switch ā¦ } syntax is crazy š
comment in response to
post
He didnāt lie to save his academics and practice because he knew it not only wouldnāt pose any threat to his career, but it would actually provide a boost, which it demonstrably did. Would love to see him keep this pose if he actually had to suffer anything for once.
comment in response to
post
Donāt think any changes to UIKit are coming our way, given what little came last year.
comment in response to
post
Both ObservableObject and Observable classes should be made MainActor.
comment in response to
post
Just a shame it so darn expensive. I had the medical excuse and fell in love later, not sure I would have got it otherwise.
comment in response to
post
Glove80 with Cherry Blossom keys feels not too mechanical and saved my wrists.
comment in response to
post
Ever tried a split ergo keyboard or should I just bother you with it until you do?
comment in response to
post
Not named and not a first American Pope, but go on I guess.
comment in response to
post
Hope he gets the gig next week
comment in response to
post
Pope wasnāt elected yet how can he play
comment in response to
post
I thought this was about SPM and got very confused when you mentioned origami.
comment in response to
post
Apple uses a lot of internal APIs which are not available to us. In UIKit you can get around that using ObjC, but with SwiftUI there is really no way to do it.
comment in response to
post
Are you trying to be edgy and wrong now? Because if so great job.
comment in response to
post
My head hurts thanks
comment in response to
post
Even worse is the Apple style of
Something(one: 1,
two: 2)
This triggers me every time I see it, especially when other people start using it.
comment in response to
post
This is triggering something deep inside me damn
comment in response to
post
Which when thinking about it seems like a #Swiftlang error, or at least a great gotcha. I would expect the compiler to infer the error type here.
comment in response to
post
Also its always ābuy it now because it has AI, which is bad (or non-existent) now, but trust us, it wil be so so good in the futureā and it never will be.
comment in response to
post
The same are hardware companies doing the whole ānow with our AIā spiel. Likeā¦and? Either it makes the product good and Iāll want it because its good, or it doesnāt do anything and I still wonāt want it. The ābuy this because it has AIā is so fucking dumb.
comment in response to
post
The applications of it are so shit they need to putt the buzzword through so much marketing and mentions.
comment in response to
post
I see any Azure logo I am getting MAD.
comment in response to
post
Small electronics manufacturer? Sucks to be you. And employees then have to find jobs with the ones who survive, i.e. big firms with political ties. Bad for competitive business. Bad for jobs. Bad for workers. And skews business to invest not in better products, but better kleptocratic relationships
comment in response to
post
Interesting!
comment in response to
post
Why is the closure marked as Binding?
comment in response to
post
I was moving some files from the main app target to an SPM package. The workflow the whole day is: Build -> let Xcode show me a single "No such module..." error -> add the dependency -> kill Xcode so it recognizes I added it after I open it -> repeat. In what world is that a production ready thing.
comment in response to
post
Haha yeah, looking forward to crawling. Ours is 6 weeks, so they stay where you leave them. Which is a great perk š
comment in response to
post
Feel ya. I stopped doing anything besides the most essential when it comes to coding, which means putting a stop to everything other than the day job. I can get back to it later, but the baby is never going to be this little again.
comment in response to
post
I am creating the Task(s) inside the VM init for now. Alternatively I could make the functions async and await them inside the task modifier, but handling that inside the VM seems preferable here, also given there are some additional layers we need between the initial VM and what is used in the View
comment in response to
post
Having it called from SwiftUI task modifier seems like leaking the functionality upwards, ideally the consumer should not care there even us an AsyncStream under the hood.
comment in response to
post
You'd think that when you change the language mode to Swift 6 for a target and you know for a fact there are errors, the build would fail. But behold, it goes through just fine š
comment in response to
post
If someone decides to not get a bank acccount ābecause it is expensiveā and gets a crypto account instead, then that someone is fucking braindead and deserves to lose the money.
comment in response to
post
The thing about these stickers is, they didn't. He was always crazy, people just didn't see it through his nerdy mask.
comment in response to
post
I think this discussion is pointless.
comment in response to
post
Oh so thatās where we donāt agreee, because the difference between writing to disk and sending requests to a remote service is quite important in my opinion.
comment in response to
post
Yeah, I am not getting how Firebase should replace CoreData/SwiftData/SharingGRDB here, given those are local databases and Firebase is a remote database system.