pooberbee (they/she)

Seems like not a real programming paradigm, and I don’t mean in a No True Scotsman way. It really is in a separate category of thing. Could’ve said logic programming or stack-oriented programming.

Tf is “return oriented”?

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.

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.

My expectation is that a post’s score is upvotes minus downvotes, but I think it should be more like upvotes plus comments with downvotes excluded (or maybe let users filter based on upvote/downvote ratio or something). Maybe count commenters instead of comments.

Well it wasn’t a website, for what it’s worth.

Tangentially related, I remember at one of my jobs being tasked (several years in a row) with updating the copyright year in all our source files’ headers.

And lawyers are pretty likely not staff at all.

I suspect there are a lot of “Rust devs” that are little more than kool-aid drinkers. Common refrains are that Rust is the fastest language, most type-safe language, and most powerful language. Rust certainly seems to move the state of the art forward in some ways, but you can still write garbage code in it.

I’ve worked with lots of different people in lots of different languages, and I think I’d rather good people in a bad language than the other way around by a mile.

It always grates on my nerves to read laypeople’s opinions of how software development should happen. So much unfettered stupidity.

The absolute disregard for the meme format here. I’m too high for this.

Ethan Iverson has a pretty interesting article about jazz pianists and how their individual styles changed (or didn’t) over the course of their careers, and he noted that IIRC many pianists whose technique was mainly finger-focused had a significant shift in style later in life versus pianists whose technique involved more arm movement.

Either #2 or #3. /usr/bin and /usr/local/bin exist for that purpose, but some people prefer to keep personal scripts and such in home, maybe as part of a dotfiles repo or something, and so just add ~/.dotfiles/scripts or something to PATH.

I prefer SQL, because you can pronounce it “sequel” or “es-cue-ell”, and it’s fine. CSS just doesn’t have that kind of flexibility as a language.