The article also mentions Cisco briefly, who also suck. Almost as much as Palo Alto
The article also mentions Cisco briefly, who also suck. Almost as much as Palo Alto
It doesn’t. read the first words behind the link you posted:
Page Status: Outdated
Here is the actual one: https://packaging.python.org/en/latest/tutorials/packaging-projects/
Uv and pip do the same thing, uv is just faster.
Hatch has the same role as Poetry or tox: managing environments for you.
Applications should be packaged properly, in a self contained installer for exactly this demographic. It’s not Python’s fault that this isn’t common practice.
Sure, there was some hyperbole. Some people need some specific setuptools plugin or something. Almost nobody.
It’s not a standard, it’s built on standards.
You can also use Poetry (which recently grew standard metadata support) or plain uv venv
if you want to do things manually but fast.
It’s fixed, and the python version had nothing to do with it. Just use hatch
No it’s not. E.g. nobody who starts a new project uses setup.py anymore
Ooo damn that sounds exactly what I’d like to try.
On the other hand I feel like I’m too old for this shit. My system works fine, I understand everything, and things rarely break and never in an unrecoverable way.
It’s been great almost since I started using it.
I started using it exactly when 4.0 came out, because that’s when I started using Linux and I thought learning 3 didn’t make sense. But 4 only got stable around 4.4 I think. The problem was that 4.0 wasn’t intended to be for end users yet, but distributions didn’t realize that and packaged it right away.
KDE didn’t repeat that mistake. 5.0 was almost completely smooth sailing (some applications took a long time to port and looked ugly, that’s it), and 6.0 was completely seamless.
If I had to guess, probably variable refresh rate
No it’s not, that’s why some smart people are starring by defining a more interesting concept: educability.
Huh, I found it to be so much easier to set up than nginx that I wrote the devs a little thank you message
That’s just completely wrong. Just try e.g. replacing the journald backend with the old text based syslog, and not only will you discover that is possible (which directly contradicts what you just said), it’s also easy!
The only thing I liked was arch’s pretty boot sequence … which I stared at for a while because SysV init was so slow.
systemd, not SystemD, or system d.
But yeah, wonderful talk!
Because they just have their own brain chemistry as the basis of it whereas the above comment clearly states:
Rust has proven empirically that the tradeoff between performance and safety doesn’t need to exist.
Which is truth. And it’s much easier to base a coherent argument on truth rather than vibes.
Weird how he’s helping the far right in both cases.
Exactly the same here. I went Nexus->Pixel 2->Pixel 6
Works flawlessly, except of course that I only get like ~28h of battery life instead of the ~48h in the beginning