In some ways, yes, but yet it's what reality is. There was probably some last factor kicking in that triggered the cascade, but there were probably many non-happy-paths not properly covered by working backup/fallback strategies.
So a report could totally still tell "it's X fault", pointing the finger there. Government would blame the owner of X, some public statement about fixing X would be made and then the ones working in the field should internally push toi improve/fix their own (reduced) scope.
I don't know what will come of this report in the next months/years, I will keep an eye on it though, since I live in Spain :)
I kind of feel like the nature of the Python ecosystem is a dozen or so extremely useful frameworks/tools that everyone uses heavily for 3 years and then abandons and never speaks of again.
I'm not very deep in Python anymore, but every time I dip my toes back in it's a completely different set of tools, with some noticably rare exceptions (eg, numpy).
i think most of the previous package management tools have been like 70% solutions - for 70% of things, they're much better than previous tools, but then 30% of the problem goes unaddressed. For example, poetry does a good job at managing your package, but decided not to manage python versions. So, I still need some other bootstrap process involving a huge pile of bash.
uv feels like the first 100% coverage solution i've seen in the python space, and it also has great developer experience.
I can't speak to the rest of the ecosystem, when I write python it's extremely boring and I'm still using Flask same as i was in 2016.
I think, it may be the first time I am actually upset by acquire announcement. I am usually like "well, it is what it is", but this time it just feels like betrayal.
Nothing. I was very much aware of their prospects. Well, best-case scenario I could imagine them being acquired by Google or Microsoft, that would have looked like a prettier death, to be honest. Anyway, knowing that people eventually die doesn't mean you are immune to being sad when somebody dear actually dies. Especially when they die so young and full of potential.
It literally says on the homepage/the page you linked, that pixi is just a frontend for uv in the background to interface with PyPI and the project TOML files.
that isn't quite true, it defaults to conda packages (and so supports non-pypi things, its main advantage), I believe only when you are mixing these with pypi packages does it then also use the same resolution library backend as uv (and indeed directly at the rust level) https://pixi.prefix.dev/latest/concepts/conda_pypi/
pixi offloads PyPI ecosystem stuff to uv, but pixi is conda first. The team were actually the first to build a Rust based Python package resolver (rip), but after uv was released they migrated to uv's resolver (Python package resolvers are hard and a lot of work to build and must be tested against the whole ecosystem).
Even without looking it up to know for sure it was pretty obvious and could be inferred by anyone playing the game. Especially the scanning, which was painfully obvious to be a data collection method.
Am I weird in that I don't think I ever interacted with a bank teller?
The only bank employee I ever interacted with was when getting a mortgage and maybe opening an account, but at least here in the Netherlands, I don't think there are any bank tellers left really? Old people complain of course, but am I missing something here?
Nothing wrong with middle men per se, but problems do arise when we all rely on the same middleman: those become way too powerful and can do nasty things.
By that time, no one can do without the nasty middle man as we have forgotten or never learned the skills to fend for ourselves and are thus beholden to the nasty middle man.
Ha, I noticed this too! And even my 3 y/o picked up on this.
We have a set (something with Spiderman IIRC) that attached wheels with yellow pins that allow for better rolling of wheels. The black pins are too tight for this indeed.
You would hire someone with the expactation that they learn, but you also need to pay them. New hires always slow the team down. And currently you wouldn't even get much out of them, as you can delegate those tasks to AI.
Additionally you can not even be sure that the junior will learn or just throw stuff at AI. The amount of vibecoded Code I have to review at the moment from Seniors is stunning.
So yeah, the market needs Seniors, but there is basically no incentive for a company to hire a Junior at the moment. It's just easier and cheaper to pay a bit better than the market and hire Seniors then to train a Junior for years.
Looks an awful like project management to me, but not for human coders. Maybe a setup like this will allow me to be a project manager without dealing with actual humans :-)
reply