The benefit of SWI would be that it is agnostic to the distribution - which can also be a bad thing if dependencies are not available... So it works for binary .app-Bundle downloads only if there is a 100% stable API and set of Frameworks.
> what's your point?
So if nobody cares about SWI any more, Wiki Pages are a better solution than nothing.
"Nobody cares" is strong: I care mainly from a preservationist point of view -- if I were to get it back up, I'd likely rewrite it in Go since that's what I'm most familiar with nowadays. Alternatively, some slightly more modern PHP, using as much from SWI as possible (but reworking queries themselves a lot).
GSWeb would be really nice, but I am not familiar with it, and I am not sure if I were to do it, that writing it would be fast enough.
There's also the option of getting it up and running inside a Docker/Podman container with older PHP, Apache2 etc.
All in all, I think the concern is "should we duplicate the information longer-term", not so much "nobody cares"...
So If anyone else feels like rewriting it, for preservation purposes, please go ahead; I'm unlikely to find the time, even though I'd like to. Hosting something with available source code and reviewed by us, especially containerized, is not a problem.