JimDabell

> is that really true for reactivity and state management?

No. Use a framework if you want those things. Everything around reactivity, state management, and components have been badly fumbled by the web platform and the various front-end frameworks are far more ergonomic.

> Germany's ideology was bad, we know this because it abjectly failed and lead Germany to destruction.

Nazi Germany’s ideology was bad for a reason completely different from how successful they were.

> Stop being obtuse and judge it empirically. The results are what matters.

This sounds like you think Nazi Germany would have a good ideology if only they had been successful.

When your primary criticism of the Nazis is that they weren’t successful enough, it’s quite clear you are a Nazi in every way that matters.

You seem to be approaching this from the perspective of “I want to play this game” when there is more value to the original source code than simply being able to run something similar.

I’m not an outsider; I’m an immigrant living in Singapore. And it’s very racially diverse.

You didn’t make a point. You asked a question. If there was a point, it was not apparent.

I don’t see anything in my original comment that was unclear.

Publication of the source code should be required for software to be copyrightable and copyright should expire much sooner. It makes no sense for a binary to fall into the public domain 70 years later.

I think you might’ve misunderstood my point or replied to the wrong person.

When you go around saying that we should whip degenerates to be a civilised society, you don’t need to explain why you don’t mind being called a Nazi. Everybody knows why.

> Also, imo Singapore is just further evidence of my statements being true.

Not anything to do with race it isn’t. It’s a direct contradiction to your claims.

You sound like a Nazi when you call people degenerates. Was that your intended meaning?

Singapore is a melting pot of many different ethnicities, it’s not xenophobic, and more than 40% of people living in Singapore are immigrants. And it has extremely low crime.

This lauding of ethnic homogeneity and xenophobia just seems to be a dog whistle from the American right because they want to say “See? If we kicked out all the non-whites it would fix our problems!” it’s not true; It’s just a very, very, very old racist playbook.

Do you apply this logic to all efficiency gains or just ones that weren’t commonplace when you entered the industry?

For instance, package managers didn’t always exist. Would you prefer it if we got rid of them? Instead of 30 seconds running `uv add whatever` collaborating with your package manager, you could spend 30 days collaborating with other human beings to build the functionality yourself.

There are some people who see the web as a platform, and some people who see a web browser as a window for zero-install applications to draw into. There have always been people in the latter group who try to abstract everything away, but it does tend to discard pretty much everything that makes the web great.

WebP is 15 years old, and Google cares about it less than anybody else. Pretty much everybody else supports WebP but Google can’t even be bothered adding support for it to Google Docs.

The video is nonsense. There’s an article that takes it down in detail here:

https://blog.andymasley.com/p/contra-benn-jordan-data-center...

Please refer to my first sentence and my final sentence.

You are not going to get downvoted for not complaining about downvotes.

Please familiarise yourself with the guidelines for participating here:

https://news.ycombinator.com/newsguidelines.html

I saw the final paragraph when your comment was minutes old and wasn’t downvoted. I downvoted it for the final paragraph.

> Your premise that the browser implementation is faster and better is rarely true.

I know that they’ve optimised this as much as they can, but it still seems to catch pretty much everybody by surprise that every single instance of a web component with a shadow DOM needs the site’s CSS reset added to it individually (or just skip it and keep forgetting that things like box-sizing will be inconsistent with your non-shadow-DOM styles). There’s no way to say “here’s my default styles” that will work consistently across the whole page once you start using web components. And then you have the !important fights between the web component and its contents as well.

Even though it’s been standard practice amongst web developers for 15+ years, the people working on the web platform seem to mostly act like CSS resets aren’t a thing.

> there are only three platforms: Blink/V8; WebKit/JavaScriptCore; and Geko/SpiderMonkey.

You’re misunderstanding the terminology here. The platform being talked about is the World-Wide Web and you are listing three implementations of the client part of the platform.

Safari 16 is not a reasonable target for the vast majority of developers.

Apple tends to support older iPhones in newer versions of iOS, and iPhone users upgrade their software a lot. The most common target is the last two major versions because people using older versions are so rare. Every iPhone released in the last nine years can upgrade to iOS 16 to get Safari 16.

You can download a CSV here to explore the data: https://gs.statcounter.com/browser-version-market-share#week...

Baseline’s support window for “Widely available” is 30 months and Safari 16 is almost twice that age: https://web-platform-dx.github.io/baseline/

If it makes sense for you to spend time supporting 0.25% of users rather than spending that time on the other 99.75% of users, then support Safari 16. Everybody else should avoid incurring that opportunity cost.

That lets you bring up the picker, let the user pick any date, and then show an error message if they picked an unavailable one. It doesn’t let you show dates as unavailable in the picker or prevent the user from picking them.

Why are your component styles global not encapsulated within the component?

Yep.

“We need a date picker to schedule a visit.”

“Okay, use `<input type=date>`”

“It needs to be a date in the future.”

“No problem, add a `min="2026-10-05"` attribute.”

“And we’re only available on weekdays.”

“Okay, throw the native date picker away completely and build one yourself from scratch.”

Did nobody involved ever bother to ask what the requirements were for a date picker? Excluding dates is one of the most common requirements there is!

> I just genuinely think WebComponents are a badly designed API that is weird and hard to use

This was exactly what sprang to mind as soon as I saw the title. I’ve been writing front-end code for over 25 years now, and exactly two things in that entire time have made me miserable enough to think about stopping: Internet Explorer 6 and web components. Every time I try to just “use the platform” it makes me miserable and I end up demotivated and stop working on whatever side project I chose to try again with. And I otherwise like the web platform! I’ve been building with it since there was nothing but the web platform. But web components kill my enthusiasm for it stone dead.

Even now in the age of agentic development, AI trips over all the same footguns in web components that humans do. It just seems like everybody involved has been adding to the standards with “yes, and…” without ever thinking about how it will be used by web developers in practice.

> Open Weights version of FLUX 3 Image is launching in the coming weeks.

— https://x.com/bfl_ai/status/2105734605621825738

OpenCode seems to have been given the run-around as well:

> on the figma mcp, we've had an email thread going on for 8 months trying to get it setup in opencode

> they seem very concerned with the labs competing with them

> finally got unblocked after i sent this email and it'll be rolled out in a week or so

The email:

> looking through the legal stuff the amount of things in there seems pretty crazy

> this is just an mcp server, there are thousands of them. we're not going to treat figma like its special

> we've been talking about this for this entire year, i don't think this makes much sense and i don't want my team burning more time on this

> once again, for a simple mcp server

— https://www.threads.com/@thdxr/post/Dd7LN-ylLQW

> how can you argue about about IP and copyright if the breakthrough of LLMs is potentially based on circumventing or breaking IP and copyright in the first place?

Easy answer: it’s not. Learning isn’t copyright infringement. Never has been and hopefully never will be.

> Spin up a bunch of loops or fire a semi-autonomous factory at a project and it's pretty easy to blow through a 20x account in a few hours if you can afford the sandboxes, CI and other infra required.

This is a tiny minority of people, not “most people”.