This is less about religion directly and more about sharing a cool app imo.

Also, tbf, there are regular posts on the HN front page that I would consider "political". (Though I'm not bothered by them.)

The fact is that many doctors do suck. Nearly all of my family members have terrible doctor stories, one even won a huge malpractice law suit. We can’t hide the real problems because we’re afraid of anti-vaxxers.

The shift wouldn't have been so turbulent if npm had simply updated their CLI in tandem. I still can't use 2FA to publish because their CLI simply cannot handle it.

CLI publishing with TOTP 2FA worked fine until they broke it.

On the contrary, Opus 4.5 is the best agent I’ve ever used for making cohesive changes across many files in a large, existing codebase. It maintains our patterns and looks like all the other code. Sometimes it hiccups for sure.

Unfortunately sim racing requires Windows (that's my last holdout).

As far as macOS goes, Linux is so good but I also like my peripherals to work for my job where I don't have time to tinker all day.

I don’t see any reason why Google wouldn’t abandon web features left and right, given how they do that with everything else.

Because they themselves use them?

Also because they know what happened to Microsoft when they did that with IE.

Microsoft didn’t control the number one search engine, the number one email client, the number one video site, probably the number one online office suite, the number one smartphone platform…

It was possible to rip people away from Microsoft. That may not be something we can do this time with Chrome.

Try telling someone that moving off of Chrome may mean moving off of every single Google property because Chrome is the only browser they work on by then.

See how easy an argument that is. It’s right up with there with “stop helping capitalism and move to the woods“.

Then it’d be time for round two of antitrust, and I doubt the judge and regulators would feel so understanding about Google keeping Chrome if that is the landscape.

I think that would’ve good. But…

1. The US isn’t doing this. They have a case but aren’t calling for breakup

2. We all know howling anti-trust and appeals take

If Google gets handed the web (let’s say) this year by Apple being forced to allow them, it could be a decade+ before the Google side gets tackled.

And I’m afraid of how much damage they can do in that timeframe.

I think fixing Google’s ownership over Chrome before forcing other browsers on iOS would be less harmless than forcing iOS to allow other browsers than doing Google.

I’m totally good with doing both. I worried about the effects of the order they’re done in.

And I am only saying this about browser engines. This should not be taken to say Apple should be able to do some of the other nonsense they’ve been doing for 10+ years abusing their position.

I think they might be, but only as long as it stays open-source (assuming we mean it works on Chromium and not Chrome). Honestly, I fundamentally don't have a problem with an open-source browser having a monopoly, because the open-source nature means that if things get bad you can always just fork it and make something better.

I remember when they did this to pictures of the moon: https://arstechnica.com/gadgets/2023/03/samsung-says-it-adds...

Before anyone wastes a lot of time like I did trying to use the popover API: it is not ready yet. You can do very basic things in all browsers but positioning is still different and/or totally broken per browser.

Yes, HTML & CSS alone won't replace JS. Of course, for complicated form validation HTML is not sufficient. But IMHO it's very important to provide basic functionality in HTML / CSS as much as possible / reasonable. Moving the functionality to HTML / CSS can potentially improve the SEO.

As for positioning, there is an experimental feature @position-try. Here I made a small demo where it handles overflows.

https://waspdev.com/articles/2025-06-29/css-features-web-dev...

But yeah, that's kind of limited if you need nice animations or some other complicated thing. Although it's fun.

Yes, popover's uses are limited without CSS anchor positioning but it will be supported in all major browsers very soon.

In the meantime, there is a polyfill to load in browsers without support.

https://caniuse.com/css-anchor-positioning

Would love full remote play somehow so I can use it for team games with my remote team!

This is something I've been thinking of as well. There's actually a demo implementation with few games that support fully remote gaming but the problem I've been running into is some memory limitations on iOS devices causing crashes. On Android everything seems to work a-ok. I think the iOS problem can be solved, just will take some time

There are remote team video games like (mine) https://epicwin.team .

Slightly different approach, each plays in their browser/phone and there is no “main display”. And my games are cooperative. DM if interested.

I’m releasing a new game BossBattle soon so keep your eyes peeled.

This is interesting, thanks for sharing! Need to try it out

This is not a legible font. You can clearly see they did not distinguish uppercase o and 0 (zero) at all. Uppercase i and lowercase L are barely distinguishable. Classic font blunders.

That makes sense for code or technical text, but it is less relevant for car UIs. In an infotainment system you almost never see ambiguous strings where O vs 0 or I vs l matters. Everything is highly contextual, short, and glance-based. These fonts are tuned for distance, motion, glare, and quick recognition, not for reading arbitrary identifiers. If it tested poorly in real driving conditions that would be a real problem, but judging it by programmer font rules feels like the wrong yardstick.

Yikes - I thought it looked fine at first but that's a wide zero.