Here's one for the icons-in-menus haters on macOS Tahoe:
defaults write -g NSMenuEnableActionImages -bool NO
It even preserves the couple of instances you do want icons, like for window zoom/resize
/cc @gruber
| website | https://www.thinkpractice.nl |
| https://www.linkedin.com/in/tjadejong2 |
Here's one for the icons-in-menus haters on macOS Tahoe:
defaults write -g NSMenuEnableActionImages -bool NO
It even preserves the couple of instances you do want icons, like for window zoom/resize
/cc @gruber
While I certainly think AI tools like Codex have their merits, I often wonder where this need for speed and more and more productivity is heading. I enjoy being able to finish things I wasn’t able to before (or in less time) but I also miss the joy of coding when I am using them. This article also hits the nail on the head:
https://lucumr.pocoo.org/2026/3/20/some-things-just-take-time/
Some thoughts on @stroughtonsmith's month with Codex, what's happening to software development, and the blurry lines between human art forms and AI:
https://www.macstories.net/linked/a-developers-month-with-openais-codex/

An eye-opening story from Steve Troughton-Smith, who tested Codex for a month and ended up rewriting a bunch of his apps and shipping versions for Windows and Android: I spent one month battle-testing Codex 5.3, the latest model from OpenAI, since I was already paying for the $20 ChatGPT Plus plan and already had access

TelemetryDeck is an app analytics service specifically for developers, designed to manage usage analytics that are anonymized, privacy-focused, and really easy to use. TelemetryDeck is managing the data of over 16 million people every month, helping thousands of app publishers improve their products, and we’re doing it all with a Swift-based infrastructure.
@MuseumShuffle remembering your talk @SwiftLeeds last year while working on my app. So guess what I'm struggling with.... 😃
Just booked for my next @SwiftLeeds ! Looking forward. Anyone else going?

It's time to take off for the 6th edition of SwiftLeeds, a mobile iOS Swift conference in the heart of Leeds, UK. We're super excited to reach new altitudes for this year's event, which is hosted in Leeds, a diverse, vibrant city that is accessible to all. 🛫 With a diverse panel of expert speakers from the community and the chance to network with like-minded people, it's time to prepare for boarding 🧑✈️ All tickets will be provided with the following: Unique SwiftLeeds merchandise Local Food (breakfast/lunch/snacks) Freshly made drinks (hot & cold) Access to the whole venue to network with others A FREE 1-1 Drop-In Session with one of our on-site experts We can't wait to welcome you aboard this year!
🚀 GRDB 7.10.0 is out! This release ships the hard work of @marcprux, @tjadejong and Micah Moore for supporting Android, Linux, Windows, and SQLCipher with SPM (for encrypted databases).
The situation of GRDB+SQLCipher with SPM is much better, but still not all sunshine and roses. You must fork GRDB, and modify Package.swift. Instructions are in the file itself, in comments that contain "GRDB+SQLCipher".
Maybe an "official" fork will ship eventually–this is still under discussion. In all cases, SQLCipher will need a GRDB fork for several years to come, which means that all derived repositories (GRDBQuery, GRDBSnapshotTesting, SQLiteData, etc) will need to be forked as well.
What are we currently lacking in order to avoid forks?
We need Xcode to support package traits. Only package traits can reliably link GRDB with SQLite, or SQLCipher, but not both.
We also need SPM to stop downloading unused dependencies, because I do not want that your projects download SQLCipher, or declare a dependency on SQLCipher, when you do not use it. And when GRDB adds more traits for more SQLite and SQLCipher variants, I do not want that those are downloaded, too.
RE: https://mas.to/@SwiftPackageUpdates/116076598841202063
Glad to have been able to contribute! GRDB should now again build on Linux (and more)!
@danielsaidi I was reading your article: https://danielsaidi.com/blog/2025/12/02/a-better-way-to-localize-swift-packages-with-xcode-string-catalogs
And I've since moved all my Localizable.xcstrings to my SPM packages. However, Xcode is now marking all translations as stale (unless I marked them as manual). Is this to be expected?