sukhmel

I guess, opening a PR without forking is possible, but hey that's sort of incredibly bullshit idea

Pretty much sums my experience with windows, something you want will either work fine, or be mysteriously broken beyond repair with no apparent reason. MacOS is like that sometimes, too. Linux is not perfect, but it usually allows for a fix to exist.

Not only them, and I'm not here to blame 😅

There's no such thing as "zeroith" because it's called "zeroth — being numbered zero in a series"

This works for building storeys, this would work equally well for tables. The only reason this is not used often is because the series are rarely zero-based in anything that doesn't also want to equate index and offset.

You're right that first may be read as "opposite of last", that would add to the confusion, but that's just natural language not being precise enough.

Edit: spelling

Edit2: also, if you extend that logic, when you're presented with an ordinal number, you would need to first check all the options, sort them, and then apply the position you're asked, that's not really how people would expect ordinal number to be treated, not me, at the very least

Wow, Republicans are Marxists 🤔

That was about what I meant, but thanks for expressing this, sorry I was vague.

…but still edible. I usually alternate between eating kiwi whole and with a spoon ¯\_(ツ)_/¯

You were supposed to not eat those? Well, I figured, I'm not obligated to eat everything if I want less spicy, but I never thought that those are decorative

I first thought you were talking about waving to pedestrians to cross when you stop to let them go. Which (edit: stopping and waiting) is a correct and expected behaviour, afaik

Are we still talking about COBOL?

To be fair, I disagree with all the points author makes, except for performance which is important but may be less important than code clarity in different cases. I am surprised that exceptions perform that well, and I am surprised the author said that compared C++ exceptions to Rust results, but actually did the right thing and compared C++ exceptions with C++ expected first. I thought it was going to be one of those "let's compare assembly to lisp"

Yeah, I shaped my words poorly. What I meant is that errors are sort of equivalent to exceptions, but errors are first class citizens of type system, and this is an improvement over exceptions being kind of independent of type