,
7 tweets,
2 min read
Read on Twitter
I honestly wonder whether the educators that love to bash Python features that are supposed to make it more “respectable” realize that the current brain drain caused by Python not considered adequate for non-science production use will eventually hit their bottom line too. (1/6)
The community _already_ consists almost entirely out of consumers: given the immense growth in the past years, the relative number of makers is negligible. For me, that's already very apparent at conferences and meetups and it will only get worse. (2/6)
We who want to use Python for serious (non-science) work have to fight two battles at once: colleagues/employers who‘d rather use JS/Go/Rust & those who don't want to add anything (even if it's optional) to the language that makes it less fun and/or harder to teach. (3/6)
It's no wonder so many have given up & many crucial packages are languishing. This isn't even the usual sustainability problem, this is a major clash of cultures within the community & I'm not sure for how much longer I want to deal with this myself. (4/6)
It's getting lonely. Our success stories are dead: YouTube is on C++, Dropbox is moving more stuff to Rust, and Instagram is flirting with a new runtime for their backend. It's hard to find a Go newsletter that doesn't contain a success story about moving from Python to Go. (5/6)
If you expected a conclusion or call for action here, I have none. Maybe this is how it’s supposed to go and Python’s time outside the sciences is over and I just need to move on and follow my friends that left years ago. (6/6)
Bonus point: did you know that most of PyCA (cryptography, pyOpenSSL, bcrypt, pynacl…) is selflessly maintained by people who don’t write any Python on their jobs _at all_? And that passlib hasn’t seen a commit in 2 years?
