I'd like to inform you about an important change at envs.net.
As many of you know, the Matrix service consumes a lot of resources. This has become increasingly problematic in recent months, as it's making operation more and more expensive.
For this reason, I've decided to discontinue the Matrix service.
The shutdown is planned for March 1, 2026, but no later than April 1, 2026.
Registration of new Matrix accounts has already been disabled.
I believe this timeframe is appropriate to give everyone enough time to migrate their Matrix account to another server.
At the same time, the entire envs.net infrastructure will be moved to a new, more cost-effective server to return closer to envs' original minimalist values.
In the future, chat for the envs project will again take place via IRC.
As before, we will be using the tildeverse IRC server:
• Server: irc.tilde.chat
• Channel: #envs
Please respect this decision and refrain from sending private messages expecting justifications.
Thank you for your understanding and please accept our apologies for any inconvenience.
For CGI endpoints that are called infrequently—daily, weekly, or even monthly—the script startup delay is negligible. Even a persistent process waiting to handle a request can have its memory swapped to disk by the OS under varying server load. When a request finally arrives, the delay from swapping that memory back in can negate any theoretical advantage over a cold-starting CGI script.
I see this just as repetition of the 32 bit vs 64 bit operating systems. Why would anyone want to use 64 bit operating system? Instructions are longer, it requires more cache, RAM, disk space and so on, making performance worse. Nobody actually wants 64 bit systems. Endless problems with drivers, programs, etc.
Many don't have Matrix client installed.