Python-specific, oddly generic name
Many argue the protocol only serves Python (its result-type schema is very Python-shaped) and should be named accordingly rather than claiming the generic TSP namespace.
Python itself is the problem
A large subthread debates Python's quality, with critics citing packaging, venvs and the 2-to-3 split, while defenders credit ease of use, the standard library and NumPy/SciPy for its success.
Unclear why LSP isn't enough
Several commenters ask what TSP adds; the apparent answer is machine-readable type queries so Pylance can plug in third-party checkers like Pyrefly or ty.