4 ms·
As another example, YouTube uses a feature called HTML imports to load scripts. HTML imports haven't been widely adopted, either by developers or browsers alike
by cageface 8y ago
As another example, YouTube uses a feature called HTML imports to load scripts. HTML imports haven't been widely adopted, either by developers or browsers alike, and ECMAScript modules are expected to serve the same role. But they're available in Chrome and used by YouTube.
At least in this particular case my understanding was that Google was pushing for the adoption of HTML imports as a web standard, which would have been better for all browsers, but other browser vendors balked and Google was forced to use JS module imports instead. AFAIK I know they are now discouraging any further use of HTML imports. This is a bummer because it's not possible to leverage web components without JS now.
I'm concerned about a web monoculture too but so far Google has mostly done a good job IMO. Even Mozilla has done some pretty dumb things when it comes to web standards (unilaterally killing WebSQL, for example). I certainly can't think of any other big tech company I'd prefer to see calling the shots on the web.
- JeremyBanks 8y agoWebSQL's SQL spec was literally: > User agents must implement the SQL dialect supported by Sqlite 3.6.19. That's only a "standard" in the way that "Chromium-compatible" is becoming a standard.
- cageface 8y agoYeah this was the argument at the time. I still think it would have been better to formalize that spec instead of just pull indexdb out of some unmentionable orifice.