I've got an extremely tough Swift / architecture problem for Cork I've been stuck on for more than a month at this point, and I am completely out of ideas… @ctietze, @mattiem, @dimitribouniol, would you find the time to lend me a hand?

It has something to do with shell output matching and translating that into an enum

https://github.com/buresdv/Cork/blob/c7ec6d35b3dff4e19cbc4e29cb1afc42eaa6f1e8/Modules/TerminalSupport/Protocols/Terminal%20Output%20Matchable.swift#L61

https://github.com/buresdv/Cork/blob/c7ec6d35b3dff4e19cbc4e29cb1afc42eaa6f1e8/Cork/Logic/Updating%20and%20Upgrading/Refresh%20Packages.swift#L108

It worked great until I needed associated values:

https://github.com/buresdv/Cork/blob/fb067fa8cb389af7466363b3473a350614e0a50f/Modules/Packages/PackagesModels/Models/Package%20Installation/Installation%20Progress%20Tracker.swift#L119

If you'd find the time, I'd appreciate it

#swift

Cork/Modules/TerminalSupport/Protocols/Terminal Output Matchable.swift at c7ec6d35b3dff4e19cbc4e29cb1afc42eaa6f1e8 · buresdv/Cork

A fast GUI for Homebrew written in SwiftUI. Contribute to buresdv/Cork development by creating an account on GitHub.

GitHub
In our CI pipeline we cache `.build` for #Swift projects keyed on Package.resolved. The cache restore works — the archive downloads cleanly at the start of the job. But then recompiles everything from scratch, including untouched dependencies.
I assume the culprit is that git checkout rewrites every source file's mtime to "now" on each run, so Swift's incremental driver sees all sources as newer than the cached artifacts and rebuilds the world.
How are you handling this?
Maybe @finestructure ?

AI agents hallucinate Apple APIs that don't exist. Cupertino fixes that by indexing hundreds of thousands of Apple documentation pages into a local, searchable database served via Model Context Protocol. Ground your AI in actual platform docs.

🔗: https://github.com/mihaelamj/cupertino by Mihaela Mihaljevic

#Swift #AI #AppleDevelopment

GitHub - mihaelamj/cupertino: A local Apple Documentation crawler and MCP server. Written in Swift.

A local Apple Documentation crawler and MCP server. Written in Swift. - mihaelamj/cupertino

GitHub

Out of time, but fixed the queue selection on tvOS (again)! Tomorrow night, let's fix some background spillover issues on macOS Tahoe. See you then!

🔜 Tomorrow’s stream: https://youtube.com/live/Qos2gTMo-YA
⏮️ Playlist so far: https://www.youtube.com/playlist?list=PLRxjf93xotuofCtaxtGOcWeuxVZYJyY-m
📲 Download Jiiiii: https://apps.apple.com/app/apple-store/id6472801548?pt=14724&ct=MastodonCCStreams&mt=8

#Jiiiii #DevStream #tvOS #visionOS #macOS #iOS #iPadOS #Anime #Swift #SwiftUI #Vapor #WebAuthn #BuildInPublic #TestFlight #PWA #WebPush

Late Night Silent Completions: Jiiiii — Part 926

YouTube

¿Tu vista de SwiftUI no se actualiza cuando debería? 🤔

Muchas veces el problema no está en SwiftUI, sino en cómo gestionamos el estado.

En este artículo repaso:

• @State vs @Binding
• El origen de la verdad
• Observation
• Errores comunes que provocan UIs desincronizadas

#Swift #SwiftUI #iOSDev #AppleDeveloper #Observation #Xcode

https://blog.arturorivas.com/posts/estado-en-swiftui-fuentes-de-verdad-observation-y-errores-comunes/

Estado en SwiftUI: fuentes de verdad, bindings y errores que aparecen cuando la vista empieza a crecer

🧭 En SwiftUI, casi todos los problemas de con el estado empiezan igual: una pantalla pequeña funciona perfectamente, se añaden dos o tres interacciones más, aparece una vista hija, luego otra, y de pronto algo deja de actualizarse, se reinicia cuando no debería o se comparte entre vistas de forma inesperada. No suele ser un fallo de SwiftUI, sino una señal de que la fuente de verdad no está colocada en el sitio correcto.

Swift Pills
Built a small SwiftUI playground for AI loading states, the repo already hit 12 stars in few days. #iOS #Swift #Apple #WWDC
https://github.com/mdo91/AI-Animation-Demo

Pero la gran sorpresa para los desarrolladores fue 𝑺𝒘𝒊𝒇𝒕: un nuevo lenguaje creado para reemplazar gradualmente la complejidad de Objective-C con una sintaxis más moderna, segura y accesible.

Ese día 𝗔𝗽𝗽𝗹𝗲 no solo renovó el aspecto del Mac: también preparó el terreno para una nueva generación de aplicaciones.

𝒀𝒐𝒔𝒆𝒎𝒊𝒕𝒆 cambió la cara del sistema. 𝑺𝒘𝒊𝒇𝒕 cambió la forma de construirlo.

#retrocomputingmx #Apple #OSXYosemite #swift #WWDC2014 #mac #ios #programacion #computerhistory #retrocomputing

El 2 de junio de 2014, durante la 𝐖𝐖𝐃𝐂, 𝗔𝗽𝗽𝗹𝗲 presentó dos piezas clave para su futuro: 𝑶𝑺 𝑿 10.10 𝒀𝒐𝒔𝒆𝒎𝒊𝒕𝒆 y el lenguaje de programación 𝑺𝒘𝒊𝒇𝒕.

𝒀𝒐𝒔𝒆𝒎𝒊𝒕𝒆 llevó al Mac hacia una interfaz más limpia, plana y conectada con iOS, reforzando funciones como Handoff, Continuity y una integración más estrecha entre Mac, iPhone y iPad.

#retrocomputingmx #Apple #OSXYosemite #swift #WWDC2014 #mac #ios #programacion #computerhistory #retrocomputing

👨‍💻In this post, I revisit a parallel computing model I worked with twenty years ago and re-implement it in Swift. No async/await, no actors, just a task DAG, work-helping, and a fixed pool of real OS threads. The result matches Swift's structured concurrency on most workloads and beats it on some. Galaxy collisions and crowd simulations included.

https://otavio.cc/posts/twenty-years-later-coltrane

#Swift #macOSDev #BlogPost

Twenty Years Later: Coltrane - Otávio C.

For a year before starting my Computer Science master's, I worked as a researcher for a research group that was developing a parallel computing runtime called Anahy1,2. I wasn't there...

Otávio C.