This has not been discussed on the WG mail list, so despite your
apparent limited ability to conceive of valid objections, they do
exist.
actually it's the other way around. there are far more valid
objections to the use of SL than there are to deprecating SL.
Trying to use SL for routing between sites is what is broken.
SL is broken whether or not you try to use it for routing between sites.
It is far cheaper to train an app developer (though there may be an
exception or
two) to deal with it than it is to fix all the ad-hoc solutions that
people will come up with to replace SL.
no, you have it exactly opposite. you can't train an app developer to
fix the problems caused by SL because in order to fix the problems
caused by SL you have to deploy extra infrastructure and create a new
network on top of the dysfunctional one that uses SL. and it's far
cheaper and cleaner to solve those problems in other ways.
SL is the ad hoc solution that didn't get sufficient scrutiny before
being approved. Fortunately that mistake has finally been rectified.
Again, this is not a trival issue and there has been no discussion of
it
on the WG mail list. The decision has NOT been made.
a clear consensus of the WG has spoken.
Keith