2 ms·
WebAssembly won't do anything for the latency delays of a myriad of support files (javascript, CSS, images) which is the key problem for small apps and non-appl
by dspillett 11y ago
WebAssembly won't do anything for the latency delays of a myriad of support files (javascript, CSS, images) which is the key problem for small apps and non-applicatino pages, HTTP2's better handling of multiple files (or for HTTP(S) grouping everything into one minified block) won't help if they are coming from different 3rd parties, ...
That is an issue that needs to be addressed by people changing how they currently build some pages/apps. It is particularly bothersome when mobile and stuck on a slow high-latency connection.
- jmzwar 11y agoWeb Assembly could help given devs won't need to rely on external frameworks (which do slow things down considerably). Your spot on about HTTP2 though, it just streams the files. There should be metadata in the HTTP request object that signifies the device properties and an appropriate response is given for that device's specifications.