The codebase is dense, hard to compile, using outdated dependencies, and doesn't play nice with anything else. Documentation is sparse, often incorrect, and severely lacking in anything like a new user guide. Everything assumes you work for Pixar already and know the ins and outs of their pipeline.
3D is much, much, much more complicated than 2D, especially if you're trying to interchange between arbitrary applications that may have divergent needs.
Start with this little thought experiment.
What do you mean by 3d object?
Do you mean a set of polygons, like in a traditional triangle mesh? A volume, like voxels? A set of 3d surfaces?
Do you need to model interior details, or only the exterior envelope? Do you need to be able to split or explode it at some arbitrary level of detail? Do we need to encode sharp edges or creases in some way?
etc, etc, etc
This is before you have touched materials, texturing, lighting, any of that.
Like in HTML with divs? So if you have a virtual lamp you want to copy, all the various elements that make up the lamp are in a VR equivalent object markup as <div id=‘lamp’ />. If you want to copy specific elements you can, but you’d have specific actions, e.g copy color etc.
Maybe I’m missing something though and it’s more complex.
3D is not like tabular data. There isn’t some default resting state it naturally wants to exist in. It’s all edge cases and special logic. Also, it’s mind bogglingly vast amounts of raw data. Even a simple scene can contains hundreds of thousands of surfaces/polygons/spline patches/voxels/whatever representation.
A VR environment is essentially running a high end 3d game engine at all times.
I don't think the intention is to copy an object with the baked in lighting at the time of making a copy. I can imagine you just want to copy the object and the behavior how it reacts to whatever environment it's placed in.
In 2D apps and games, you can often get away with incredibly simplistic calculations. Rarely much other than a translation. Many times 1D with naively obvious solutions. With 3D, you rapidly need to move to 4D matrices than can handle arbitrary scale, translate, rotate, perspective, clip volumes.
Nearly every 3D app anywhere has to handle the model, to world, to camera, to clip space path, which involves a lot of complex math well beyond most 2D apps. Usually, 3 different matrix mults with 4x4 matrices.
v_world = M⋅v_model
v_camera = V⋅M⋅v_model
v_clip = P⋅V⋅M⋅v_model
v_clip = [[P00,...,P30],[...],[...],[P30,...,P33]] ⋅ [V00...V33] ⋅
[M00...M33] ⋅ [m00...m33]
It's one of the main reasons voxels have been the only real 3D implementation with large scale use. The amount of work necessary to develop, ... really anything that works with 3D is a large step upward in difficulty unless its totally regular and square. Otherwise, huge numbers of optimizations are no longer available. Plus, the compression cliff for normal users of effectively arbitrary 3D shape design and movement is really steep. Most first time users of an industry 3D CAD package (ProE, Solidworks, AutoCAD, Maya, 3DSMax, Blender, ect...) or similar have the "wall of difficulty" moment.Edited: dumb math error
The problem with the Apple approach is that there are no apps and games, and there probably won't be many given it's a 3500$ device with few users that Apple exerts its tyrannical grip over (or if there will be, they will be ports of Unity/Unreal, PC or Android VR apps, not using any of the special features that the Apple OS may have).