pooberbee (they/she)

https://www.swi-prolog.org/pldoc/doc_for?object=%23>%3D+%2F+2

It’s a better replacement for the built-in >= predicate.

Yeah, you would get a runtime error calling that member without checking that it exists.

Javascript and not Coq?

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.

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