<story><title>Live Coding in VR with Oculus Rift, Firefox WebVR, JavaScript, Three.js [video]</title><url>https://www.youtube.com/watch?v=db-7J5OaSag</url></story><parent_chain><item><author>tinco</author><text>This is why I bought a DK2, I believe VR IDE&amp;#x27;s are going to be a thing, and they&amp;#x27;re going to be great. The fonts aren&amp;#x27;t very crisp in this video, but once we get some nice editors in there it&amp;#x27;s going to rock, the new display has a high enough resolution to make it look great, and I bet the consumer version is going to have a retina display which will just make any discomfort vanish.&lt;p&gt;Note that in the video there&amp;#x27;s just one editing window, in an IDE obviously there could be editing windows and references all around you. You would never need a mouse as your head movements convey positional information, though you can use a mouse of course, and with good keyboard controls I think you can have an editing space ten times as big as the traditional dual 27&amp;quot; monitors give you.&lt;p&gt;No more hiding buffers in tabs, no more disruptions of flow as you&amp;#x27;re scrolling through your buffers looking for the right one. You just access the visual memory in your brain to intuively remember where you left the buffers you use.&lt;p&gt;Also, the idea that this would somehow be bad for your neck sounds ludicrous to me, how is staring for hours at a stationary rectangle with miniature information more natural and easy for your neck muscles than having information spread around you in even spacing at a comfortable virtual distance? I think it&amp;#x27;s going to be a relief for nearly everyone.</text></item></parent_chain><comment><author>JackC</author><text>&amp;gt; how is staring for hours at a stationary rectangle with miniature information more natural and easy for your neck muscles than having information spread around you in even spacing at a comfortable virtual distance?&lt;p&gt;Low-pixel displays can&amp;#x27;t replace high-pixel displays (yet). It&amp;#x27;s all about the speed your head can move, vs. the speed your eyes can move, vs. the speed your display can refresh.&lt;p&gt;As a simple test, try holding your head still while moving your eyes back and forth ten times, from one extreme of your FOV to the other. Then try moving your head back and forth ten times to see things beyond your FOV on each side. Two observations when I try this: (1) the eye movement was much faster than the head movement; (2) the head movement was much more tiring.&lt;p&gt;In fact, eye movement is the fastest thing we can do, and even uses special circuits to reduce latency:&lt;p&gt;&amp;quot;Saccades are the fastest movements produced by the human body. The peak angular speed of the eye during a saccade reaches up to 900°&amp;#x2F;s in humans; in some monkeys, peak speed can reach 1000°&amp;#x2F;s. ... Under certain laboratory circumstances, the latency of, or reaction time to, saccade production can be cut nearly in half (express saccades). These saccades are generated by a neuronal mechanism that bypasses time-consuming circuits and activates the eye muscles more directly.&amp;quot;[1]&lt;p&gt;Head movement apparently maxes out at 500°&amp;#x2F;s or so, and that&amp;#x27;s not comfortable to keep up for long. So it&amp;#x27;s at least twice as fast to access high-resolution information by eye movement as to access the same information at lower res by turning your head. That&amp;#x27;s the tradeoff between using a fixed monitor at your max comfortable resolution, and using a lower-res head-mounted display.&lt;p&gt;At the same time, a fixed display (for now) allows you to move your head &lt;i&gt;more&lt;/i&gt; rather than less while reading comfortably. A head-mounted display has to update the display in response to your head movement, and a fixed display doesn&amp;#x27;t.&lt;p&gt;As a test here, see how fast you can move your head back and forth while reading text on your fixed display. Then see how fast you can move back and forth while reading on your DK2. The second will be slower, because the Oculus has to impersonate a pixel on your virtual display by juggling which physical pixels are used to render it as your head turns. In addition to further throwing away resolution by aliasing your virtual display onto your real display (the virtual text has to look sharp regardless of how it happens to overlap with physical pixels), this means the refresh rate is a limiting factor on how fast you can turn your head and still read. The text which was crisp while your head was still is physically blurred before it even gets to your eye, because the Oculus can&amp;#x27;t quite keep up with where it should be. That stops being a factor at, say, 1000hz, but we&amp;#x27;re not there yet.[2]&lt;p&gt;So on a fixed display, you can actually move and stretch your neck and turn your head without affecting the reading experience; on a virtual display, those movements will blur the text you&amp;#x27;re trying to read.&lt;p&gt;I&amp;#x27;m very excited about all of the things VR can be -- just saying that one thing it can&amp;#x27;t be, yet, is a replacement for a high-resolution monitor when you&amp;#x27;re trying to quickly access lots of text.&lt;p&gt;[1] &lt;a href=&quot;http://en.wikipedia.org/wiki/Saccade&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;Saccade&lt;/a&gt;
[2] &lt;a href=&quot;http://blogs.valvesoftware.com/abrash/down-the-vr-rabbit-hole-fixing-judder/&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;blogs.valvesoftware.com&amp;#x2F;abrash&amp;#x2F;down-the-vr-rabbit-hol...&lt;/a&gt;</text></comment>
<story><title>Live Coding in VR with Oculus Rift, Firefox WebVR, JavaScript, Three.js [video]</title><url>https://www.youtube.com/watch?v=db-7J5OaSag</url></story><parent_chain><item><author>tinco</author><text>This is why I bought a DK2, I believe VR IDE&amp;#x27;s are going to be a thing, and they&amp;#x27;re going to be great. The fonts aren&amp;#x27;t very crisp in this video, but once we get some nice editors in there it&amp;#x27;s going to rock, the new display has a high enough resolution to make it look great, and I bet the consumer version is going to have a retina display which will just make any discomfort vanish.&lt;p&gt;Note that in the video there&amp;#x27;s just one editing window, in an IDE obviously there could be editing windows and references all around you. You would never need a mouse as your head movements convey positional information, though you can use a mouse of course, and with good keyboard controls I think you can have an editing space ten times as big as the traditional dual 27&amp;quot; monitors give you.&lt;p&gt;No more hiding buffers in tabs, no more disruptions of flow as you&amp;#x27;re scrolling through your buffers looking for the right one. You just access the visual memory in your brain to intuively remember where you left the buffers you use.&lt;p&gt;Also, the idea that this would somehow be bad for your neck sounds ludicrous to me, how is staring for hours at a stationary rectangle with miniature information more natural and easy for your neck muscles than having information spread around you in even spacing at a comfortable virtual distance? I think it&amp;#x27;s going to be a relief for nearly everyone.</text></item></parent_chain><comment><author>Void_</author><text>I&amp;#x27;m happy with a single 24&amp;quot; monitor with one split screen.&lt;p&gt;There is a virtual space 10 times bigger than 27&amp;quot; monitor, but it&amp;#x27;s only in my head, and I have no need to see it in 3D space.&lt;p&gt;But that&amp;#x27;s because I work in this space every day, I know all filenames by memory, I always know exactly where I wanna go, and type cmd+t followed by filename automatically.&lt;p&gt;This VR idea is like flying through places, but you don&amp;#x27;t need that if you can teleport.&lt;p&gt;I can&amp;#x27;t imagine this being useful in day-to-day programming, but definitely would use it for discovering an unknown project.</text></comment>