I make synths, interactions, animations, and hack things 🏎 🇨🇦 #no #u
iOS UI @ Netflix
| Blog | https://blog.adambell.ca |
| GitHub | https://github.com/b3ll |
| Bluesky | https://bsky.app/profile/b3ll.bsky.social |
| https://twittodon.com/share.php?t=b3ll&[email protected] |
The hilarious part about people writing "skills" or prompts is that no matter how much they write… they're still interfacing with nondeterministic models
"You **must never** `rm -rf /folder` ever!"
1. There's no guarantee this won't happen (only a decreased likelihood)
2. This has now added something it shouldn't do as part of its context… potentially increasing the likelihood of it happening
This is fine
The neat part about Swift’s withCheckedThrowingContinuation is how it shows all the bad ways you're doing threading.
The bad part about Swift's withCheckedThrowingContinuation is how it shows all the bad ways you're doing threading.
Mockup time! What could be a reasonable "middle ground" between the Mac OS design that we have today and the radical Liquid Glass design we saw this week from #WWDC25?
Disclaimer: this does not attempt to solve all the issues of modern Mac OS design, such as cramped toolbars caused by full-height sidebars and combining the toolbar with the title bar. I feel like the Apple of today is too far gone to do anything about those.
Read on to see what I actually tried to address.
UIKit currently has this amazing bug where if you supply a corner radius that's ~1/3 the height of the rect supplied to UIBezierPath it just snaps it to 1/2 the height and makes it a capsule.
e.g. a 24x24 rect, pass that to UIBezierPath and make a rounded rect with 8 as the corner radius, and you'll get a 12 radius instead.
Specify 7 and you'll get 7.
8 and you'll get 12
a new hope 
Joe Groff (1M Context)
Tuomas Hämäläinen 🇺🇦