> and there is still nothing in the protocol that can not be done with HTTP.

This argument itself is using flawed reasoning. Gemini was purposely designed as a subset of HTTP rather than a superset, starting with a tough approximation of HTTP 0.9.

Of course everything that is supported in Gemini can also be implemented in HTTP.

The same arguments from that linked comment still apply and make sense to me but don't seem to hold water for you, so I won't rehash them.