Thanks, I have seen that post. Personally, I focus on different kind of issues.
@richharris
has his own vision about how the specifications are designed and what things are missing according to him as a framework author.
On the other hand, as a component library developer, I mostly care about the issues and nitty-gritty details with the actual implementation (some of those, like Selection API, focus etc, I have faced myself or learned from my team's experience).
I respect the input by Rich, but personally I don't see any "action point" for the community in his blog post (except for "beware of using Web Components").
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
dev.to/richharris/why-i-don-t-use-...
also explains other issues related to webcomponents.
Thanks, I have seen that post. Personally, I focus on different kind of issues.
@richharris has his own vision about how the specifications are designed and what things are missing according to him as a framework author.
On the other hand, as a component library developer, I mostly care about the issues and nitty-gritty details with the actual implementation (some of those, like Selection API, focus etc, I have faced myself or learned from my team's experience).
I respect the input by Rich, but personally I don't see any "action point" for the community in his blog post (except for "beware of using Web Components").