Exploring the key focus for finding markets for VR-based 3D designing. Two questions: Is I/O performance the correct “key” selling point for VR designing? Historically, in the short term, a disruptive performance gain doesn’t always work as the main selling point. Does Freebird’s target market already consider performance to be a crucial factor? Rationale: The early successful Solid State Drive markets seem to be due to form-factor, power usage, and mechanical resilience.
A Nodes-like system for all actions (geometry-wise) is probably what I’ll go with. It makes sense for the use-cases I’m planning to support. Incidentally, Blender is moving in that direction too with Geometry Nodes, and Maya already works that way. It has its advantages: Simple to reason about conceptually. Very flexible and powerful. Good for scripting. Good for non-scripting (i.e. easy to build new functionality without writing code). But it has its disadvantages too: