Curtis Hard

Guessing no-one at Apple checked what happens when you have folder sharing on and Finder displays the opaque bar at the top... obviously looks even worse further right you go.

The amount of slop that is being released on mac recently due to AI just creating … slop is insane. It’s gotten to a point where people are now posting “how do i fix this EXC_BAD_ADDRESS” on reddit because they have no idea what it is and expecting a single line answer. The code shared has more race conditions than an F1 season. The performance sucks, UI barely works and people are making money from that crap. What.

Been working on the next version of IconJar for the past 2 years or so (version 3.0), no vibe coding, just pure Swift (SwiftUI used in the sheets) but AppKit everywhere else.

Slowly getting there, a lot to do, but a complete rewrite from 2.0 which was Objective-C.

Loads of new features, new formats supports. Watch this space :-)

NSView's isFlipped i would had thought should be MainActor only, but ... when using drag n drop, if you hit the limit of whatever AppKit decides it wants to chunk up drag n drop items into multiple threads, it can call isFlipped on a background thread, so you MUST mark it as nonisolated (if you subclass) or it will crash

@marioguzman@mastodon.social cant work out if this is sarcastic or not ….

I’m sorry, but when people say on their app page “optimized for Apple Silicon” what does that mean exactly? Have they gone out the way to do AS only code or ASM or, just let the compiler compile ARM and x86 automatically? - at no point since AS has come out have I written anything specific for that platform 🤷‍♂️.

I don't think I've ever worked on fixing issues on a macOS release as buggy and sloppy and Tahoe. Everything seems like it's held together with semi wet turd and a slight prod breaks it. The amount of work arounds to just fix an issue that only exists on Tahoe is insane. Chances are my work arounds will break once the rdars are fixed 🥲

@siracusa@mastodon.social Hey - what was your workaround for the jumping controls in SwiftUI in Tahoe? I have a basic form and mousing over each row seems to make it move around 😅

Reason being is we need to load a library, but check up-front if we need to perform a light weight, or any form of CoreData migration, if we do, we need to backup the library you are trying to load with the model that matches that library, not the one that we are migrating too. The backup can take time as it needs to copy the stores + icons etc, so needs to be some UI for the user, but all in the same flow as loading a library and presenting it at the end.

That moment you have to completely refactor how you load a Library (in IconJar) because of a single asyn function that needs to be made synchronous. Cant use a semaphore and wait as it causes a deadlock on the thread due to its internals, so have to completely move over to async await just for that one part (i say part, loading a library is a big part)…