DeVault: Announcing the Hare programming language

DeVault: Announcing the Hare programming language

Getting you to stop depending on unsupported services is the goal. The service is unsupported, and its uptime is a fluke - by taking it down frequently, you cause people who need it to be up to switch to something that's supported in order to retain their uptime, or they do whatever's needed to get the service they depend upon back into support.

Basically, it's better to have the service become deliberately unreliable and trigger people into worrying about it, than to let it float along seemingly working just fine and then go offline permanently when it breaks and no-one knows how to fix it. A planned outage means that anyone who doesn't know that they depend on your unsupported service learns about their dependency at a point where fixing it is trivial, rather than finding out that they depend on it when the service breaks in a way that cannot be fixed.

I've had experience of working somewhere that refused to have planned outages for unsupported services - it was not pretty when the hardware failed, and it turned out to be impossible to get replacement parts, and non-trivial to port the software onto a machine we could get. And it turned out that something critical depended on the service on hardware that was now dead and not replaceable. Oops.