It's sometimes nice to be deterministic.

I don't often care about a specific order, only that I get the same order every time.

Thinking about this upfront for me, I am actually wondering why this is useful outside of equality comparisons.

Granted, I live and work in TypeScript, where I can't `===` two objects but I could see this deterministic behavior making it easier for a language to compare two objects, especially if equality comparison is dependent on a generated hash.

The other is guaranteed iteration order, if you are reliant on the index-contents relationship of an iterable, but we're talking about Dicts which are keyed, but extending this idea to List, I see this usefulness in some scenarios.

Beyond that, I'm not sure it matters, but I also realize I could simply not have enough imagination at the moment to think of other benefits

I work on a build system (Bazel), so perhaps I care more than most.

But maybe it does all just come down to equality comparisons. Just not always within your own code.

Being able to parse something into a dict and then serialise it back to the same thing is a bit easier. Not a huge advantage, though.

Open source projects? Maybe less so.

But there are definitely companies that use Bazel in a major way.

At least in British English usage, there is no distinction between Jail, Gaol, and Prison other than at least one of these is a dated word.

I believe only the US has a strong distinction between Prison and Jail.

Part 4c (this is quite a long series) goes into some detail here. https://acoup.blog/2025/09/12/collections-life-work-death-an...

My own interpretation is that it's difficult to precisely compare how peasants were exploited to modern taxation regimes in the developed world. Perhaps more as an unfavorable relationship with the only employer in town?

This may be because the 'headshot' multiplier is lower than the regular multiplier (1x vs 2x) for the prod and baton. For most weapons the headshot multiplier is 8x (or something).

So torso hits from behind are the way to go.

Those are not the same; one is a bit less than an hour, another is 3 and a half days.

A microcentury is 100 nanoyears if you prefer that.

It's actually 100 microyears!

Erm, yes. Yes it is...

Set comprehensions are normal in mathematics and, barring very long complex ones, I find them the easiest to parse because they are so natural.

They're just a tad more verbose in Python than mathematics because it uses words like 'for' and 'in' instead of symbols.

I highly doubt market makers are in the business of betting against retail traders.

I suspect they're in the business of collecting the spread on lots of small trades that they can assume are largely random.

What you described is how you bet against retail traders. The bet is that they have no edge so it’s safe to run tight spreads and nice pure market making algos that assume random behavior at volume.

Feels weird to call it a 'bet against' when the other side can (potentially) benefit from the tighter spread you offer.

But yes, the market maker doesn't run the risk of trading with someone with knowledge and a lot of capital to apply it.

Yeah, I don’t like the phrase either, but market making in these pools is quite literally taking the other side of their trades.

Your perception of Fencing and HEMA aside; I can promise you that if HEMA was an Olympic sport:

* The same money problems that Fencing athletes face would apply to potential 'HEMA athletes'.

* You would hate what HEMA becomes because now it's a sport that people try to win at, with the 'realism' aspect all but destroyed.

Yeah there still wouldn't be much money in it, it's pretty niche, and would probably only grow the viewership slightly. But at least it wouldn't be dumb.

I routinely read HN on my phone. I'm doing it right now.

I think I've only accidentally flagged about posts by mistake...