The answer is yes, I still use, but not Google nor Bing. Relying exclusively on LLMs sounds a bit dangerous and naive.

Until when, I don't know.

I'm still digesting what I've “witnessed” yesterday. I have no words for it, I'm baffled. Time to re-think…

For Django projects, I would say DjLint [1]. It doesn't cover all you asked, but makes the job of writing the templates (HTML) much more pleasant.

[1] https://djlint.com/

Exactly, this fits perfectly in the `.well-known` use cases. What a shame.

I've worked for many years with both frameworks. I have the opposite view, since I prefer the Django ecosystem and Python.

Rails has nice things, but overall, I prefer Django's approach and the language it uses.

I'm not surprised

Awesome, looking forward to testing it out. I really like that idea of being able to gradually migrate WSGI (Django) apps, or even support running both at the same time.

Some time ago, I built a similar project: https://github.com/dethos/worker-ddns

The main difference is that, for security reasons, it uses a "Cloudflare worker" to change the DNS record.

> Since Cloudflare API Token permissions aren't granular enough to limit the token access to a single DNS record, we place a worker in front of it (this way the token with extra priviledges never leaves cloudflare's servers).

It works very well, no complaints until now.

I solved it by avoiding Google products and services, whenever possible.

That 'whenever possible' qualifier gets more significant everyday

Sounds great. I'm eager to try it, when a release with early Linux support is published. Keep it going.

`curl https://zed.dev/install.sh | sh`