Gopher purism
==============
2021-07-14

Recently I've read article[1], and one of points that
it trying to say is that people trying to use gopher
as stripped-down web instead of it "organic" usage as
hierarchical file system with some extra features (or
network of interconnected menus and files).
Therefore gopher will always fail as "real" replacement
of web, conceptually and technically. Using gopher
for web concepts/content formats is similar (but even
more useless) to using browser runtime for desktop
applications (hello, HTA and ActiveDesktop).

Modern gopher resembles weird mix of cargo cult
combined with anti-web resentiment. Non-spec i selector
is a marker of this approach. Its usage can be valid,
but most of times it is abused, same to ASCII-art -
it's kinda retro and not like web images so let's
put it in thing that really should serve as directory
index and don't consider it visual garbage. And those
people say "we're keeping our net nonsense-free, not
like interwebz chaos".

So I decided to create client that will behave
"correctly" (in some sense) and won't display
information selectors at all, and also create
section in my gopherhole that will follow
this concept of "pure" Gopher.

[1] gopher://gopher.somnolescent.net/0/maris-essays/why-gopher-will-fail.md