3 ms·

This sounds very interesting. As I've seen others voice here on occasion, the IDE use case for VR is the one that speaks most to me. Adding a collaborative el

• mlatu 6y ago
  I imagine this VR OS-Shell will be a VR space that represents your personal system behind the scenes. Eventually I want to be able to connect to other systems I own and manipulate files via 9P (for example). There'd be a workbench for manipulating code and a filing cabinet for browsing files. You'd mount a sourcefile on the workbench and manipulate its AST. There will be a way to add a 2D/3D scene to your project and open a viewport into it as you are manipulating its source code and assets. Longterm vision is to add a door to a public scene, a lobby if you will, for allowing other users in, with an airlock (to allow multiple users to enter together as a party) to enter your exhibited scenes. Later there could be another door added to the lobby to connect all the lobbies with a public and open space. So there are: personal spaces: e.g. your workbench, only authenticated users have access private spaces: your lobby and standalone systems in the public space, here you can invite friends over to explore an experience you built together. I think if monetization comes into play you will have to authenticate yourself with your public key to enter a payed-experience. and one public space: the world, (you would be anonymous here) you can set up standalone systems that run private spaces with experiences for passersby to explore. The location of said systems should be a function of their proximity to you in regards to lag. Well. Something like that ^^