I use tunnels to access my entire dev environment within my Quest Pro.

How often and for how long do you code like this? What has your experience been like? I always find the idea of coding in VR intriguing but am unsure of what the actual experience would be like.

If you don't mind my asking, I am honestly curious about this. Is the QPro high enough resolution to do actual dev work inside it?

Not for me, and I am sad about it. I wish it was.

What would the benefit of that be?

The idea of this[1] working for me led me down a rabbit hole of all of the VR appliances in an effort to make it work.

For me, getting into the flow of programming is as much about the environment as it is anything else. Scenery, keyboard, mouse, desktop environment, form factor, etc. I am peculiar about all of it depending on context (collab space vs. in transit vs. coffee shop vs. at home hacking)

To have a device where I could be literally floating in space with all of the context surrounding me sounded like nirvana. Until you actually try it and the world is blurry, resolution is shitty, fonts look like garbage, etc.

I've settled for a very large ultra wide monitor - 5120x1440@240hz resolution which takes up ~3 screens worth of horizontal space without the bevel. If I could get one twice as tall pixel and physical dimension wise I'd buy it in a heartbeat.

I want so bad for it to work, but it doesn't.

1: https://medium.com/immersedteam/working-from-orbit-39bf95a6d...

How likely do you think it is that it works with the Apple Vision?

I've become disillusioned at the prospect, will try again when there's significant breakthroughs.

>If I could get one twice as tall pixel and physical dimension wise I'd buy it in a heartbeat.

I can recommend using a 8k 55" TV as a monitor. They can sometimes be found for around 1000 USD and I am quite happy with mine after several years of use.

How far away do you sit from it and how curved is it (if at all)?

About arms-length. No curve, I run it at 175% scaling which at 55" makes everything large enough that even the corners are easily readable.

I used to run a 42" 4k monitor before this at 100% scaling, which made everything a little too small in the corners and I kinda wished it was curved, but with the 55 it's no problem.

It's a very personal thing. Some people happily do it all day, others declare it a blurry mess. I'm somewhere in between. I enjoy doing stints of 1-2 hours in there just for a change of scenery and to help me focus. It's perfectly usable for me, but it's not as good as a real multimonitor setup in general.

A key element is that although the resolution is lower than a real monitor, you get to make the monitor bigger. So the limit ends up being when you start having to turn your head to see what's on the other side of the monitor, which sounds benign but is an ergonomic disaster.

Does developing like this for an extended period of time actually work?

What wouldn't work about it?

Not being exhausted from eye strain or lack of focus.

to clarify - are you saying you use the Quest browser to connect to the vscode.dev environment? Or do you use an app like Immersed with a desktop browser? Just curious if the Quest browser is powerful enough for it and works well enough.

I use NordVPN meshnet tunnels to connect to everything. Even when VPN is blocked by DPI, meshnet tends to stay on.

> For instance, right now you can have 5 tunnels registered for your account. If you'd like to create a new tunnel and already have 5 others registered, the CLI will pick a random unused tunnel and delete it. Please note this limit is subject to change.

I have a feeling that this limit used to be 10 tunnels/user, did they decrease it?

What'd be the difference with the Remote-SSH option?

You need an SSH server running and the remote machine to be accessible (through NAT, firewall) to connect there with SSH. With tunnels, it's inverted: the remote machine needs to be able to connect to the central server, which is typically much easier; then you can connect to it.

Seems like you also must have a github account to use that.

Thanks, this makes sense. I think I still prefer the SSH option, but I have to give Tunnels a try.

I love Remote Tunnel and the Remote SSH feature. Super useful for developing on Linux on Raspberry Pi or a cloud VM when experiment with different Linux distros.

Port forwarding is also very useful: https://code.visualstudio.com/docs/remote/ssh

It allows me to rent a cheap cloud machine, build and test code there instead of upgrading my laptop.