The problem I see with every example of web-components is all the boilerplate required. So you land up having to learn that instead (or use a library to simplify the process). Compared to learning some simple conventions in a well implemented framework means I'm not yet convinced of the benefits...
Yes, web-components can have boilerplate code. But it's straightforward code. Frameworks and libraries have much more boilerplate code to actually work. The main differences is who writes that code, framework/library creator or programmer :)
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.
Or you can use Svelte :P
The problem I see with every example of web-components is all the boilerplate required. So you land up having to learn that instead (or use a library to simplify the process). Compared to learning some simple conventions in a well implemented framework means I'm not yet convinced of the benefits...
Thanks.
Svelte already caught my eye, it looks promising.
Yes, web-components can have boilerplate code. But it's straightforward code. Frameworks and libraries have much more boilerplate code to actually work. The main differences is who writes that code, framework/library creator or programmer :)