5 ms·
I have long been a supporter of Web Components over non-native libraries. Recently I tried to put together a native only site with them and it was a lot of fun.
by ehnto 7y ago
I have long been a supporter of Web Components over non-native libraries. Recently I tried to put together a native only site with them and it was a lot of fun. It's not without it's quirks or concerns, but for a smaller, non SPA site I would pick it over React or others just to cut out the tooling chain and node ecosystem cruft. It would save me some headspace at the very least.
- ricardobeat 7y agoDid you use anything for rendering templates?
- ehnto 7y agoI wrote a small helper class that I extend my components from https://bitbucket.org/polylab/polyblocks/src/master/polyblocks.js https://bitbucket.org/polylab/polyblocks/src/master/polybloc... I have changed the details a bit since this but the approach is the same. The readme of that repo explains how I approached working with them, I tried to keep the process simple.
- krasicki 7y agoI worked with early Polymer versions for about a year on a pilot project and loved the technology and implementation. Conceptually, I think its superior to lots of the alternatives. Fact of the matter is that the javascript/nodejs (e.g. React) hordes shouted down a really fine set of ideas. its a sad loss, IMO.
- krasicki 7y agoShocker: https://micro-frontends.org/ https://micro-frontends.org/
- ehnto 7y agoThat article seems to confuse project management issues with architecture I think. Who in their sane mind would recommend using three different frontend frameworks living in one codebase? Who inevitably wraps it all together, Team Mop Bucket? What would the build pipeline look like and who maintains and fixes that? Monoliths still work if managed correctly. You can even organise code to get similar isolation as a microservice but still in the same codebase and tooling. If you find yourself looking into "micro services but it's frontend components" then I think you need to look at hiring a technical lead who can see a bigger picture architecture for everyone to work in. One of the benefits of consistent tooling and frameworks is knowledge sharing and mastering your tools as a company. If everyone is using different tools then you have created fragile knowledge silos throughout your company and you don't get that hive mind mastery of the tools, where there is always someone who knows what the right approach is.