Introducing the React VR Pre-Release

Compare and contrast: <a href="https:&#x2F;&#x2F;aframe.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;aframe.io&#x2F;</a><p>A-frame has got a certain amount of traction, it&#x27;s component based and declarative. It feels like an extensible &quot;VR HTML&quot; (or &quot;VR Web components&quot;). React is similarly component based - but one step removed from the markup.

I don&#x27;t understand the intent here. What am I building that&#x27;s a browser VR experience? That&#x27;s as foreign to me as saying a browser cooking experience. Those are words, but I just don&#x27;t understand how they&#x27;d operate together in a way that would be enjoyable and easy to use.

The future of the VR web: everyone who uses it gives patent indemnity across their whole portfolio to Facebook. Facebook only gives reciprocation across the narrow patents covered by React&#x2F;ReactVR, not their full portfolio.<p>If you build a part of your business on this, they can pull the license if you sue them for infringement in some completely unrelated area and leave you screwed.

I really want WebVR to work but when I tested with a Chromium WebVR-capable build I ran into a bunch of aframe samples that claimed my browser was not VR capable, some that were really choppy in performance, and a handful thay worked correctly.<p>After that I started thinking I should just build in Unity because there was a much greater liklihood of people actually using it with a client they download that actually works rather than hoping they would have a working browser for WebVR.<p>I also would like to have browser windows available inside of VR for interfacing with remote desktops or any existing 2d interface. Which you can do that with Unity using a browser component from the Asset Store.<p>But I would prefer using JavaScript&#x2F;A-Frame if it would actually work for most people.<p>It seems that Altspace maybe is some custom build of Chromium build because they support aframe.

Who wrote this release copy? Full of English errors...

ctrl-F: &quot;vrml&quot;<p>welp, now I feel old.

So, where is all the real work being done?<p>Oh, that&#x27;s right, by THREE.js inside the normal WebGL API.<p>This is just a fancy way to execute a banal-ly simple 3D scene that takes a single parameter - what text to show. It doesn&#x27;t do much and I don&#x27;t see any useful abstractions for the usual 3D primitives and doesn&#x27;t meet the requirements of 3D programming in general.

How do I say that this is total bullshit without being spotted as redditor?