Thanks for sharing a simple setup that avoids SwiftPM. It is nice to have more options.
Swift has to shed the perception that it only works on apple platforms. I've found the the C++ interop to be pretty good for my computer vision use cases.
It’s nice to see this addition. I’m not sure if Godot would be better off bridging OpenXR to apple’s ar compositer or do as these PRs implement.
It isn’t much work to bridge from a metal renderer to the ar compositor. There are nice, if under documented c apis for Compositor Services in visionOS. I don’t think this will end up being a heavy maintenance burden, but they should donate some headsets as the second vertex amplification doesn’t run in the simulator. The max threads per thread group also differ. So real hardware is needed to measure performance.
I built an interactive call graph interface targeting visionOS that I'll be open sourcing soon. My approach is to use the Language Server Protocol(LSP) as the itermediate format as many LSP implementations support the call hierarchy method. You can then proxy the commands to the headset for rendering. Using the LSP is nice because you can integrate the controls into small editor plugins and get live code analysis.
Most code analysis programs fail in some combination of editor integration, language support, iteration speed, or interactivity.
One of the big issues with visionOS right now is the divide between a full immersive space and a volume. There is a dev option to enable the virtual display to work in an immersive space, but normally a full metal rendered scene will hide your mac monitor. The volume requires RealityKit and provides no hand tracking data. My approach is to run the graph fruchterman-reingold spring embedder in a metal compute kernel updating a LowLevelMesh in a volume. The biggest limit I've faced is around 1000 input targets (graph nodes) is the most the RealitKyt renderer can support before the frame rate dips under 90Hz.
Good luck if you attempt visionOS, it is nearly undocumented.
Looks promising. It would be nice if the XR components exposed more configuration options. For example I don't see a way to use the transient pointer of the apple headset nor the depth buffer of the Quest 3.
Maybe all these years of staring into the uncaring blackness of my terminal has damaged my brain, but there are some real gems in "Tales from the TinkerPop."
"Grasily had been stationed at vertex v[32] for as long as he could remember. ... Grasily's commanding officer was org.apache.tinkerpop.gremlin.process.traversal.Traverser@76a36b71"
"The famous mystic traverser Gri Gurobindo (ग्री गुरोबिंदो) once said:
My single step in the graph is composed of the steps of numerous other traversers."
Our computers are at least 10,000 times faster than decades ago. Yet, are we having 10,000 times the fun?
Amazon Neptune supported both Gremlin and Cypher. AWS states in a blog post[0] that Cypher is the pathway to GQL. That aligns with the blog post. Personally I was hoping Gremlin would go farther, but it appears GQL is on track to be the unifying language for property graphs in a few years.
Guess it is time to learn Cypher as increasingly graph db vendors are adopting GQL. Is there an existing GraphDB that implements the GQL spec?
More open source projects should have fun text and drawings in them like the Tinkerpop[1].
There has been a chicken and egg problem for gpu intensive media on the web. WebGL overhead limits complexity -> demanding applications remain native -> tooling for WebGL/WebGPU is limited or lags behind.
I bet these are some of the most complex WebGPU programs.
Congrats on the launch! Good luck on the optimization.
It's neat, but I have a feeling this will result in very large downloads and long load times. Like the Unity WebGL exports of the past.
The car example https://car.tiwsamples.com/ took 120 seconds to load, making 1820 network requests, and transferred 392MB of data / 487MB decompressed.
You can deliver a significantly better user experience by building for the web directly.
It was probably from my workloads being relatively small that I could get away with 90Hz read on the cpu side. I'll need to dig deeper into it. The metrics I was seeing were showing 200-300 microseconds of GPU time for physics calculations and within the same frame the cpu reading from that buffer. Maybe I'm wrong, need to test more.
Thanks for investigating the threads federation. With reddit and twitter charging large fees for api access it has felt like one chapter of the web was closing. Now with the federation of threads there are even more people to interact with via a medium we have control over.
I'm glad to see someone find value in the open api nature of mastodon(and others). Thank you mastodon and ActivityPub for exposing the internet tubes.
The article has a nice history review of inheritance, but it would have been useful for there to be some concrete examples.
The worst example of inheritance I've ever found is in java Minecraft's mobs[0]. It is very deep in some places and has numerous examples of sub classes not fully implementing their parent interfaces.
Blaze has a bit for 'Is on fire', but how is this any different from Mob 'Is aggressive'?
Blaze > Monster > Pathfinder Mob > Mob > Living Entity > Entity
Swift has to shed the perception that it only works on apple platforms. I've found the the C++ interop to be pretty good for my computer vision use cases.