| Model Colors | https://apps.apple.com/app/model-colors/id1200319954 |
| https://www.linkedin.com/in/janekholm/ | |
| https://twitter.com/jan_ekholm |
That model is then used like below. Fetching does not refresh the view, but I see that it gets content. The second time I open the view it usually shows the content.
SwiftUI has so many weird gotchas and bugs like this. Probably I'm holding it wrong, but I see no reason why this should not work.
God damn the Observable stuff in SwiftUI is hard to use. For me it's always just buggy garbage.
To me this looks like a sane model for fetching some feedback (ignore the errors, I stripped out irrelevant stuff):
When you move a config file to the parent directory:
mv .env ,,
and wonder why nothing works anymore. Seems I need new glasses.
Submitted a new version of 4.14 of my app to Apple for review. It was about time as the previous version was from April.
Now I think it’s soon time to see about iOS and iPadOS 26 and fix any regressions. I don’t think there’s anything new or improved stuff in the frameworks this year, it’ll probably all be about working around new bugs Apple has introduced with this dumb new theme redesign. I don’t think anyone actually wants that stuff.
Hah, got uv to build psycopg2. For some reason it didn't check for all needed libraries and headers, but instead just failed.
So now my environment and uv.lock contains the newest versions of my dependencies. I assume I have to manually copy the new minimum versions from uv.lock to pyproject.toml, as nothing I've found seems to update the versions in that file.
This is all quite complex, but I assume there's some deeper reason that I'm just too dumb to grok.
Is it only me or does uv not have a convenient way to update packages? Trivial to install and get going, but once my packages are in pyproject.toml I can't seem to find any way to update the versions, the file still refers to old versions.
I love the speed of uv, but by god is it unnecessarily complicated to manage packages.
The “productivity” crap is all a lie.
Leadership pushing AI on the workforce is all a cover simply to scare and undermine labor, thereby gaining a permanent upper hand in hiring and negotiations. They’re inventing artificial workers as imaginary competition for your jobs.
Apple’s photo syncing is such utter garbage. It’s now been uploading 6 photos for 15 minutes. This screenshot however synced immediately. Nothing I can do either, but kill Photos and restart, which usually works. Unreliable crap.
Apple's docs are only mentioning really shallow and trivial happy cases, nothing even remotely realistic and complex. I'm sure it works ok with one class and one view, assuming you avoid all the gotchas.
If Apple did commit to fixing bugs in SwiftUI and also dogfood it a bit I guess these issues could be ironed out.
The promise of SwiftUI is great, but right now there are a huge amounts of weird things you Just Have To Know.
Having a shit day trying to understand why Observable in SwiftUI just does not work. That on top of why using a task{} to load data asynchronously would mean that all sheets get immediately dismissed once.
SwiftUI is great in theory, but it contains immense amounts of gotchas that you just have to run into a few times and learn workarounds for. I've learned now to avoid task{} and Observable altogether and continue to load data upon startup and use ObservableObject.
Jeff Johnson