When comparing Web Components vs Blazor, the Slant community recommends Blazor for most people. In the question“What are the best solutions to "The JavaScript Problem"?” Blazor is ranked 16th while Web Components is ranked 29th. The most important reason people chose Blazor is:
Allows to use .NET Standard libraries.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Great for small—likely published—reusable libraries
Very extendable as a single-import base layer for visual controls and probably also something like a react-redux Provider.
Pro Works with any framework
Less recreation of the wheel and fewer wrappers.
Pro Fallback styling when not yet defined
Before a component's script defines the custom element—either as the page is loading or with JavaScript disabled—it can be temporarily styled via :not(:defined)
. This may prevent the need for SSR.
Pro Customizable templates via custom-recognized "slots"
slot="name"
and <slot name="name">
for customizing a component's HTML in specific areas of its shadow DOM. Also fallbacks when not defined.
Pro Stylable via custom-exposed "parts"
::part(name)
pseudo-element for styling elements within a component's shadow DOM.
Pro Use existing .NET libraries
Allows to use .NET Standard libraries.
Pro JavaScript interop
Call JavaScript APIs and libraries.
Pro Free and open source
Cons
Con Not well-suited for application wiring
Having to serialize/deserialize data between components is not convenient. You'll probably still need a [light/simple] framework. Some things are still quite nice, such as using the light DOM -- think <option>
with <select>
and <datalist>
.
Con SSR is potentially more difficult
…if you need more than CSS' :not(:defined)
, that is.
Check out this video to see how the creator of SkateJS handled it: https://www.youtube.com/watch?v=yT-EsESAmgA