Despite JavaScript frameworks being used more widely than ever, there is still a need for native solutions. Yet Web Components currently fall short of addressing developer pain points effectively, with Web Components APIs and especially Shadow DOM dominating the top 10 of worst experiences across all HTML-related technologies.
This indicates that there is still significant work to be done before they can truly enhance HTML's extensibility and become a strong alternative to framework components. However, the ongoing activity in this area leaves me hopeful.
Link to sectionWeb Components Experience & Sentiment
Group by:
Sort by:
Experience
- Used it: Respondents who have used an item.
- Heard of it: Respondents who have heard about an item, but haven't used it.
- Never heard of it: Respondents who have never heard about an item.
Sentiment
- Positive: Respondents who are interested in learning more about a technology; or are willing to use it again.
- Neutral: Responents who did not indicate any sentiment about a technology.
- Negative: Respondents who are not interested in learning more about a technology; or have used it and had a negative experience.
Link to sectionOther Web Component Features
Link to sectionWeb Components Libraries
Link to sectionUsing Web Components Pain Points
Using Web Components that you or others have made. Missing features, browser incompatibilities, etc.
Link to sectionMaking Web Components Pain Points
What prevents you from creating the amazing components you envision? Missing features, browser incompatibilities, etc.
Link to sectionRecommended Resources
