whoyee
Re:Introducing the WebVR 1.0 API Proposal
on Thursday March 03, 2016 @07:41PM (#11221175)
It's approachable and easy to use. That was the intent. But that doesn't mean its not powerful. It's built on top of a entity-component model (similar in many ways to that of game engines like Unity) that makes it highly extensible and customizable.
The arguments are well articulated in this post: http://ngokevin.com/blog/aframe-vs-3dml/
Re:Introducing the WebVR 1.0 API Proposal
on Wednesday March 02, 2016 @08:57PM (#11214553)
That's just it. Being able to render web content in VR makes it possible for your typical web developer to use their existing skills to build content for VR. Unity and Unreal are fantastic tools and very well suited for building games, but not everything is a game.
Besides this, instant access by url with no downloads and installs, no-app store "gatekeepers" and a free and open technology stack are solid reasons for why you would want to have or use WebVR.
And while performance definetly lags behind native, I'm not sure that it's going to be that far off. WebGL 2, Web assembly, WebGL in workers, will in combination with general improvements in graphics and rendering performance will get it close.
Re:Introducing the WebVR 1.0 API Proposal
on Wednesday March 02, 2016 @08:19PM (#11214397)
It was ahead of it's time. Mozilla's A-Frame is kind of it's spiritual successor. VR experiences starting with just a few lines of markup. Check it out https://aframe.io