There seems to be a desire to provide more use-specific elements to the platform. Pay for what you use, it a way to enable that by only letting the users of these specific elements pay for the additional loading time and memory usage. There are comments suggesting that, if implemented in native browser code, the host OS might be smart enough to mitigate this, ie. it will just load the memory regions when needed. That might not be the case if some of these elements are written as ES modules internally in the browser, or used as polyfills initially in order to get proper web developer feedback. Related to: https://github.com/whatwg/html/issues/4696 https://github.com/whatwg/html/issues/4697 https://github.com/w3ctag/design-reviews/issues/384 https://github.com/w3ctag/design-reviews/issues/385 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/421
Received on Thursday, 12 September 2019 07:20:34 UTC