Something that gets lost in the desktop focus of most web developers is that web components are supported *everywhere* on mobile. Perhaps the only browsers you will need to bring in polyfills for in 2018 are low-usage desktop browsers. Vs. global browsing time and share, Web Components support is *huge*.
Solid is not W3C endorsed.
The W3C endorses internet standards through its “recommendation track” process (or “Rec Track” in the parlance). You can see the full list of W3C Recommendations here:
Sort of! The background sync API has retry built in. If your operation doesn’t succeed, it will be restarted later. You can know if you’re on your last retry by looking at the value of
They’re less useful at the app level, but “data flow” for terminal nodes is “properties and attributes” which DOM has. If you’re building a library of UI controls, this works *great*.
HTML Imports do de-duping. That why you’ll see projects with Polymer components all <link rel=”import” href=”/path/to/polymer.html”> at the top without concern.
It’s totally true; you can’t just coin a term over dinner. You need to follow the well-established protocol that has been handed down from the founders. PWAs, obviously, can’t be a “real thing” because I failed to reserve the special “term coining” room deep under the Federal Reserve building in SF.