On Tuesday, June 23, 2015 at 4:36:12 PM UTC-7, John Carmack wrote: > The intersection of Gear VR owners and Racket users may consist of just me at > the moment, but if anyone else here is interested in discussing the work I am > doing with driving VR by Racket/Scheme, I would welcome the input. Would > that be > an appropriate topic on the list? > >
I don't mind digging into Racket, but I would like to advocate for Javascript compatibility as early as possible. The devs building multi-server-multi-client VR apps are mostly on Node.js and/or Three.js. JSON data is super nimble. Objects sent from over the air are currently popping into our scenes in a very jarring fashion, but eventually we'll have new file types that re-package each poly with its surface data so that we can all figure out what progressive rendering should look like. (I'm guessing it will look something like people and scenery getting beamed up right before our eyes.) JSON is probably going to be the go-to format to send/receive renderable 3D packets. The thought of doing it with XML makes me feel ill. I'm sure Racket can handle JSON data (it very well might already for all I know), but Javascript found its way across the whole stack (among other reasons) because we love the idea of having a universal language to eliminate the serialization between client and server, plus it knocks down communication barriers between front-end and back-end team members. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
