3 ms·

Don’t both your points boil down to: “for my use cases, I don’t care” but then you’re applying them to the general use case that the OP is talking about. You’r

by dagmx 3y ago

Don’t both your points boil down to: “for my use cases, I don’t care” but then you’re applying them to the general use case that the OP is talking about. You’re also oddly fixated on games, which is clearly not what the product is focused on delivering. That’s just incongruent and reductive to the argument at hand. But to your last point, that’s exactly what the progressive APIs let you do. You can integrate 3D elements on top of your windowed iPad. You’re thinking in “either 3D or 2D”, whereas this is allowing developers to progressively adopt the entire gamut within the singular app which can target iOS and visionOS. The quest just can’t do that.

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 ago
  I 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.

by dagmx 3y ago

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 ago
I 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.