I quit python after realizing the amount of effort it required to just implement the tooling for a project… when all of that comes included with rust. I have spent maybe an hour in the last year thinking about tooling. Glorious.

But yeah, I feel for you. It is an impossible sell when they pay off is impossible to understand without a Time Machine and the only thing known about the cost is that it’s high. But for new people and projects, I can’t imagine starting with python in 2026.

I’ll always remember the outrage I felt when they go to the hospital when her father needs heart surgery and they have to pretend not to know the hospital director because he was previously their janitor and they were afraid to embarrass him by acknowledging that and not getting treatment. Absurdity.

They all have APIs of course, but you have to contact sales for what I’m sure is a very expensive negotiation. I believe that’s what news aggregators like Apple News and ground news does.

But yeah, it sucks. AP is outstanding. Their push notifications are all the mainstream news anyone really needs for timely updates. But their App is awful once you click on those notifications.

I also thought the terminal usage was neat. The movie starts with a sudo command. I also think I saw PyTorch.

E-bikes are really power efficient, and food production is very inefficient. Your average American commute probably uses less power per day than a refrigerator.

That said, it’s not really meaningful when comparing to the carbon footprint of driving. Diet and e-bike vs bike just really does not matter compared to the choice of driving an ICE or not driving an ICE. It’s more of just a neat fact.

The entire complaint here is that automating this risks that was is encoded is not what you want.

What I absolutely loathe and instantly block is AI narration. That’s an instant deal breaker for me. And it’s gotten to the point that without a shot of the creator or obvious humanisms like microphone sounds, I assume a new creator is AI tts reading an LLM generated script. There are thousands of these channels.

It’s a by product of tax policies and lax anti-monopoly policies that allows incompetence to thrive. If a company gets too big to fail, then it stops calibrating for competency.

The most effective military leaders in history had a deep understanding of fighting war because they came up through the system and the cost of failure was their death.

This is cope.

I do give you that rust is more verbose and thus more token heavy. However that verbosity is meaningful and the LLM would have to spend tokens thinking about the code to understand less verbose languages. So I’d consider that a wash - in some cases it hurts and in some it helps.

The downside is that maybe it should fail sometimes when an idiomatic approach isn’t viable… instead it will implement something stupid that compiles and meets the request.

Yes you can lint out unwraps and other panic operations, but if there was a subset of no-panic rust a large part of the issue detailed in this post goes away. But it’s frustrating working with a language that has so many operations that can, in theory, panic even if in practice they should only do so if a bit flips. Like a proving an array is non-empty or working with async. You either end up with a lot of error handling for situations which will never happen or really strange patterns like non-empty list pattern (structure with first field and then your list). Which of course ends up adding its own bloat.