Profile avatar
richoncode.bsky.social
Spatial developer.
52 posts 117 followers 433 following
Regular Contributor
Active Commenter
comment in response to post
Great to see!
comment in response to post
Copy on mutate may be more efficient if multiple properties are the same.
comment in response to post
Nicely done. Very clear to follow.
comment in response to post
Free. Unless you have mega demand and need to show demand to get funding to finish.
comment in response to post
struct SubValue: ExpressibleByStringLiteral, LosslessStringConvertible { let value: String //LosslessStringC… init?(_ description: String) { self.value = description } // ExpressibleByStrin… init(stringLiteral value: String) { self.value = value } }
comment in response to post
Swift for matter devices is an option. There are advantages of shared code for your projects. developer.apple.com/documentatio...
comment in response to post
Not familiar with the app. Thought about the concept. Can scale well especially when you think of subscription service and language barriers. Expats wanting to engage more with new community being able to make lists of events to meet more people.
comment in response to post
This one is more than “some skill”. AI will get better faster at this one than most human developers. Once AI has been trained on all the anti-patterns. We’ve been trying to get humans good in this space for decades. Did you ask ai to scrub for secure code? It should have a lot of data.
comment in response to post
Any current way to follow him in social?
comment in response to post
Atlas? 1960?
comment in response to post
Have a debug flag to pause changes. If stalls still happen then some other code is the cause.
comment in response to post
Works on iphone 12. The enter AR button does not dismiss. Pretty water.
comment in response to post
Are you creating and destroying the objects? Instead, recycle the faded out ones to the back again. This way no object creation occurs an no garbage collection is needed. The memory level is constant.
comment in response to post
Wonderfully efficient.
comment in response to post
Its so bad. Chatgpt is my goto search engine for apple apis.
comment in response to post
Great summary!
comment in response to post
Swift as well. Anything i add can feel like part of the core. And I can get the strict perf when i need it.
comment in response to post
Equator surprises me? I guess because it is not linear crossing zero?
comment in response to post
Followed. New method for pruning weights and biases.
comment in response to post
Implanted has scenes from the empty playa.
comment in response to post
Upvoted
comment in response to post
Agree completely. Like any tool, its good for specific tasks.
comment in response to post
Big fan of defined functions replacing anonymous closures when compiler output is not helpful.
comment in response to post
Depends on next goal. Leetcode is fun and since it may have the languages you already know, you can compare. Less so if perf and data are not your focus.
comment in response to post
The floor is lava.
comment in response to post
I get that. Scaling teams can have tiers of developers. The first tier for me should not stumble into concurrency. The second tier should not be using low level locks. Bad deadlocks, data races, or perf bottlenecks end up on my plate. Much more efficient to avoid some issues.
comment in response to post
I like the notion of having MainActor because the default. I’m starting to lean toward actors as being the next thing to teach. It aligns well with separation of worker classes and single purpose actor/storage/access being colocated. It feels like fewer pitfalls. Until we get to more perf criticl
comment in response to post
Omg. Best feature ever.
comment in response to post
Easy fix, transform coirdinate to entity.parent context. Rather than to nil/scene context.
comment in response to post
I tested this Friday and verified. The problem with getting the object gesture in scene/world coordinate is that the entity position will be interpreted by it parent. If the parent is not in the same scale and axis aligned with scene the position is wrong.
comment in response to post
Transform would only apply inside a parent that would read it. This is the top level parent that uses transforms to place its children. Nodes above this are not realitykit elements.
comment in response to post
Its a great series. One thing i keep seeing is an assumption that the applied offset to enity. Position are always in scene coordinates. In reality they would be in parent space coordinates, right? Why not translate them to that space rather then .scene? Then they would work for dollhouse scale.
comment in response to post
Agree completely.
comment in response to post
Nice writeup.