Matthew Amato
Matthew Amato
- Have a clear definition of when a result parameter should be required and enforce it everywhere (we may just require them everywhere). Right now result parameters are optional in...
Just to prevent anyone doing a bunch of work that we end up being unable to merge. Please keep us in the loop in terms of exactly what you would...
> Even 'step 1' as you call it is very problematic; there is a lot of 'code smell' issues in Cesium when removing AMD (like 'return' outside of a function...
Two more things; 1. Coverage will also need to be updated to work. I'm not sure if the old and busted jscoverage that Cesium is using can be made to...
> This is an example of the first issue. This pattern is used throughout the code base. This is a coarse grained check so the code can actually load in...
The issue is that we can't throw an error. The code needs to load cleanly in browsers that don't support TypedArray (like old IE). The code does not need to...
ES6 PR is open, see #8224
@lilleyse if I'm understanding this correctly while the low-level capability is now there, there is not a standard way for using it? For example, if someone hands me a 3D...
I know the link in the description alludes to this already, but given that HTTP/2 support is now standard in all browsers, is this still needed? Does it provide any...
Awesome, looking forward to the results and methodology (since HTTP/2 server configuration probably comes into play as well)