The available libraries are the ONLY excuse for Python.
When you need tools more sophisticated (and labor intense) than your tool to make your tool functional, it’s time to re-examine your choice of toolchain.
Python is great for standalone scripts/CLIs with standard system dependencies. For actual apps you want venvs, probably managed by uv these days.
I’ve written 1000s of python CLIs/scripts over the years, typically wrapping APIs for otherwise shitty enterprise and SaaS software (also many one-off scripts for ETL).
Nowadays, AI writes these scripts in a fraction of the time (and reads the shitty API docs / otherwise figures it out) and my CLI toolkit is better than ever (with $0 ongoing cost). Calling MCPs from CLIs is also interesting, as some vendors never had usable APIs before now.
I learned basic programming in BASIC in the 80s. Back then when you needed more speed, you grafted in assembly calls, and the speed difference was dramatic.
Straight Python feels as slow as BASIC - it’s got nifty speedy library calls to stuff written in other languages, but if you need something that’s not available in a library, now you’re writing a library function for Python, in another language, and why not just write the whole thing in that other language and ditch the heavy toolchain?
I used to work at a place that used Jython (which never got updated to Python 3, BTW) and was responsible for trying to keep that shit working even as various libraries started dropping Python 2 support.
I still get a thousand-yard stare when I think about it.
(Still worth it vs. writing actual Java code, though.)
Just recently there was an article here, where a person claimed that recommended python tooling is inadequate because they needes to read two paragraphs of documentation. Endemic problem really.
I have lots of experience with node and a little with python.
Python seems great for working with large data sets and I really like jupyter notebooks. The available libraries are really great.
However, the thought of installing a Python CLI app makes me twitchy.
I suspect that node has all the same problems and that I’m used to working around them, but all the Python environment stuff is a nightmare.
Edit: dear python dweebs: I don’t care.
The available libraries are the ONLY excuse for Python.
When you need tools more sophisticated (and labor intense) than your tool to make your tool functional, it’s time to re-examine your choice of toolchain.
uv is a fantastic tool if you didn’t know
Yeah, absolute nightmare of writing
pipx install programname.iykyk
Just stand up a VM to do it in, so you don’t corrupt anything else you made in python that you also want to run on the same box, amirite?
Python is great for standalone scripts/CLIs with standard system dependencies. For actual apps you want venvs, probably managed by uv these days.
I’ve written 1000s of python CLIs/scripts over the years, typically wrapping APIs for otherwise shitty enterprise and SaaS software (also many one-off scripts for ETL).
Nowadays, AI writes these scripts in a fraction of the time (and reads the shitty API docs / otherwise figures it out) and my CLI toolkit is better than ever (with $0 ongoing cost). Calling MCPs from CLIs is also interesting, as some vendors never had usable APIs before now.
Python environment/packaging sucks, but at least the language itself doesn’t.
I learned basic programming in BASIC in the 80s. Back then when you needed more speed, you grafted in assembly calls, and the speed difference was dramatic.
Straight Python feels as slow as BASIC - it’s got nifty speedy library calls to stuff written in other languages, but if you need something that’s not available in a library, now you’re writing a library function for Python, in another language, and why not just write the whole thing in that other language and ditch the heavy toolchain?
It’s fine actually, all of the problemswith python packaging and env are overblown to insane degree.
I used to work at a place that used Jython (which never got updated to Python 3, BTW) and was responsible for trying to keep that shit working even as various libraries started dropping Python 2 support.
I still get a thousand-yard stare when I think about it.
(Still worth it vs. writing actual Java code, though.)
yeah everyone elses experience is invalid.
Npm/yarn are absolute horseshit.
See? Node is just as bad as Python now.
Yep, they are.
Just recently there was an article here, where a person claimed that recommended python tooling is inadequate because they needes to read two paragraphs of documentation. Endemic problem really.