JD
banner
greentea.bsky.social
JD
@greentea.bsky.social
SWE/MLE by day, iOS dev in my free time. Trying to journal my progress on my side projects!
This has helped! And lazy loading views that are part of a navigation stack
July 14, 2025 at 2:07 AM
Fuel for the Monday morning commute 🙌 cheers
July 13, 2025 at 11:18 PM
Yeah 😔 appreciate the help though! I’ll let you know if I figure out a workaround 🙂
July 13, 2025 at 7:17 PM
Yeah, thats a solid idea. I’m generating these Entity objects programmatically (just from the default cube resource). I looked into Model3D but I thought maybe it was for rendering models from file only. I’ll give it another look though! Hopefully you’ll have solved my memory usage issues :-)
July 13, 2025 at 7:00 PM
I think I’ll need to provide a preview another way, either with just a screenshot or a small video or something. But it was fun to provide a preview that showed the entity rotating in real time! Like this, but times like, 20 LOL #ios #augmentedreality
July 13, 2025 at 12:52 AM
As someone working on an AR app, I have this exact problem. I can test properties all day but testing the ~look~ of something is much harder to pinpoint
July 12, 2025 at 10:33 PM
Save us, Iain Banks 🙏
July 11, 2025 at 2:35 AM
I’ve just been using the vim mode in Xcode and pretending 😭 love neovim but need device simulators for most of my swift dev work
July 4, 2025 at 5:15 PM
Nvm, just read through the full proposal and I think it answered my questions
July 2, 2025 at 1:56 PM
This would be amazing, and the proposed form reminds me of C++/Rust, which is great uniformity.

I can’t say I’ve encountered this problem in Swift before. Does the compiler warn you about ambiguous naming? Would it warn you/stop you in the future?
July 2, 2025 at 12:22 PM
The tools aren’t even consistent, e.g loading my 3D USDZ model in Xcode (left) vs. Preview (right)
July 2, 2025 at 12:15 PM
It’s dog.fill IRL!! Or I’ve been spending too much time in SF symbols 😅😵‍💫
June 30, 2025 at 2:04 AM