HTML Web Components (blog.jim-nielsen.com)

Article summary

The article discusses the concept of HTML Web Components, which prioritize enhancement over replacement, allowing for rendering before JavaScript and encouraging a design of composability. This approach is contrasted with React components, which are seen as replacing existing browser functionality. The author argues that HTML Web Components promote a mindset of augmentation, leveraging the browser's capabilities to improve resilience. This approach is seen as a key factor in the long-term success of web development.

Main themes

• HTML Web Components
• React components
• augmentation vs replacement
• Server-Side Rendering
• web development best practices
• frontend complexity
• composability and declarative coding

What commenters say

• Some argue that Web Components are cumbersome to use and do not solve real problems like state management and routing.
• Others believe that Web Components are useful for large enterprise applications with multiple divisions and frameworks.
• There is disagreement over whether React is a suitable choice for building web applications, with some arguing it is stable and backwards compatible, while others see it as part of the problem of frontend complexity.
• Some commenters suggest that Server-Side Rendering (SSR) can achieve similar results to Web Components, rendering React components on the server and sending them as plain HTML.
• Others argue that Web Components offer a unique advantage in allowing static frontend bundles to have power previously reserved for SSR or HTML-only apps.
• There is also discussion over the trade-offs between using Web Components and other approaches, such as the potential for nastier coupling and more complex tree structures.
• Some commenters see Web Components as a way to promote a more declarative and observable approach to web development, while others are skeptical of their benefits.