Web Components could replace frontend frameworks?

Post by IggleSniggle » Fri, Apr 12, 2019, 3:01 AM UTC

zarzz wrote: post #46

jaunkst wrote: post #42

Ploymer was a crapshow and HTML import a nightmare for load times. Unless some sort of topology bundling is provided for web components I'm out. We tried to do generic components for multiple frameworks based in webcomponets and it was an utter failure in practice especially for low band networks.

Allow me to float ZephJS at you as an example of a Web Component framework with a bundling tool to do what you describe. Simplifies everything about building Web Components. Introduction: https://gist.github.com/arei/8083a6270e704b830c68a2020f3e5e3... Bundling specifically: https://github.com/awesomeeng/zephjs/blob/master/docs/Compon...

Post by jbwyme » Fri, Apr 12, 2019, 3:15 AM UTC

ssorallen wrote: post #11

Web Components don’t offer a declarative way of updating the DOM; it’s still `innerHTML` and using DOM APIs to edit the state of the live DOM. Backbone was a hassle to manage in any sizeable app because updating the view was left up to every dev to figure out themselves. React brought a declarative wrapper around the statefulness of the DOM, and that is the killer feature that Web Components does not offer at all. Vu…

Post by ww520 » Fri, Apr 12, 2019, 3:15 AM UTC

gedy wrote: post #48

lstamour wrote: post #25

Earlier quoted context omitted.

Slots require shadow DOM which means there can be performance and CSS issues on widgets designed for local use with shared CSS. But I agree they’re also an option. :)

This. I feel like an old man yelling at a cloud, but while everyone seems to focus on how awesome shadow DOM and isolated CSS is, I need to deal with using a global theme and styles.

Post by Andrex » Fri, Apr 12, 2019, 3:22 AM UTC

jchw wrote: post #9

>Web Components will replace your frontend framework Yeah, I very much doubt that. Web Components is basically a suite of browser technologies. It's actually particularly heavy and I kind of hope it doesn't catch on personally, since it pushes so much to already giant monolithic web browsers. Frameworks and libraries like React and Angular are tools for developing applications first and foremost. The actual technolog…

Post by bicknergseng » Fri, Apr 12, 2019, 3:23 AM UTC

austincheney wrote: post #38

johncolanduoni wrote: post #34

Earlier quoted context omitted.

I would argue that for what the OP was discussing `textContent` (From the linked example) is very much like `innerHTML` (As it’s a safer version of the former). I’m not sure what you mean by the DOM being neither stateful or stateless, or describing an implementation of logic. Could you clarify?

The DOM is a model of a markup language instance plus access methods. State describes memory of properties resulting from a change. For example HTTP is stateless. The DOM can be both stateful and stateless, neither, or one of. The statefulness depends on your application logic rather than any intrinsic quality of the DOM itself.