[troupo]

It's a nonsensical term for components with predefined markup and no Shadow DOM

[jamiedumont]

So essentially what partials in a template or server-side include solve.

That's the only "build-like" part of my current website, but I'd much rather manage this beforehand and serve static HTML, or run a server-side process than use JS/HTML web components at runtime.

[gryzzly]

JS/HTML web components are the static HTML –

``` <marker-of-dynamic-behavior> {your standard static html} </marker-of-dynamic-behavior> ```

This is just a better way of doing DOM scripting, enhancing without waiting for Document Ready event, and having more freedom when to load the dynamic bits.

[troupo]

> This is just a better way of doing DOM scripting

Better than what?

> enhancing without waiting for Document Ready event

Instead you wait for `connectedCallback`

> and having more freedom when to load the dynamic bits.

You literally have no freedom over that. Web components are rendered the moment they are added to the page, and you have no control over that. So if something dynamic is happening in your `connectedCallback`, boom, our dynamic bits are loaded whether you want them or not.

[gryzzly]

better than centralized `$('.special-element').applyDynamicBehaviour()`

you control when the script is loaded right?

connectedCallback happens per component, not in a centralised manner – so you write the logic for what happens in a place where it happens