and the most unrealistic thing is trump apologizing

I’ll die on the hill that curl | bash is fine if you’re installing software that self updates - very common for package managers like other comments already illustrated.

If you don’t trust the authors, don’t install it (duh).

You’re already installing a binary from them, the trust on both the authors and the delivery method is already there.

If you don’t trust, then don’t install their binaries.

does that count as a blow job?

“Do one thing and one thing well”

This is why the Python landscape is such a mess in the first place. The “one thing” should have been project management. Instead, we end up with 20 different tools that have a very limited context, often overlapping or being mutually exclusive to each other in functionality, and it’s up to each project to adopt and configure them correctly.

The mass adoption of uv is a clear sign that we’re tired of this flawed approach. Leave the Unix philosophy to core utilities of an OS.

They all have it.

Exactly what I did. I’d get a 65" monitor if there was any. But an always offline smart TV will do.

That’s pretty much the conclusion: you should try uv first, and there’s a small chance it doesn’t work for you and you’re not willing to fix it, or it’s out of your hands.

Examples include legacy projects and companies that don’t allow it (but I do question how they’d even enforce this, and how developers can even do their jobs if they can’t run binaries at the user level).

no shit, are some people really surprised by this, or do they just want the attention?

I just got a “swipe right or left” ad for duo

thanks, spotify, for occasionally reminding me I’m single

maybe i am a rug

Not 4y ago because I have the memory of a fish for the things I said.

But I’ll think of some shit I said 2 days ago, and I think that’s worse.

That’s really annoying to have enabled all the time, but might be useful for a “free-form” code refactoring that’s not just renaming variables.

it’s turtles all the way regardless; but it’s much easier to handle side effects if you have more numerous but smaller functions.

I prefer that because fully reading a module or component is not the most common scenario. The most common use case of reading code is (or should be) not caring about most of the implementation details until you need to; only then you have to go down the rabbit hole.

Longer functions force the reader to understand most of their context every time they get there, a problem especially when the function has a bunch of local vars.

single use functions are fine; I often break 20+ line functions apart and it makes it easier to test and reason about, it’s not just to avoid comments: block comments are just a sign that the function might be getting too complex.

U-238 is very stable, the post should have picked Radium or Francium for example

I can read it when the other person can write it

Inflation

gist.github.com

pastebin.com

I may choose to use single or double quotes in specific cases and need that change to be visible, even if the language rules say it is indifferent

Then a semantic diff is not for you, just use the old method.