[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Re: WEBGL_get_buffer_sub_data_async
Below is my rationale for arguing strictly against cutting mapBufferRange out from the standard nearly 2 years ago.
On Fri, Mar 6, 2015 at 11:13 PM, Florian Bösch <email@example.com>
I made some predictions there which have come true:
- Difficulties with transpilers [CHECK]
- Problems with different semantics [CHECK]
- Issues of the bifurcation of the standard into two distinct flavors (ES 3.0 "The web version" and ES 3.0 the native version) [CHECK]
- Issues with recasting core functionality as an extension [CHECK]
I'd wish I wasn't the one who has to tell you "told you so".