Web Components Club

Skip to main content

003: Do I need Polymer though?

Yeh yeh, I know I said I wanted to look at Shadow DOM in the last post, but I’ve been reading and the “vanilla” web components API looks it could possibly be quite straightforward, so I thought I’d jot down some thoughts.

Keeping things light

I yearn to deliver the lightest possible payload to a browser and going “frameworkless” with JavaScript while using portable, reusable components feels like a dream.

There has to be a trade-off though, right? Efficient re-rendering and that almost magic feeing when a state-driven app just updates itself are very useful things that frameworks give us. Maybe writing and reusing some tiny boilerplate code and base classes is the answer to almost recreating that. Maybe there’s functionality there that I’m yet to learn. It’s exciting not knowing, for sure.

All this again seems relevant to the Shadow DOM, so I’ll stay on course now (I promise). I’m just going to consider wether Polymer as a whole is worth looking at before I get too deep. Maybe I just take parts like the awesome router that I keep going on about instead.