3 ms·

There is no good reason to use gopher other than for nostalgic reasons.

• classichasclass 8y ago
  Gopher menus are quick to parse and interact with even on very constrained systems, and the protocol is very simple. Given some of the other responses in this thread, I don't think those things are simply "nostalgia." I think you could argue that gopher has few practical uses, and while (as a Gopher user) I don't personally agree, I think the position is defensible depending on what your use cases are. But Gopher is a good example of how a minimal protocol can still offer services of some reasonable basic functionality, and I think that's worth something more than reminiscence.
  • enneff 8y ago
    I love the Gopher protocol but there is no practical difference between a gopher service and a web server serving directory listings and files.
    • classichasclass 8y ago
      You're excluding gopher menus themselves, which can be customized and act as miniature documents, and search servers, which can take queries and offer basic interactivity.
    • JdeBP 8y ago
      A gopher menu does not have to be a directory listing.