Jacob Clayden 

NEW TWEAK! Iris — Put the sparkle back in 'i'Message! Available now @CharizTeam. Read the Reddit post for more information: reddit.com/r/jailbreak/co…

@TimSweeneyEpic @AndroidAuth Want to jailbreak your phone? Go ahead—but you have to answer a few multiple-choice questions correctly to access it! Hell, you could even require the user to write a fizzbuzz solution. The point is to add friction, essentially eliminating the chances of someone being scammed.

@TimSweeneyEpic @AndroidAuth I’ve always thought that the simplest way to give users advanced permissions would be to gate it behind a tech quiz.

I don’t recognize the Android I fell in love with anymore androidauthority.com/i-dont-recogni…

@merlindru @benhylak @skiptools @pointfreeco @stephencelis Also, if you're interested in @pointfreeco's tools, you can join their Slack at pointfree.co/slack

@merlindru @benhylak @skiptools @pointfreeco @stephencelis There's a Slack in the page header over at skip.dev

narrator: it is not

@merlindru @benhylak @skiptools @pointfreeco @stephencelis Stuff it all in the frameworks, but ✨ elegantly ✨. SkipFuseUI re-exports SwiftUI on Android, so as long as SkipUI supports the same API surface, @pointfreeco's tools can integrate with it. A lot of my work has been focused on this to make it transparent to app developers.

@jcxdev @benhylak @skiptools @pointfreeco @stephencelis faaaaaaaawck how??????/

@merlindru @benhylak @skiptools Hah, I wish—I’m just an aspiring contributor! @marcprux is the genius you’re thinking of.

@jcxdev @benhylak @skiptools oh shit you're the guy behind skip? i've read about that project a good while ago and was extremely impressed because it's an endeavor many tried and all failed at, yet you seem to have it working. good luck with it!!

@merlindru @benhylak @skiptools @pointfreeco @stephencelis Oh, and did I mention there's zero app-level conditional compilation?

@merlindru @benhylak @skiptools (This is running on Android using @pointfreeco's swift-composable-architecture 1.25.2, SQLiteData, swift-dependencies, and more… all powered by Swift's observation tools and @skiptools' runtime bridging. @stephencelis I promise I'll make that GitHub discussion soon…ish.)

@merlindru @benhylak hopperapp.com

@merlindru @benhylak Hopper is just a disassembler for macOS which is almost purpose-built for Objective-C & Swift. It's similar—and yet different in the ways that matter—to Ghidra and IDA Pro. It has a built-in MCP which, when combined with its Apple affinity, makes Hopper a very compelling product.

@merlindru @benhylak I appreciate that, but more context than a stripped binary is hardly comparable to source code. This is coming from a huge proponent of Hopper's MCP btw—I even requested some additions which are being worked on. But as with anything, it's important to recognise the limitations.

@jcxdev @benhylak sure but we also get the header files and a bunch of internal usage examples as far as i'm aware (folks routinely post about how apple uses their frameworks so im guessing symbols are shipped in most apple binaries) so there's a lot more context to work with than raw executables

@merlindru @benhylak LLMs can be great tools for interpreting disassembly or decompilation output, but their correctness is limited by that of the decompiler, lack of context, hallucinations, and confident incorrectness.

@merlindru @benhylak Disassembly can only get you so far. Things are mangled, encoded, use weird math, compiler optimisations are a thing, and spread across a binary (often multiple).

@jacobtechtavern @skiptools I must admit, I do miss the lottery of coming into the office to see whether I'll be Jacob's MacBook Pro or Jacob's MacBook Pro 2 for the day!

@jcxdev @skiptools I’ll never blame a fellow Jacob

Oh god, make it stop. I wish I could go back to five minutes ago before I had this knowledge

@adxtyahq Allow me to introduce you to: omarchy.org I'll never leave macOS, but I damn well want to leave Windows for this.

macOS Tahoe might be the worst Apple update ever my laptop now lags out of nowhere this thing didn’t stutter even for a millisecond before actually considering switching to Windows now

Not again… @bcherny what is going on recently? 🥲

@twannl Have you considered providing credit where knowledge has been sourced verbatim from third parties?

My iOS Agent Skills are packed with knowledge. I even include things you'd think an LLM already knows, like: - "Use Observable instead of ObservableObject" - "Use async/await instead of DispatchQueue" You might think Agents know these things, but in my experience: - They need strict guidance - They still make rookie mistakes - They get influenced by your code patterns, which often still use older APIs Even though training data is there, my Agent Skills guide your agents toward better iOS development. The risk of this approach is token usage. An inefficient skill will eat your context, leaving less room for the actual task. That's why my skills are: - Optimized for token usage - Designed for Agents navigating through reference files Code examples are intentionally minimal: just enough for an Agent to know what to do, nothing more. The latest release of my Concurrency Agent Skill saves ~4,000 tokens per query through smart routing, with zero loss in knowledge depth. Quick install instructions below 🚀 What Agent Skills are you using for iOS development?

@jacobtechtavern Poor understanding of identity is usually to blame… besides SwiftUI itself, of course. I hope Apple's rewritten SpringBoard in SwiftUI with iOS 26, as that would explain iOS 26.3's extremely poor performance and incentivise them to finally address it properly all in one go!

SwiftUI vs UIKit: the head-to-head scroll performance comparison I have crappy perception, so didn’t rate my ability to feel minor animation issues. But during my first run, I felt two very noticeable hangs, where the UI was briefly unresponsive betwixt tap and scroll. But this wasn’t the half of it. Once I looked at my proper instruments trace, I felt like the detective barging into a Jack The Ripper’s crime scene. - 78 hitches (frame drops) in 24 seconds of running. - 2 severe hangs (unresponsive UI) of ~2 seconds each. This was consistent across multiple runs. Average hitch duration was just over 24ms, meaning ~3 dropped frames per hitch. The UI threw up 3.4 hitches per second. Given that I struggled to perceive this, I should think about going to Specsavers. You can see clusters of red lines on the Hitches trace, representing more frame drops where I was scrolling more rapidly. Memory, CPU, and thermal profile with Xcode So scroll performance wasn’t great. For UIKit, I did the same set of tests, the same number of times. Load, scroll, scroll faster, and play with the gifs. I freely admit I’m not enormously perceptive, but there was something there. The SwiftUI one, even before looking at the trace, and experiencing the UI freeze, felt unexplainedly off. The UIKit version had no such problems. It just felt like it worked, and no part of my lizard brain was screaming. When it comes to the actual Instruments trace, UIKit is kind of showing off. Across my tests, I measured 0.7 hitches per second (compared to 3.4 for SwiftUI). Average hitch duration was the same. No hangs were detected, but there were a couple of brief (38ms) interaction delays, highlighted in grey. Read my scientific performance comparison right here 🧪 blog.jacobstechtavern.com/p/swiftui-vs-u…