As a self-initiated learner, being able to view source brought to mind the experience of a slow walk through someone elses map.

This ability to observe software makes HTML special to work with.

This is a good description of the appeal of HTML web components:

WC lifecycles are crazy simple: you register the component with customElements.define and its off to the races. Just write a class and the browser will take care of elements appearing and disappearing for you, regardless of whether they came from a full reload, a fetch request, orgod forbida document.write. The syntax looks great in markup, too: no more having to decorate with js-something classes or data attributes, you just wrap your shit in a custom element called something-controller and everyone can see what youre up to. Since Im firmly in camp progressively enhance or go home this fits me like a glove, and I also have great hopes for Web Components improving the poor state of pulling in epic dependencies like date pickers or text editors.

The power of interoperability:

Web components wont take web development by storm, or show us the One True Way to build websites. They dont need to dethrone JavaScript frameworks. We probably wont even all learn how to write them!

What web components will do  at least, I hope  is let us collectively build a rich ecosystem of dynamic components that work with any web stack. No more silos. Thats the web component success story.

Lots of new features landing in Safari, and it’s worth paying attention to the new icon requirements now that websites can be added to the dock:

To provide the best user experience on macOS, supply at least one opaque, full-bleed maskable square icon in the web app manifest, either as SVG (any size) or high resolution bitmap (1024�1024).

Here’s the video of the talk I gave in Nuremberg recently.