4 ms·
> oddly fixated on games Well, the reason I bought a number of headsets was for developing productivity applications. I just found that it was a bit of a deade
by atchoo 3y ago
> oddly fixated on games
Well, the reason I bought a number of headsets was for developing productivity applications. I just found that it was a bit of a deadend and that the only meaningful value was in existing 3d experiences (games, modelling, visualisation). I couldn't find the value in spatialising 2d productivity experiences. Hence the heuristic, if there was any value, we would already be wasd-ing our way around a 3d view in our 2d tools. There have always been a stream of 3d experiments like debuggers or knowledgement management tools but they just don't offer value compared to 2d text-oriented experiences.
Some of the talk about Spatial, feels like a pendullum swing back to Hacker's "Gibson" or Jurrasic Park's "Unix, I know this" 3d interfaces that were assumptions of what would be useful in 3D, and we have made real versions of these, but they just suck. Classic case of imagination / reality mismatch that often comes with tech.
> allowing developers to progressively adopt the entire gamut
That is just the "how", not the "why".
- klibertp 3y agoI still want to be able to tell a coworker to "go past the routers, turn to the left and go past views until you get to models; the one you're looking for will be the one on top of the pile on the right". It would be "wow" for sure, but also - spatial memory is one of the easiest to hijack and repurpose for something useful. Of course, being able to visualize the codebase like this would require a Smalltalk-level system (I'm seeing a chance here for Smalltalk & Moose/Roassal/Mondrian/GToolkit/etc.). The problem: once you get to that model, you need to read it. And until now reading lots of text in VR wasn't the best experience, not without things costing $10k+. So, the idea is shelved and waits for a good opportunity in the future... Maybe.