I love the implication that he’s speaking to the AI and wants to not disturb people, but has no headphones on. so I can only assume it’s responding from the speakers.

I’m not hating on this feature, but it’s frustrating to me because individual commits could already solve this. This is .ore a complaint of people’s commiting style than anything. But so many places just squash to merge, so why bother making them pretty? Either way though, it can still be useful to say a specific range of commits is something to view as a chunk.

You could always just make the ticket yourself. But yeah, I hate this policy as well.

I first check the logs for what the failure is.

I know what this is, but every time I see it I think it’s FSF related lol

It felt repetitive to me too lol. I thought it scrolled back up to the top of something.

Never forget that Epstein was talking about fucking children in plaintext on Gmail and they did nothing whenever you see politicians say encryption should be illegal so they can capture criminals.

Finally, I’ve been waiting for Linux to work on the Atari Jaguar before I pulled the trigger. People called me a hold out in 1993.

It’s not even the good midwit format lol

Doesn’t Rust’s safety guarantees mean automatic reference counting? Or am I misunderstanding. I guess it means more like happening dynamically at runtime.

I’ve heard a lot of good things about the book “automate the boring stuff with Python.” It focuses on practical examples more than the theory. It’s also available for free since it is licensed under Creative Commons. That said, I haven’t personally checked it out. Just mentioning it as something that focuses on goals and works towards accomplishing them, which sounds like what you’re looking for.

Eh, I don’t really see a problem with releasing an app before you “should” release one. I don’t think the world improves by discouraging amateurs from sharing their work. Now whether they actually try to learn and grow or just keep vibe coding, who knows.

I guess in my mind I just associate raw pointers with low level. But I guess Rust lets you do that with unsafe blocks still?

My point is that the natural, not trying to push the limits definition of wheel is already much broader than door.

My bedroom has about four doors in it, but even just one dresser has like 16 wheels inside of it, two per drawer.

Depends how generous we are with the definition of door. Do we consider any sort of opening a door? Is the way bugs get into the ground a door? If so, then doors. Otherwise it’s probably wheels. I think the general definition for what we consider a wheel (without getting really loosey goosey like I was before) is much more broad. A door is something for a person to open and close. A wheel is a round thing that spins. Even if you’re thinking something like “well, buildings have a lot of doors, and there are more buildings than cars…” Consider that a lot of furniture has wheels. Drawers have wheels. My dishwasher has a “door” but the racks have wheels. My office chair has 5, maybe 10 depending on how you count. I’ve got like four in the house I think. That’s already like 40 wheels from just office chairs.

Fork me on GitHub!

Is rust low level? Genuine question, not trying to start an argument. I guess I sort of view it as low level but with a high level compiler lmao.

Yeah, I think the flow was this,

1. Is this vibe coded?
2. Partially, because of some of the features of Rust.
3. Borrow checker?
4. (Humourous misunderstanding ensues.)

Basically asking if the thing that gave them trouble was the borrow checker.