if a service runs TLS 1.2, and a client runs TLS 1.2, and they can talk to each other right now, why change the language?
if you released a thing, and people are choosing not to use it, is the right move really to enshittify their current choice to force them off it?
But if you only control one of the endpoints, then your ability to connect to a peer depends on what the peer thinks. And if the peer follows a standard that says your offered ciphersuites are all insecure, then you're out of luck.
So long as TLS 1.2 can still be used securely, its really not a big deal.
True, but from a technical perspective "necessity" might be a bit of a strong term. For example as far as I know there aren't any Windows versions left that don't have support for TLS 1.2 but are still supported (i.e. not EOL). iirc Windows Server 2012 has support, but it's not enabled by default. So that's the closest to "unsupported" you get with Windows.
I think this is mostly because people are some what hesitant of enabling TLS 1.3. Because merely enabling TLS 1.3 along side TLS 1.2 can trigger latent bugs in clients.