This article has seemed to cause a defensive reaction in the comments and in me as well (painful to admit).
For me, that defensive reaction was caused by my belief that I needed to use web components. I thought and assumed that there was no easy way to integrate with other frameworks if I didn't.
My suggestion for an alternative title for this piece would be, "Why you don't need to use web components and perhaps shouldn't."
In essence, what I've taken away from the experience of reading the article and comments is that web components aren't a go-to thing. They are a have-to thing. But if I'm using svelte (which I love btw), then I should seriously question my assumptions before setting customElement: true compiler flag.
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.
This article has seemed to cause a defensive reaction in the comments and in me as well (painful to admit).
For me, that defensive reaction was caused by my belief that I needed to use web components. I thought and assumed that there was no easy way to integrate with other frameworks if I didn't.
My suggestion for an alternative title for this piece would be, "Why you don't need to use web components and perhaps shouldn't."
In essence, what I've taken away from the experience of reading the article and comments is that web components aren't a go-to thing. They are a have-to thing. But if I'm using svelte (which I love btw), then I should seriously question my assumptions before setting customElement: true compiler flag.