[usrbinbash]

Nothing is stopping me from writing a google-ASR powered program hooked into my terminal, and start yelling my code into the computer either.

But as long as this isn't faster, easier or more reliable than typing it on a keyboard, I won't.

People don't work a certain way because it's possible. People work a certain way because it saves time, money, sanity, or simply because it's convenient.

If wearing a VR headset while coding isn't providing substantial benefits over what my current system provides, why would I do it?

[charcircuit]

The difference is you can already use a keyboard in VR where your system sounds like you would have to go and mild it.

>If wearing a VR headset while coding isn't providing substantial benefits over what my current system provides, why would I do it?

You wouldn't.

[usrbinbash]

How can I use my keyboard in VR?

There are only 2 options:

Either I see the keyboard through some sort of passthrough, in which case the entire VR experience is basically just an overly expensive desktop background.

Or the keyboard is replaced by a VR representation, which relies on the device knowing where the keyboard is. Obviously, that will require a special keyboard with IR markers, so good bye custom keyboard, good bye laptop keyboard.

Oh, and I cannot see my hand movements on it, which kinda defeats the purpose of seeing the keyboard, because current hand tracking technology cannot keep up.

Neither of these offer me any benefit over the cheaper, easier and functional technology that I am using right now.