|
|
|
|
|
|
by latch
1611 days ago
|
|
|
The post is a broad, and IMO, valid criticism. Though I'm not sure having a different protocol is a _huge_ problem. If Gemini ever got popular both backends and clients would add support. I think the real issue, and the OP touches on it, is the text/gemini format. There's a ton of content that would enrich Gemini (and that fits Gemini's mission) but that simply isn't usable in text/gemini. Specifically, I'm talking about inline-links (though that isn't the only issue). I wrote a server in elixir, and tried to convert Wikiversity's Introduction to Programming (1) both manually and automatically. I found the output unusable and couldn't come up with a case where I'd ever prefer/recommend it. (1) https://en.wikiversity.org/wiki/Introduction_to_Programming |
|
|
That's kind of what I've concluded too. I like the mission of gemini (and I believe the web is fundamentally broken and unrepairable), but I do feel like text/gemini flings way too far in the opposite direction. It's not a new pattern, I see this all the time: thing X is too complex and bloated and user-hostile, let's make a suckless thing Y. Y is minimalistic to a fault.
Making something that's too minimalistic or too complex is easy. Finding the right balance and making something that is small and simple yet still capable of covering wide use scenarios is an engineering challenge..
Since I agree with gemini's mission, I'm not going to complain too much about it. It's not exactly what I want, but if it encourages people to write content and deliver it in a form that is guaranteed not to have web's problems, I'm all for it, because I do stand to benefit from it.