I would break it into an interface that abstracts the sorting algorithm so that the sorting logic is decoupled from comparison logic or from the visuals. This would make it so that you can use different sorting algorithms and compare between them to see which one seems the most magical.
Magical might mean something different between us, so I don't want to assume and just give you an algo.
Craigslist is still around
Are there any versions where you don't have to pay to find the link of yourself?
Every high school yearbook
The article made a few good points, but a good amount of it was conjecture. I liked the part about comparing the two functions and showing that exceptions are faster but I think a big thing he's not getting is readability. Even in the functions he showed, you can directly see that the one using std::expected has the happy path and error path directly in the function signature, whereas the exception one doesn't.
As for the "error kind" trap he was talking about, that definitely exists, but ignores the fact that you can also get this same kind of error from exceptions. I've definitely gotten exceptions that I didn't understand from Python or Java libraries, but it's not a problem with exceptions but a problem with how they're shown. If there's nothing to tell me that I should have thought of that error, it shouldn't be an expectation for a dev to have thought of it.
Omg that's so fucking cuuuuuuuttttteeeeeee
It would go perfect on a costume for like a fake techno watch. There's probably real uses that's just my first thought though.
I've been working on a scraper to get congress stock trades. I'm thinking of potentially just serving it as an API. If theres an API that someone else knows about I'm all ears.
I forget that some people have crazy fast internet. Mine downloads 2.5gb in like 20 minutes.
This is an amazing idea for a bit and I really appreciate whoever made it.
Holy shit, that's in log scale.