What We Need Instead of "Web Components" (blog.carlana.net) | HN Screenshots

YHacker Newsscreenshots

Screenshot of blog.carlana.net: What We Need Instead of "Web Components"

First screen, captured 2 years ago.

Looks similar

Screenshot of blog.carlmjohnson.net: Ten years of “Go: The good, the bad, and the meh”

Ten years of “Go: The good, the bad, and the meh”(blog.carlmjohnson.net)

158 points by jo_beef 3 years ago | 153 comments

Screenshot of blog.carlmjohnson.net: Why does all() return True if the iterable is empty?

Why does all() return True if the iterable is empty?(blog.carlmjohnson.net)

100 points by vikrum 3 years ago | 156 comments

Screenshot of jamiemagee.co.uk: Honey, I shrunk the NPM package

Honey, I shrunk the NPM package (jamiemagee.co.uk)

141 points by vinnyglennon 3 years ago | 62 comments

Screenshot of blog.jim-nielsen.com: HTML Web Components

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

417 points by goranmoomin 2 years ago | 222 comments

Jim Nielsen blog post arguing web components work differently from React components and are best used to progressively enhance existing HTML.

web-components html react custom-elements

Screenshot of typesanitizer.com: Optimizers need a rethink

Optimizers need a rethink (typesanitizer.com)

132 points by ingve 2 years ago | 139 comments

Screenshot of garnaudov.com: How I think about Kubernetes

How I think about Kubernetes (garnaudov.com)

66 points by todsacerdoti 10 months ago | 38 comments