pooberbee (any)

But that’s the point. The Onion tries to write real-sounding headlines, and c/nottheonion is for real headlines that sound particularly unbelievable.

One serving of peanut butter

Every day in standup

You coud try eating the pellicle from a batch of kombucha.

I’ve been each of these at some point.

This was not a case of “I agree with you, but…”, though. “But” is perfectly appropriate here to contrast between the first statement and the second.

Perlence subrange 6-36 is good too

I need a ttrpg with a pogs battle mechanic

Are you implying that sports aren’t popular everywhere or that everywhere is a dictatorship?

sex = true

But we’re playing Connect Four!

It’s already a good pun. When two different newspapers combine, they often use a combination of their two names for the new organization, for example the Chicago Sun-Times and the Minnesota Star Tribune. So Sun Tribune looks like such a combination, but for a newspaper on the Sun it needn’t be.

The trial and error is important, so you might end up buying a bunch anyway

Shit, I never thought that might be why, but we’ve dealt with a lot of skin irritation, and our kid prefers keeping a dirty diaper over getting changed. My day is ruined.

Armed Bear in the same vein

C shell

Hmm… I admit I didn’t follow the video and who was speaking very well and didn’t notice hostility that others seem to pick up on. I’ve worked with plenty of people who turn childish when a technical discussion doesn’t go their way, and I’ve had the luxury of mostly ignoring them, I guess.

It sounded like he was asking for deeper specification than others were willing or able to provide. That’s a constant stalemate in software development. He’s right to push for better specs, but if there aren’t any then they have to work with what they’ve got.

My first response here was responding to the direct comparison of languages, which is kind of apples and oranges in this context, and I guess the languages involved aren’t even really the issue.

I think most people would agree with you, but that isn’t really the issue. Rather the question is where the threshold for rewriting in Rust vs maintaining in C lies. Rewriting in any language is costly and error-prone, so at what point do the benefits outweigh that cost and risk? For a legacy, battle-tested codebase (possibly one of the most widely tested codebases out there), the benefit is probably on the lower side.

I like Hal Higdon’s website