As far as I know you're right, also using pyproject.toml generates platform independent dependency trees (I don't have experience with the tools he mentions but that's what poetry does), requirements.txt does not and must be generated on a server or carefully picking the crossplatform version of the packages.

Also kinda weird he says to not use pip, but requirements.txt are pip commands... And should be running with pip... Hmm I don't know about this article anymore.

uv and rye (which depends on uv) use pyproject.toml and spit out requirements.txt like files as lock files. They aren't platform independent but are easier to install in a docket container (just use pip inside the container). Not sure about hatch/pdm which they recommended. Some people use pip-compile which also converts toml files in requirements.txt files

Not until it gets thrown out kicking and screaming like python 2 was, I guess.

AFAIK several cloud services rely on requirements.txt for deployment.