For those, who do not know what the Gemini protocol is, think of it as a modern, light-weight HTTP alternative without CSS or JavaScript. In layman term, you could see it as Web 1.0 reinvented. It uses GemText instead of HTML. For folks who want to try it out, you can either install a Gemini extension for your HTTPs browser (which kinda defeats the purpose, as modern browsers are heavy), or download a dedicated Gemini browser like Lagrange. Here's a few sites you can access in Gemini.
Personally, I love it, although I miss a few stuff, like for example, multimedia, streaming and stuff like that. The memory foorprint is very low, and pages are super-fast.
Why?
What problem does this solve over simple HTML/CSS pages?
Outside of a very specific niche I can't see how anyone would choose this over normal HTML and HTTP/HTTPS, you'd need to run a new Gemini specific server to host Gemini specific files, created by Gemini specific softwares or Gemini specific developers, files that can only be read with a Gemini specific client.
This won't happen outside systems with highly specialized requirenments.
The advantage is that it's an obligate web 1.0 (-ish) experience. You aren't clicking a link on a Gemini site that is going to take you anywhere crazy. There's no tracking pixels and embedded content to get in the way.
It's possible to attempt this by just following web 1.0 standards on your w3 site, and only linking to sites that do the same, and so on, but eventually there's going to be a like button or an embedded video or something that ruins the experience. The web is messy.
Smaller spaces with constraints can be a lot of fun. Working within those constraints can breed innovation.
Sure, but untill web browsers support the protocol natively, it will never take off
This completely misses the point.
Why would you not want a broader adoption of the system?