Hi Ivan,
Ivan Vučica wrote:
"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).
for the time being, I think it is better to just remove it.
I like your "preservationist PoV"
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.
Since we both are unlikely to do it in the near time.. I razed it.
Maybe we will get it back.
A lot of interesting things could have been done with SWI... e.g. use it
for checking updates, or feed installers. But as now nothing of that was
done, so since it was another thing to maintain... and the duplication
irked many, let us rest it, It can be resuscitated.
Riccardo
