In hindsight, it was a mistake to let the mule drink.

I appreciate that they called them anti-Israel protesters and not antisemites (or similar).

Oh don't think for a second he plans to actually go after the real cartels. He just wants an excuse to kill random Mexicans.

After his orders to kill people we'll have news reports from actual Mexicans saying the people he order killed weren't drug dealers. And they'll be right.

I don't know if Republicans will accept this. As much as they fear betraying Trump, taking away their power in Congress is exactly the type of move that could get Trump impeached (a third time).

Here's how that's going to go:

• He'll send in the military and they'll successfully kill some "drug dealers".
• Mexico will be (rightly) pissed AF.
• Mexico will retaliate by just ending all exports to the US of some essential goods (e.g. tomatoes, car parts).
• The price of those goods will skyrocket. Business will close. White people who voted for Trump will bitch that, "he's hurting the wrong people" again (leopards eating faces).
• Mexico will refuse to take "back" their immigrants because of Trump's bullshit.
• Trump will "suddenly" need to jail a lot more "illegals" that he's rounded up.
• They'll start making up stories about how all the millions of people in the concentration camps are nasty criminals and murderers... As an excuse for the poor treatment and blatant raping and murdering going on.
• Right wing media will tow the party line. Anyone defending the "criminals" (which will include families with children) is a traitor to the country.

History will repeat itself.

without type safety your code is no longer predictable or maintainable

This sounds like someone who's never worked on a large Python project with multiple developers. I've been doing this for almost two decades and we never encounter bugs because of mismatched types.

For reference, the most common bugs we encounter are related to exception handling. Either the code captured the exception and didn't do the right thing (whatever that is) in specific situations or it didn't capture the exception in the right place so it bubbles up waaaaay too high up the chain and we end up with super annoying troubleshooting where it's difficult to reproduce or difficult to track down.

Also, testing is completely orthogonal to types.

It'd be ineffective and in fact, decrease the likelihood of obtaining that default assumption of innocence that cuteness provides. It'd be like tying a pink ribbon to the tail of a tiger. The ribbon itself would be cute but the tiger would still be viewed as a dangerous predator.

Might help with getting out of manual labor though 🤔 🤣

fast changing

This happens because JS is such a shit language! There's no best way (or even good way) to solve any given problem. This results in everyone reinventing the wheel every goddamned day.

Someone like you and me thinks to themselves, "this is such crap!" And they're right! 🤣 So they come up with a new way of doing things that's just a little bit better and they post it publicly.

Then some huge amount of new JS developers (there's always a steady stream) and a few old ones think, "hey, this isn't a bad idea!" So they start using the new thing. Then it becomes the hot new thing and suddenly huge amounts of JS code is depending on it.

Then people start to realize that this new way doesn't quite work so well in certain situations so they add on to it by making new utilities/GUI libs. Others see the wisdom in this and adopt these new tools.

These new "solutions" build and grow in complexity until new JS devs working with the new paradigm think, "this is such crap!" And they're right!

😂

Yeah that's annoying but it's a short-term problem. Python just recently cleaned up some long-standing issues that broke backwards compatibility in packaging (for certain things). Most public modules that broke made trivial changes to fix the problems (once they learned about them) and life went on.

However, for some fucking reason a whole bunch of dependencies related to AI are dragging their feet and taking forever to fix their shit. Insisting that everyone "just use Python 3.10" and it drives me nuts too.

This problem started to become a real thing almost two years ago (so they had plenty of warning and time to fix things) and yet here we are with still a handful of core dependencies that won't install for things like Stable Diffusion, Flux, and various LLM stuff because they're dragging their feet.

I blame corporate culture: Enterprises hate upgrading their shit and they're as slow as glaciers sometimes. There's probably tooling at Nvidia, for example, that needs a ton of work for Torch to work with new versions of Python and since all their documentation already was written for running on Python 3.10 (and Ubuntu 22.04 LTS) they've created a lot of work for themselves.

Any day now they'll finally finish fixing all these little dependencies and then we'll have another two years of ease before the problem rises again with Python 3.14 and it's massive GIL-free improvements that require big changes in code to actually take advantage of them.

Why? The most annoying thing that I remember about it was popular modules that hadn't been ported yet. In essence, a temporary problem; growing pains.

The Unicode/string/bytes changes were welcome (to me). But that might just be because I had actually encountered situations where I had to deal with seemingly endless complexity and ambiguity related to Unicode stuff and encodings. Python 3 made everything much more logical 🤷

Haha: "A space breaks everything." Fuck YES! Are you kidding me‽ It's one of the best features!

Why? Because it's so easy to see. In other languages you've got semicolons which are surprisingly difficult to notice when they're missing. Depending on the situation (or if you're just new to programming) you could spend a great deal of time troubleshooting your code only to find out that you're missing a semicolon. It's frustrating and it makes you feel stupid which is never a good thing for people who are new programming.

Types are in a different category altogether with seemingly infinite reasons why you'd want a feature-rich, low-level type system and also why you'd want to avoid that.

IMHO, the point of Python is to be a simple language that's quick to write yet also very powerful and speedy when you need it to be (by taking advantage of modules written in C or better, Rust). If it had a complex type system I think it would significantly lower the value of the language. Just like how when I see an entire code repo using Pydantic and type hints everywhere it makes the code unnecessarily complex (just use type hints where it matters 🙄).

I'm not saying using type hints on everything is a terrible thing... I just think it makes the code harder to read which, IMHO defeats the point of using Python and adds a TON of complexity to the language.

The promise of type hints is that they'll enable the interpreter to significantly speed up certain things and reduce memory utilization by orders of magnitude at some point in the future. When that happens I'll definitely be reevaluating the situation but right now there doesn't seem to be much point.

For reference, I've been coding in Python for about 18 years now and I've only ever encountered a bug (in production) that would've been prevented by type hints once. It was a long time ago, before I knew better and didn't write unit tests.

These days when I'm working on code that requires type hints (by policy; not actual necessity) it feels like doing situps. Like, do I really need to add a string type hint to a function called, parse_log()? LOL!

In the US we teach kids that trash men are suckers and idiots that didn't work hard enough in school! Also, that trash is an externality: Someone else's problem.

"We pay taxes for people to clean that up! Why should I spend my valuable time doing someone else's job‽"

It's an awful culture.

They get paid more than most people would think but it's still not enough based on the hazards of the job. They get exposed to all sorts of nasty things that can ruin their long term health and they have increased likelihood that they'll get a life-altering injury at work.

I'm receptive to your radiant reply.

What movies? Hopefully nothing too exciting.

You're never right 🤷

Your wish has been granted! You will now keenly remember old photographs 👍

To get what I want by just being cute. Like little kids or cute girls. Or to be automatically excluded from manual labor/heavy lifting for the same reason.

If you're a healthy boy, the moment you become a teenager is the moment you're just expected to be performing manual labor or other hot, sweaty activities. At least in the US 🤷

Self-tapping too! Nice 👍

"Listen to your body" No, that's how you get fat. Your body wants to build up fat! That's how we survived famines. Famines that don't happen anymore.

Listen to your doctor instead 👍