diiiimaaaa

I recently had to setup another complex monorepo with eslint/vitest/vite/tsup/turborepo and it was such a pain. All the time either eslint breaks for some file, or some build breaks because of some obscure thing in tsconfig, turborepo behaves in a weird way, adding new packages is a pain, etc.

Hopefully Evan can pull this off and we have simpler initial setup.

Not only that.

My main problem with web components that you end up with a build step anyway.

Not every component is interactive and relies on JS, some are just static elements (say avatar image) that you wanna render right away (but at the same time keep styles and logic scoped). Declarative shadow DOM helps, but you end up with a bunch of duplicate code in your final output, which begs the question - why am I using web components at all.

Leaflet should easily handle stuff like this if configured correctly. OP just slaps 3000 markers in a single layer, and each of them is an image element in dom. Should probably use some marker clustering for that.

Similar thing happened in iOS7(?) where they released glassy panels. Not far from that `-webkit-backdrop-filter` was added that allowed similar effect, I expect similar will happen. For new glassy effect it seems you need a separate filter for border, or maybe it's just gradient + blend mode.

I think we're in a loop guys

So if I understand correctly all JS is custom-written Alpine JS components.

And all CSS is custom classes that use Tailwind @apply, I'm not sure why, can someone elaborate.

These placeholders are generated by processing the image on a server beforehand. Generally they create some html, css or svg markup that is served inline. Having to do a separate request for such placeholder is very bad idea.

It's not clear if these placeholders do actually help, especially placeholders with very low quality. In my opinion, they only add visual noise.

I'd focus more on avoiding layout shifts when images load, and serving images in a good format (avif, webp) and size (use `srcset` or `<picture>`).

I really appreciate your position, but the letter is incredibly weak. I understand that it's aimed at government that won't read it otherwise, but:

You call it "operation", it's not operation, it's war.

You ask to prevent human casualties, but thousands are already dead.

A lot of people signing from companies such as Yandex - a search engine that promotes propaganda and hides evidence-based journalism. From VK - a social network that bans opposition communities and spreads misinformation. You can't have it both ways folks.

It also misses 3 web fonts with 4 weight variations each.

I didn't want to sleep anyway.

I've seen similar posts when Apple announced that there won't be Flash on mobile Safari. And I agree with Chrome team decision to force passive on document level listeners.

Also, note that not many people complained about "blocking video/audio autoplay on mobile browsers", because it's good for users.

BUT:

- Passive event listener detection is horrible and it baffles me that they start thinking about proper way only now.

- The announcement of this breaking change was quite silent. Chrome has so many influencers on social media, but almost no one shared/explained this change properly.

I was always using UserVoice. It's quite cheap, and even has (or at least had) discounts for open-source/non-profit projects.

... and you can't translate a page, you can't search on a page, you can't select or zoom images, you can't open link in the new tab.

Imho, making custom "DOM" via canvas just to make UI look fancy is not a solution. Web was always about delivering accessible content for everyone.

Though, library might be good for web apps or games that are not content oriented.