I would not want to run https://example.com/: any large service probably has buggy automated systems hammering it, but https://example.com/ is almost certainly worse.
On the plus side, I suppose they have no paying customers or SLA to worry about.
miniblog.
Related Posts
Are there many good static analysis tools for CSS?
I have website projects in both Django and Express that almost certainly have unused rules due to unused classes.
I'm debating whether `from foo import *` is a bad feature for my toy programming language.
Forcing `import foo as f` and later `f::bar()` is so much more amenable to local static analysis. You also don't get issues with name clashes.
It's certainly convenient though.
I certainly see the appeal of an LLM system with full context and tool use (OpenClaw), but the lethal trifecta puts me off deploying it.
I do like the idea of an agent with a heartbeat though. A bunch of nice cron-style workflows can be built on top.