> VirtualScreens does in theory give you the ability to show different
> workspaces on different VS's, which is a place the other code doesn't
> even try to go.
AFAICT this is the only feature of `VirtualScreens` not provided by the
new code. So if we care about it, the better option would be to add
that feature to the new code.
> But even that comes with a lot of limitations due to X
Indeed, so adding that feature to the new code would probably want to
use a different implementation strategy (and/or rethink the UI).
> From the dev side, life would be easier if it could all go away. From
> the user side, it sure seems like it has too many weakness and quirks
> to be attractive even if it were the only way to attempt dealing with
> multiple monitors, and it won't be anymore. So, I propose that we
> deorbit it. I suggest a plan like:
Agreed.
> - In the upcoming release (4.1.0 presumptively), we deprecate it and
> complain when we see it in configs, but everything continues working
> the same.
I think we want to go further: disable it by default and force the users
to use a new setting in their config file to reactivate it (and that
new config should have a name that makes it clear that the feature will
disappear at the next version). We want to make sure that users who
care about this feature come and complain here.
Stefan
