Slow is relative, but you might want to check out Garnet [0] for ideas. Previous discussion at [1], current compatibility at [2].

[0] https://www.microsoft.com/en-us/research/blog/introducing-ga...

[1] https://news.ycombinator.com/item?id=39752504

[2] https://microsoft.github.io/garnet/docs/commands/api-compati...

Yes.

1. It is single-threaded, which severely limits throughput for a single instance.

2. All communication must go over a socket, which severely impacts latency for use cases where it could otherwise run in-process.

What is the better alternative?

Do checkout https://www.dragonflydb.io . It's also mentioned in the review!

I'm so tired of these Web pages that look like iPhone screens.

depends on your use case. also, for most redis is fast enough which is why it is wildly popular

I wish there was more context around that statement in his post.

Redis while not having some of the features he mentions in [1] (i.e. SQL), when used for what it excels at is usually not considered "slow".

As an in-memory data structure server, a common use case is to use it for where some operations in a typical RDBMS are slow.

[1] https://youtu.be/fZbwD1gzjLk?t=2018