Social 📸 Photography

Adam FowlerI made a thing <a href="https://mastodon.scot/tags/valkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#valkey</a> <a href="https://mastodon.scot/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> <a href="https://valkey.io/blog/valkey-swift/" rel="nofollow noopener" translate="no" target="_blank">https://valkey.io/blog/valkey-swift/</a>

Christian TietzeIs there a <a href="https://mastodon.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> linting tool that marks e.g. NavigationView usage where new APIs should be used?

Jason SadlerNES Emulator: CPU InstructionsI’m <a href="https://www.sadlerjw.com/2025/07/31/writing-an-nes-emulator-in-swift/" rel="nofollow noopener" target="_blank">writing an NES emulator</a> in Swift!The NES uses a <a href="https://en.wikipedia.org/wiki/MOS_Technology_6502" rel="nofollow noopener" target="_blank">6502</a> processor, which has 3 normal registers (<code>a</code>, <code>x</code>, and <code>y</code>) and defines its own instruction set of <a href="https://www.nesdev.org/wiki/Instruction_reference" rel="nofollow noopener" target="_blank">56 instructions</a>. That makes for a lot of little tiny implementations! Addition (<a href="https://www.nesdev.org/wiki/Instruction_reference#ADC" rel="nofollow noopener" target="_blank"><code>ADC</code></a>) and subtraction (<a href="https://www.nesdev.org/wiki/Instruction_reference#SBC" rel="nofollow noopener" target="_blank"><code>SBC</code></a>) are probably the most complex ones, with the latter taking me some two hours to figure out simply because it’s the first time since 2004(?) that I’ve had to think about binary math and <a href="https://en.wikipedia.org/wiki/Two%27s_complement" rel="nofollow noopener" target="_blank">two’s complements</a>. Luckily (or annoyingly depending on your point of view) many of the instructions are nearly identical, especially the six “transfer” instructions, which just copy values between different registers.While the obvious thing might have been to implement each instruction as a small function on my <code>CPU</code> class, I wanted to break each out into its own file to avoid making it a multi-thousand-line mess. Having each instruction implemented as its own struct also gives me the flexibility to turn each into a little state machine if I decide to make my emulator clock-accurate in the future. For the time being, each instruction fully executes on its first clock tick, and then the CPU just spins for the <a href="https://www.nesdev.org/wiki/6502_cycle_times" rel="nofollow noopener" target="_blank">correct number of ticks</a> before executing the next instruction. So my current implementation is duration-accurate, but not clock-accurate.The <a href="https://github.com/sadlerjw/SwiftNES/blob/9dcf155f4f54918bcf6afde4d5dc7ba8a27ef9b7/NES-iOS/Emulator/Instructions.swift#L8" rel="nofollow noopener" target="_blank"><code>Instruction</code> protocol</a> that each instruction conforms to just defines an <code>execute</code> method that takes the CPU as an argument. Since the instruction naturally needs to be able to fully access the CPU, one downside of this arrangement is that none of the CPU’s state can be declared private. The <code>NES</code> class is the only other code with a reference to the CPU, but it does expose it as public so that I can create some <a href="https://www.sadlerjw.com/wp-content/uploads/2025/08/Simulator-Screenshot-Clone-2-of-iPhone-16-Pro-2025-08-02-at-15.03.19.png" rel="nofollow noopener" target="_blank">debugging UI</a> with access to its registers. Maybe I can mitigate that with some module boundaries. We’ll see.Because I have no idea what I’m doing (and because I hope the source can be a bit of a portfolio piece to show to potential employers), <a href="https://github.com/sadlerjw/SwiftNES/tree/main/NES-iOSTests" rel="nofollow noopener" target="_blank">I wrote unit tests</a> for each instruction and addressing mode.One mistake I made is forgetting that of course some instructions write to memory! Since most of the instructions just read values and store results in registers, I had the CPU’s <code>tick</code> function use the current addressing mode to fetch the appropriate value and make it available to the instruction via a property on <code>CPU</code> before calling the instruction’s <code>execute</code> method. When I got to read-modify-write instructions like <a href="https://www.nesdev.org/wiki/Instruction_reference#ASL" rel="nofollow noopener" target="_blank"><code>ASL</code></a>, I let the instruction return a value from <code>execute</code> and then the tick function would use the addressing mode to write it back to where it came from.But wait! There’s another complication! <a href="https://www.nesdev.org/wiki/Instruction_reference#JMP" rel="nofollow noopener" target="_blank"><code>JMP</code></a> actually needs to read two bytes from memory. (Addresses are 2 bytes long, but memory reads and writes only operate on a byte at a time.) This means I need to store the address from the addressing mode so that the instruction can read the extra byte from the following address.I think sometime down the road instead of having the CPU’s <code>tick</code> method try to be smart and do these things, I’ll just pass the addressing mode into the instruction’s <code>execute</code> method and let it read and write exactly what it needs. Whoops!I finally finished implementing all of the instructions and I’m on to the <a href="https://www.nesdev.org/wiki/PPU" rel="nofollow noopener" target="_blank">PPU</a>, starting with its memory-mapped registers that are exposed on the CPU’s bus. Reading and writing these registers cause side effects within the PPU! More interesting times ahead! Stay tuned for more.If you’re interested in following along you can find the code <a href="https://github.com/sadlerjw/SwiftNES/" rel="nofollow noopener" target="_blank">on Github</a>. <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://www.sadlerjw.com/tag/emulation/" target="_blank">#emulation</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://www.sadlerjw.com/tag/nes/" target="_blank">#nes</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://www.sadlerjw.com/tag/programming/" target="_blank">#programming</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://www.sadlerjw.com/tag/swift/" target="_blank">#swift</a>

David BurešGuys, I'm trying to make the swift-dependencies framework work for CorkAm I misunderstanding something, or can @Observable classes not be registered as dependencies?I have a @MainActor @Observable class, and when I try to register it, I get the error "Main actor-isolated static property "liveValue" cannot be used to satisfy nonisolated protocol requirement." I looked it up but can't figure it outMaybe the great async sage <a href="https://mastodon.social/@mattiem" class="u-url mention" rel="nofollow noopener" target="_blank">@mattiem</a> has some insight? :blobcatpatyou: <a href="https://hachyderm.io/@pointfreeco" class="u-url mention" rel="nofollow noopener" target="_blank">@pointfreeco</a> <a href="https://mstdn.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a>

🇨🇦 Steve"Steve, that makes no sense."I agree. Yet where we are. See screenshots. <a href="https://appdot.net/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a>

🇨🇦 SteveThis code:viewModel.selectedClasses.remove(at: index)…fails. Ambiguous use of remove(at:). Should be mutable, but whatever.This code:var classes = viewModel.selectedClasses classes.remove(at: index) viewModel.selectedClasses = classesWorks. Fine.Now the weird part. If I put the second code after the first code, BOTH ENABLED, the first code now compiles (but second remove is now redundant, of course).Any ideas? <a href="https://appdot.net/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a>Edit: remove(at:) returns a result. Prefixing with _ = fixes.

Natalia PanferovaIf you haven't got my book SwiftUI Fundamentals yet, this week there is a great chance to grab it with a 30% discount! Folks from Those Who Swift are running a special promotion, check out their latest newsletter for details: <a href="https://thosewhoswift.substack.com/p/those-who-swift-issue-225" rel="nofollow noopener" translate="no" target="_blank">https://thosewhoswift.substack.com/p/those-who-swift-issue-225</a> <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftUI</a> <a href="https://mastodon.social/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOSDev</a> <a href="https://mastodon.social/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a>

trozI have just published my almost-annual article on the new features of SwiftUI and Swift as they apply to Mac apps:<a href="https://troz.net/post/2025/swiftui-mac-2025/" rel="nofollow noopener" translate="no" target="_blank">https://troz.net/post/2025/swiftui-mac-2025/</a>I'm not using HTTP Cats this year, but the icon has a cat, so all is well.<a href="https://mastodon.social/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftUI</a> <a href="https://mastodon.social/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a> <a href="https://mastodon.social/tags/WWDC" class="mention hashtag" rel="nofollow noopener" target="_blank">#WWDC</a> <a href="https://mastodon.social/tags/WWDC2025" class="mention hashtag" rel="nofollow noopener" target="_blank">#WWDC2025</a>

Natalia PanferovaThe July issue of the Nil Coalescing newsletter is out! It’s been sent to all email subscribers and is now also available online. I’ve shared some key takeaways from Apple’s WWDC recap event, plus links to my latest videos and blog posts: <a href="https://nilcoalescing.com/newsletter/2025-07-30" rel="nofollow noopener" translate="no" target="_blank">https://nilcoalescing.com/newsletter/2025-07-30</a> <a href="https://mastodon.social/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOSDev</a> <a href="https://mastodon.social/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a>

David BurešJust got a simple app idea:You put in a Reddit username, and based on your requirements, it will go through the last few comments of that user and use an LLM to tell you if it’s worth arguing with themLike and subscribe and hit that bell if you want to follow the development of this app<a href="https://mstdn.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> <a href="https://mstdn.social/tags/swiftui" class="mention hashtag" rel="nofollow noopener" target="_blank">#swiftui</a> <a href="https://mstdn.social/tags/macdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#macdev</a> <a href="https://mstdn.social/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOSDev</a>

Pedro PiñeraMaking Tuist’s server code source available and merging it to a monorepo have been huge productivity boosters <a href="https://mastodon.pepicrft.me/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a><a href="https://tuist.dev/blog/2025/07/08/server-fcl" rel="nofollow noopener" translate="no" target="_blank">https://tuist.dev/blog/2025/07/08/server-fcl</a>

John<a href="https://expressional.social/tags/nature" class="mention hashtag" rel="nofollow noopener" target="_blank">#nature</a> <a href="https://expressional.social/tags/birds" class="mention hashtag" rel="nofollow noopener" target="_blank">#birds</a> <a href="https://expressional.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> <a href="https://expressional.social/tags/nestbox" class="mention hashtag" rel="nofollow noopener" target="_blank">#nestbox</a> Make a Swift Box before 2026 ! Much of the current building stock is either new or renovated. This has led to the disappearance of many nesting sites for Swifts due to different building standards than before. The species has had a dramatic decline. <a href="https://www.fuglevennen.no/arkiv/?vis=oppslag&op_id=1647&fbclid=IwY2xjawL1_M1leHRuA2FlbQIxMAABHuKJa1X2dEX7SBRv09ToXJtQWr4LBFHtTQlrKAsFVGxGxWz__YjUbAuaNjTw_aem_SFe9YtkhTG3rHBuiSsxHBg" rel="nofollow noopener" translate="no" target="_blank">https://www.fuglevennen.no/arkiv/?vis=oppslag&op_id=1647&fbclid=IwY2xjawL1_M1leHRuA2FlbQIxMAABHuKJa1X2dEX7SBRv09ToXJtQWr4LBFHtTQlrKAsFVGxGxWz__YjUbAuaNjTw_aem_SFe9YtkhTG3rHBuiSsxHBg</a>

obrhoffLooking at CKSyncEngine, I find it a bit surprising that this wasn’t implemented. Wouldn’t you want to know which table or record type you’re deleting from, rather than just passing in an ID with no context?It works fine in the example Apple provided, but conveniently they only sync a single type of entity. Now it seems people encode the Record Type into the ID and parse it out. 😭 <a href="https://mastodon.social/tags/iosdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#iosdev</a> <a href="https://mastodon.social/tags/macosdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#macosdev</a> <a href="https://mastodon.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a><a href="https://github.com/apple/sample-cloudkit-sync-engine/issues/12" rel="nofollow noopener" translate="no" target="_blank">https://github.com/apple/sample-cloudkit-sync-engine/issues/12</a>

Eshu MarneediIf anyone has any insight on this, I’d love to know, but for now, app intents will be ripped out of the next Citations build unless I can find a solution. <a href="https://mastodon.social/tags/SwiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftUI</a> <a href="https://mastodon.social/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a>

iOS Dev Jobs👋 We’re hiring an Apple Engineer at Doist! Join us to build legendary tools like Todoist and Twist; simple yet powerful. Work from anywhere, own projects end to end, and collaborate asynchronously in a team that values ambition, mastery, independence, and communication. <a href="https://iosdevjobs.com/jobs/m-5b9d2bb0-acef-40a3-bc6a-218397889b55" rel="nofollow noopener" translate="no" target="_blank">https://iosdevjobs.com/jobs/m-5b9d2bb0-acef-40a3-bc6a-218397889b55</a> <a href="https://iosdev.space/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a> <a href="https://iosdev.space/tags/SwiftLang" class="mention hashtag" rel="nofollow noopener" target="_blank">#SwiftLang</a> <a href="https://iosdev.space/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOSDev</a> <a href="https://iosdev.space/tags/MacDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacDev</a> <a href="https://iosdev.space/tags/iOSDevJobs" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOSDevJobs</a>

TootSDKA new release of TootSDK - 17.0.0 📣 <a href="https://github.com/TootSDK/TootSDK/releases/tag/17.0.0" rel="nofollow noopener" translate="no" target="_blank">https://github.com/TootSDK/TootSDK/releases/tag/17.0.0</a>What's changed:- Quote posts <a href="https://mastodon.online/@dale_price" class="u-url mention" rel="nofollow noopener" target="_blank">@dale_price</a> - Support Mastodon 4.4 account management additions <a href="https://mastodon.online/@dale_price" class="u-url mention" rel="nofollow noopener" target="_blank">@dale_price</a> - Masto 4.4 media deletion <a href="https://mastodon.online/@dale_price" class="u-url mention" rel="nofollow noopener" target="_blank">@dale_price</a> - Add missing Mastodon properties to InstanceV2 <a href="https://mastodon.online/@dale_price" class="u-url mention" rel="nofollow noopener" target="_blank">@dale_price</a>Community contributions are greatly appreciated 🙌 <a href="https://iosdev.space/tags/iOSDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOSDev</a> <a href="https://iosdev.space/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a> <a href="https://iosdev.space/tags/TootSDK" class="mention hashtag" rel="nofollow noopener" target="_blank">#TootSDK</a> <a href="https://iosdev.space/tags/Fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fediverse</a>

Cork: The Homebrew CompanionCork version 1.5.6 is out. This update includes a complete rewrite of the Homebrew pinning system in Swift for 20x performance gains, pinning from sidebar, manual update checking, and fixes for many crashes.See <a href="https://open.substack.com/pub/corkapp/p/cork-156-out-big-changes?r=2vioyx&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true" rel="nofollow noopener" translate="no" target="_blank">https://open.substack.com/pub/corkapp/p/cork-156-out-big-changes?r=2vioyx&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true</a> for more info.Buy Cork to support its development: <a href="https://corkmac.app" rel="nofollow noopener" translate="no" target="_blank">https://corkmac.app</a>Join the Discord community: <a href="https://discord.gg/kUHg8uGHpG" rel="nofollow noopener" translate="no" target="_blank">https://discord.gg/kUHg8uGHpG</a>See the source code: <a href="https://github.com/buresdv/Cork" rel="nofollow noopener" translate="no" target="_blank">https://github.com/buresdv/Cork</a><a href="https://mstdn.social/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> <a href="https://mstdn.social/tags/swiftUI" class="mention hashtag" rel="nofollow noopener" target="_blank">#swiftUI</a> <a href="https://mstdn.social/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> <a href="https://mstdn.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a> <a href="https://mstdn.social/tags/buildinpublic" class="mention hashtag" rel="nofollow noopener" target="_blank">#buildinpublic</a> <a href="https://mstdn.social/tags/macdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#macdev</a> <a href="https://mstdn.social/tags/homebrew" class="mention hashtag" rel="nofollow noopener" target="_blank">#homebrew</a> <a href="https://mstdn.social/tags/CorkApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#CorkApp</a>

distrustful dinosaursimagine you're a bug flying around minding your own business and this is the last thing you see 🐝😱🪶<a href="https://pigeons.club/tags/birds" class="mention hashtag" rel="nofollow noopener" target="_blank">#birds</a> <a href="https://pigeons.club/tags/swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#swift</a> <a href="https://pigeons.club/tags/swifts" class="mention hashtag" rel="nofollow noopener" target="_blank">#swifts</a> <a href="https://pigeons.club/tags/urbanwildlife" class="mention hashtag" rel="nofollow noopener" target="_blank">#urbanwildlife</a>

Sean CoatesI was recently asked “Why did you choose <a href="https://scoat.es/tags/Swift" class="mention hashtag" rel="nofollow noopener" target="_blank">#Swift</a> for Studioworks?”There are reasons that I intend to write about; strong-but-approachable types is a key reason. I was just catching up on a talk from <a href="https://mastodon.social/@mattiem" class="u-url mention" rel="nofollow noopener" target="_blank">@mattiem</a> where he said the following:“[Swift Concurrency] is taking information that—you *hope*—you can find in the documentation and it is moving it into the type system in a way that you can no longer ignore.”Indigenous first-class strong typing is a beautiful thing.<a href="https://youtu.be/N5iIXwBW54A" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/N5iIXwBW54A</a>

Kevin Karhan :verified:<a href="https://toad.social/@KimPerales" class="u-url mention" rel="nofollow noopener" target="_blank">@KimPerales</a> I consider the actions.of the <a href="https://infosec.space/tags/Trump" class="mention hashtag" rel="nofollow noopener" target="_blank">#Trump</a> regime to be <a href="https://infosec.space/tags/blackmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#blackmail</a> and expect the cancellation of any <a href="https://infosec.space/tags/DataSharing" class="mention hashtag" rel="nofollow noopener" target="_blank">#DataSharing</a> agreements and automatic retaliatory <a href="https://infosec.space/tags/tariffs" class="mention hashtag" rel="nofollow noopener" target="_blank">#tariffs</a> against the <a href="https://infosec.space/tags/USA" class="mention hashtag" rel="nofollow noopener" target="_blank">#USA</a>, including the cancellation of <a href="https://infosec.space/tags/FATCA" class="mention hashtag" rel="nofollow noopener" target="_blank">#FATCA</a> & <a href="https://infosec.space/tags/ESTA" class="mention hashtag" rel="nofollow noopener" target="_blank">#ESTA</a> as well as <a href="https://infosec.space/tags/SWIFT" class="mention hashtag" rel="nofollow noopener" target="_blank">#SWIFT</a> arrangements and noncompliance with <a href="https://infosec.space/tags/US" class="mention hashtag" rel="nofollow noopener" target="_blank">#US</a> <a href="https://infosec.space/tags/sanctions" class="mention hashtag" rel="nofollow noopener" target="_blank">#sanctions</a>.<a href="https://infosec.space/tags/sarcasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#sarcasm</a> <a href="https://infosec.space/tags/EUpol" class="mention hashtag" rel="nofollow noopener" target="_blank">#EUpol</a>

Recent searches

Search options

Administered by:

Server stats:

#swift