2 ms·
> All custom frameworks end up getting crufty and unmanageable same person: > I suggested adding lit-html > I would suggest redux, or even something hand-roll
by dmitriid 9y ago
> All custom frameworks end up getting crufty and unmanageable
same person:
> I suggested adding lit-html
> I would suggest redux, or even something hand-rolled
> See: https://www.webcomponents.org/ https://www.webcomponents.org/ for countless form components.
How quickly will that become crufty and unmanageable? Oh, pretty quickly.
Also, the following statement is if not false, then misleading
> I'd say that the first, second, and fourth are EXACTLY what web components provide.
- Web Components don't even do one thing well.
- There are still issues with "serving as input": you need to manually construct and add them to your templates if you need complex properties (i.e. anything that's not a string), there are issues interacting with the rest of the spec (form data, labels not supporting custom elements, input elements not being extensible, ARIA still not aligned with custom elements)
- WCs don't provide any tools and definitely do not lighten a programming task. Because at this point they provide nothing but low-level overly verbose primitives to construct custom elements. Everything else has to be brought in in the form of helpers, third-party libs or, yes, frameworks (e.g., if you call React a framework, then Polymer is also a framework).
So, original comment said this:
> I've recently tried to get into React seriously and I found myself getting stuck pretty quickly. I tried Vue.js which seem to be popular as well and I had a blast. I found the templates more intuitive, the documentation easier to read and the concepts just fun to use.
Your suggestion to go for Web Components because custom frameworks are crufty and unmanageable is disingenuous at best. You will end up with both custom frameworks on top of WebComponents and potential multiple issues that exist. Unless, of course, you go for "hundreds of components on webcomponents.org", vast majority of whom use Polymer to plug all the holes in the spec.
- colordrops 9y agoRedux and lit are not frameworks, but modular components that can be swapped out if you keep your interfaces clean. And neither are web components a framework. But go on with your rant.
- dmitriid 9y agoIf you cared long enough to read and understand what I wrote, there would be a point to continue this conversation. What you do though is twist my words every which way and fight with that twisted version. Just to point out a few things: - I never said Web Components written in X would be incompatible with Y - I never said Web Components were a framework - I never said Redux was a framework The rest I really couldn’t be bothered to lay out and dispel, as I have better things to do with my life.
- colordrops 9y agoBy the way, web components are a W3C standard, and a standard component built with any framework, including Polymer, will work with any other web component, regardless of what was used to build it. The whole point is encapsulation and standardization. Saying that web components will get crufty is like saying that arrays and divs will get crufty. Web component standards are minimalist and vetted by years of process, and are now included by all major browsers. I've personally worked on a large project built using over 100 in-house web components, and can tell you we've never into any issues with input. You are just picking on some minor nit you read online that has ho relevance to almost anyone. Are you aware that a large percentage of Google's public and internal web properties are now using web components? Seems a bit absurd if input was broken.