[grive]

I would tend to agree.

This article conveniently designs its benchmark to be exactly when open addressing would work.

In almost all of the maps implementations I have used so far, chaining was necessary and intrusive linked lists were used.

An open-addressing scheme was however preferable (cuckoo) for a read-mostly map allowing concurrent reads and locked writes.

I would be more interested in an article exploring the compromises involved there, e.g. related to paying the cost of an additional indirection when accessing the value.

Another critic of this article I would add is the many tables throughout referencing different baselines. A single baseline would be much preferable, to keep a sense of scale for each change.