> our civilization relies upon workers to shoulder the burden everyday.
Our civilization? Nah. Just that one shithole country. Greatest country in the world and they schedule a single guy to work both tower and ground frequencies at a major airport, it's almost like they're asking for this shit to happen.
And before anyone mentions understaffing, this literally one of the plethora of problems that the rest of the world figured out while the U.S. continues to act special.
Not to gatekeep things but if you think uv solved python dependency issues then you probably never had those issues in the first place and pip would have been enough for your use case. Conda on the other hand, with external binary dependencies, now we're talking.
I’m someone who is not a python developer but has to use python tools and run other people’s python code. I have suffered through learning about anaconda, virtualenv, pip, and more. Uv is the first time there’s a tool that just runs the software without requiring me to become a python ecosystem expert
The key issue uv solved wasn't dependencies, it was environments.
I used to have hundreds of venv folders scattered around my machine. These days I use "uv run" or "uvx" or "uv run --with boto3 python" and uv handles all of the bookkeeping for me.
> The key issue uv solved wasn't dependencies, it was environments.
and not specific, niche features.
I don't know of such a command in Poetry, but it could still be solved with dev groups or running Python in the virtual environment and installing the package.
I can't help but find type hints in python to be..goofy? I have a colleague who has a substantial C++ background and now working in python, the code is just littered with TypeAlias, Generic, cast, long Unions etc.. this can't be the way..
Typing is a relatively easy way for the human author and the machine to notice if they disagree about what's going on before problems arise. It is unfortunate that Python doesn't do a good job with types, I was reading earlier today about the mess they made of booleans - their bool type is actually just the integers again.
Prior to 2.3 Python didn't have booleans, just "truthiness". In 2.3 they added the Boolean class as a subclass of int (because of patterns of development it was a pragmatic choice). True and False were introduced, but they were able to be reassigned which could cause all manner of fun. 3.x made them keywords which put a stop to that but the int aspect remained.
A related screw-up is implicitly casting everything to bool. A lot of languages made that mistake.
Overall I'd say they didn't do an awful job though. The main problems with Python are the absolutely abysmal tooling (which thankfully uv fixes), the abysmal performance (which sometimes isn't an issue, but it usually becomes an issue eventually), and the community's attitude to type checking.
Actually type checking code you've written yourself with Pyright in strict mode is quite a pleasant experience. But woe betide you if you want to import any third party libraries. There's at least a 50% chance they have no type annotations at all, and often it's deliberate. Typescript used to have a similar problem but the Javascript community realised a lot quicker than the Python community that type hints are a no-brainer.
Because Python decided that (for the usual New Jersey reason, simplicity of implementation) bool should just be an integer type the Liskov criterion comes into play. If we can X an integer and we've agreed bool is an integer => we can X a bool. That's not what booleans are but hey, it's sorta close and this was easier to implement.
So, can we add two bools together? Adding booleans together is nonsense, but we've said these are a kind of integer so sure, I guess True + True = 2 ? And this cascades into nonsense like ~True being a valid operation in Python and its result is true...
Out of curiosity, I tried running `~True` in a Python 3.14.2 repl and got this output (the -2 is part of the output):
>>> ~True
<python-input-1>:1: DeprecationWarning: Bitwise inversion '~' on bool is deprecated and will be removed in Python 3.16. This returns the bitwise inversion of the underlying int object and is usually not what you expect from negating a bool. Use the 'not' operator for boolean negation or ~int(x) if you really want the bitwise inversion of the underlying int.
Yes, the article I was reading was about proposals to er, undeprecate this feature. Reasoning that well, sure it's obviously a footgun - but it works for integers and we've said bools are integers so...
> So, can we add two bools together? Adding booleans together is nonsense, but we've said these are a kind of integer so sure, I guess True + True = 2 ? And this cascades into nonsense like ~True being a valid operation in Python and its result is true...
The bitwise negation is indeed janky and inaccurate, but True + True = 2 is absolutely a valid thing to say in boolean algebra. Addition mean "or", and multiplication means "and."
I always remember learning that 2 was a legit enough way to represent the result of 1 + 1, but the internet seems to agree with you mostly. Though I contend that 1 + 1 = 2 is unambiguous, so is fine.
Huh, I learn something new, I was not aware of "Two element Boolean algebra" nor just how deep this particular rabbit hole goes.
It's fine that 1 + 1 = 2. That's just integer arithmetic. The problem is that the booleans are not "just integers" and so Python's choice to implement them as "just integers" while convenient for them has consequences that are... undesirable.
the alternative should be using a real statically-typed language instead of glorified comments that don't do anything without outside tools.
I understand that very large code bases have been built in python and this is a compromise to avoid making them rewrite Ks upon Ks of LoC but as it stands, Python type annotations are akin to putting a Phillip's head screwdriver on a ball peen hammer; the screwdriver is not a real screwdriver and the ergonomics of the hammer have been compromised.
Well yes I agree using Rust or whatever would be better, but if your options are Python or Python with type hints, then the latter gets you closest to proper static typing. They're really not that bad with Pyright in strict mode. Mypy is rubbish.
This, honestly. Seeing all those billionaires on inauguration day lined up to kiss the ring was utterly pathetic. Like what is the fucking point of having billions of dollars if you're just going to be someone else's bitch. And for what? A couple more billion dollars. Oof
I hate it when people obfuscate the fact that organizations are not individual entities. Someone, or a group of people, decided to do this, not some faceless org. Some had to greenlight this.
Our civilization? Nah. Just that one shithole country. Greatest country in the world and they schedule a single guy to work both tower and ground frequencies at a major airport, it's almost like they're asking for this shit to happen.
And before anyone mentions understaffing, this literally one of the plethora of problems that the rest of the world figured out while the U.S. continues to act special.
reply