Yes. Golang actually encourages developers to use their own resolver in applications instead of the system one. Google itself uses its "Public DNS" cache addreses in software and hardware it distributes. Neither decision may have been made with the intent of thwarting DNS-based evasion of ad/tracking, however, the resulting consequences may well be the same.

"... there is nothing you can do."

I am typing this comment through a text-only browser. HTTP requests, with a bare minimum of HTTP headers, are being sent from a proxy I control, not the browser. Yet the comment looks no different than any other comment. It works. I have freedom to choose whatever software I want to make HTTP requests.

I try to avoid any software (not just browsers) that access the internet and bypasses the system DNS settings. The word "hostile" is a good choice of words I think to describe such programs.

>Yet the comment looks no different than any other comment. It works. I have freedom to choose whatever software I want to make HTTP requests. //

I mean, sure there is, some form of DRM is possible. It might be circumventable, but it would be a PITA.

Is any browser written in Golang?

Go's UI tooling is... not great. It's more aimed at server side and CLI usage. In those niches it is awesome though

> Go's UI tooling is... not great.

Hopefully https://gioui.org/ quickly fixes that.

IIUC that's what DNS-over-HTTPS is trying to do, methinks.

Exactly. Same for the nextdns.io service which I'm happily subscribing to.