Brandon Jones

+1! The reviewer suggestions and color-coded "Which files have LGTM" are the only reason I haven't starting using this extension.

Highjacking this issue to advertise that I'm effectively shutting this tracker down. Hope you don't mind! This repo was created to track issues in the experimental builds WebVR Chromium builds,...

Thanks @stuartpb! I didn't know that was a thing. And I'm consistently amazed at how much use the community at large got out of my silly little builds, but I'm...

In general the thing I'd pay attention to the most is the overhead of jumping from JS to WASM and back again. The browsers all do what they can to...

@stefnotch: It's entirely possible that I have old data in mind, and I know that it's been an area of ongoing work. I do still think it's worth paying attention...

The addition of SIMD to WASM is interesting, but I'm still wary of performance pitfalls when communicating between JS/WASM. There was a good [blog post from the Babylon.js team](https://babylonjs.medium.com/why-wasm-is-not-the-future-of-babylon-js-5832b09c9b10) recently...

I'm in favor of it!

Worth noting that the WebVR is deprecated now and WebXR (it's replacement) no longer reports FOVs directly, so `perspectiveFromFieldOfView`'s use cases are likely quite limited now.

I definitely think that the library should support these situations. @magcius' flag proposal seems very clean, and I think would be a reasonable path forward. In terms of global flags,...

That's very interesting, thanks for the bug report! I haven't seen this behavior on any other devices so far. Do you perhaps have a non-US keyboard, or have a non-English...