Yes, however, a small change of the cursor size doesn't work for me for the Neo lag (idk about the TV app). I have to set it to a size that is significantly bigger, to trigger the fix. (edit: Added that side note to the gist)
Back in the 90's I had a Matrox card that would crash the machine if the hardware cursor changed at the wrong time. I think it was related to VBI, but it's been a while.
Linux resolved this issue, but to work around it on windows, I changed my cursor to an animated dinosaur, which was built into the OS and had the side-effect of disabling the hardware cursor.
Odd, I wonder if it has to do with modern macOS resolution scaling (how there basically is no "native physical resolution" setting anymore). i.e. maybe up to a certain point it's also simply scaling the hardware-rendered cursor, if that's even possible?
By the way if you are searching for some cross-platform FUSE-like alternative for a project I encourage you to try WebDAV if something else is your bottleneck.
It saved me some headaches from bundling an installer for macFUSE or Dokan's blue screens in the past. There are server implementations and also FUSE wrappers on GitHub. It's not perfect but worth a try. And it's supported directly by many OS.
Mostly used popular tools like Hopper, LLDB, Hex Fiend. Xcode's debugger UI was surprisingly helpful too because it lists current memory allocations of obj-c instances nicely. Also learned about Frida along the way and would have used it more in retrospect.
It'll be planes, because the running cost per mile travelled is critical to making the whole thing cost effective.
Power consumption and weight of the rig isn't insubstantial, so the smallest planes and gliders can't be used, and after that cost per hour and cost per mile are the key metrics.
Mainly lived inside Chrome's dev tools for many nights. Its deobfuscator and debugger is very handy. Still scratched my head lots of times along the way.
Some interesting stuff is still missing, e.g. no idea yet how they get octant paths from geo coordinates.
The obfuscation isn't necessarily a deliberate attempt at hindering reverse engineering, but a result of their optimizing JS compiler and Protobuf-to-JSON-bridge.
That project seems to use some other kind of API. It does not handle real octree/3d data AFAIK. I've only seen quadtree and terrain elevation stuff there.
Can be done, although high LOD takes a while and the current implementation might eat up all memory. You can run it in parallel though. Shard by octants :)
https://gist.github.com/retroplasma/12e0e6e236aabd17c314cb53...