> Doing VR GUI development in the native apps is unpleasant – you can gut it out in C++ with our current interfaces, but the iteration times and code structure don’t make it a lot of fun.
> “Remote development”, where the script is actually executed in an IDE on a PC, communicating with NetHMD over a TCP connection. This allows sub-second code-change to VR change iteration cycles, and the use of a debugger. There might also be a use for a related mode where a central server directly drives one or more clients.
Why can't people see that this is the same problem even for standard GUI development rather than just VR GUI development?
This is something you get so used to with Lisp that later any environment that doesn't support it seems unnecessarily and terribly constrained. SLIME + Common Lisp is a wonderful toolset.
Yet you constantly see Clojure enthusiasts droning on about their interactive development setup, all while poorly emulating what hot swapping did 10 years ago.
> Doing VR GUI development in the native apps is unpleasant – you can gut it out in C++ with our current interfaces, but the iteration times and code structure don’t make it a lot of fun.
> “Remote development”, where the script is actually executed in an IDE on a PC, communicating with NetHMD over a TCP connection. This allows sub-second code-change to VR change iteration cycles, and the use of a debugger. There might also be a use for a related mode where a central server directly drives one or more clients.
Why can't people see that this is the same problem even for standard GUI development rather than just VR GUI development?
I would kill for these tools on my desktop ...