I was just working on an app where this exact pattern would have been useful. The app mixes serverside html with some sprinkles of React for a checkout flow. Command and commandfor would have made the linking of the two much nicer. Apps following the islands pattern will also benefit from this feature.

Sidenote: I think the web's biggest problem in the future will be how hard it is to deprecate functionality.

Maybe we need Html6 to be about removing/simplifying features from the browsers?

This falls down to the old "it depends" slogan. Tailwind is a great way to scale a your css with a larger codebase / team while semantic CSS will give you a smaller tighter stylesheet and cleaner html for that single handcoded landingpage or blog.

Also the download cost of tailwind falls as the size of the app grows and each utilityclass is used in more contexts.

AFAIK, in Norway, most fines have been directed at public institutions.

The main US advantage wrt to the last generation of tech giants (i.e. Google, Facebook and Amazon) is language. You will reach scale far faster in the US than in Europe because you do not have to translate your product to new languages and markets. Thus the US giants reached scale before similar European products could compete.

Stepping off the dependency upgrade treadmill is an interesting and valid point that I think many HN readers dream of. It seems to me that Etsy has ended up so far behind current React that going to Preact is a very valid direction to take.

The only thing I react to is the part about "It feels much like Rust vs. C++. Rather than adding layers upon layers to existing infinitely backwards-compatible software, it takes the best patterns and features and builds them from the ground up.".

Svelte bungled this in one place and that is in the html coding. For example Svelte has different syntax for if ({#if}, else ({:else}) and endif ({/if}. I end up looking this up in the documentation way too often - especially when not doing Svelte fulltime.

You still need to create the middle datastructure ( [[k1,v1], [k2, v2]] ) but it is an improvement :)

let bar = [{id: zz, }, {id: y},...]

let foo = {}

bar.forEach(v => foo[v.id] = v)

I'd love to have something like:

let foo = bar.toMap(v => [v.id, v])

I know this would seem a bit like a contradiction to the ethos of unikernels, but it would give the benefits of unikernels (i.e. smaller attack surface) to a much larger audience.

What I find lacking in this post is tips on how to best configure systemd to run docker/podman containers and/or docker-compose. Any tips on that would be great!