Hrm. This is a good question. In the past, our theory had been that someone might revisit this, so we should leave the code in place. But, it's not wrong to re-evaluate it, and simpler code has some advantages. I am ambivalent.

I vote to remove it for now; the code will always exists in the git history for reference.

There hasn't been a direct interest in it (and with direct I mean a contributor with the interest, ability and time to support it), and we are not updating it/keeping it working since the start of 4.x, so it's just dead code.

Additionally, we don't have the infra for the CI to run tests, and it would be an additional maintenance burden for whoever finds itself having to update a library, and reconfigure it on all the platforms and architectures.

In other projects, we've generally followed the idea that it will exist in git history so we can revive it there, where necessary, as Stefano is saying. Deleting code is a joy!

That said, at the very least, we would still want to get rid of the .table files right? Happy to pare this down in some way, wherever you guys decide. But I figure I would start here by submitting the maximalist approach.

Between @Smjert and @zhumo that's two votes to remove, and none to keep. I'm onboard!

@zhumo -- you mentioned not accidentally removing windows, other than that it's seems great.