[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] WEBGL_subscribe_uniform extension

WEBGL_subscribe_uniform has been moved to rejected status.


On Mon, Mar 28, 2016 at 2:52 PM, Kenneth Russell <kbr@google.com> wrote:
Apologies for the long delay revisiting this topic.

At this point I agree with rejecting this extension. It was always difficult to understand how it would be used effectively by applications, since the values the GPU saw would be a frame or two ahead of the CPU-side code. Additionally, nobody's working on the code any more. The most profitable thing to do at this point is to work on reducing the latency of all WebGL implementations, rather than working around the latency of specific ones.

Any other comments?


On Mon, Mar 28, 2016 at 1:18 PM, Kirill Dmitrenko <dmikis@yandex-team.ru> wrote:
I support. More over, I think, the problem is more general and does affect not only WebGL, but the whole platform. Thus more general solution has to be introduced. Like a function to request current state of user input devices (as, if understand correctly, done in gamepad API).
28.03.2016, 20:04, "Florian Bösch" <pyalot@gmail.com>:
I suggest to move the WEBGL_subscribe_uniform extension to rejected, for the following reasons:
  1. Asynchronous Time Warp (ATW, https://developer.oculus.com/blog/asynchronous-timewarp-on-oculus-rift/) is the preferred method to ensure most up to date HMD input -> display transform. This removes the main motivation for this extension.
  2. No further input has been provided on this extension in 16 months
  3. No evaluation beyond the initial prototype has occured for 22 fmonths
  4. The extension no longer has a champion since 16 months
  5. No other champion has come forward in the last 16 months
  6. The issues around the extension formulation have not been addressed for 20 months.
Repeated calls for a new maintainer the extension have gone unanswered with the last occurring over 12 months ago.
I would also like to state on record that I think it's poor form to introduce an extension to the registry without the necessary commitment to see it trough to its conclusion. I strongly disapprove of this sort of registry littering with garbage. 
Kirill Dmitrenko
Yandex Maps Team