Visual navigation possibilities with GopherVR for Macintosh and Unix (fwd)

"C.K.Work" <> Tue, 04 April 1995 16:22 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa04002; 4 Apr 95 12:22 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa03997; 4 Apr 95 12:21 EDT
Received: from by CNRI.Reston.VA.US id aa10410; 4 Apr 95 12:22 EDT
Received: by id <> (8.6.11/ for; Tue, 4 Apr 1995 16:42:39 +0100
Received: from by id <> (8.6.11/ for with SMTP; Tue, 4 Apr 1995 16:42:33 +0100
Received: from localhost by (5.64/1.34-032891-Polytechnic University) id AA21586; Tue, 4 Apr 95 11:27:16 -0400
Date: Tue, 4 Apr 95 11:27:16 -0400
Message-Id: <>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "C.K.Work" <>
Subject: Visual navigation possibilities with GopherVR for Macintosh and Unix (fwd)
X-Listserver-Version: 6.0 -- UNIX ListServer by Anastasios Kotsikonas
X-Comment: Polytechnic U. redistribution of
Content-Length: 1802
Content-Type: text
X-Mailer: ELM [version 2.4 PL23]
Reply-To: "C.K.Work" <>
Precedence: list

Jill Foster wrote ...
> I know many of you have moved to WWW - but gopher and WWW keep
> leap-frogging each other. This announcement of GopherVR for Macintosh and
> Unix *enables* possibilities for visual navigation through the information
> space. There was a guy from BT at last year's user support workshop that
> talked about the BT (British Telecom for the non-UK members) research
> dept's work on visual navigation as an alternative method of displaying
> relationships between information.

Speaking from a site which has just committed to WWW (more or less
bypassing Gopher) I'm intrigued to see that such effort is being put
into Gopher - the implicatation of the Jill's message is that gopher & WWW are 
alternate routes to the same end. Unless I'm misunderstanding things,
this is not the case. WWW as a technology surely offers much more than
Gopher can - both now, but perhaps more importantly in terms of scope
for development. At present Gopher space is effectively a subset of Web
space, and this will remain the case until Gopher clients can read html
(in which case won't they be Web clients?).

Granted, looking at the client end ONLY, it is possible that Gopher
clients may include features which make them easier/better/faster to
use, and for those with a serious investment in Gopher based services,
this is a good thing. But, if you were starting with a clean slate are
there any reasons to go down the gopher route rather than the Web route?

Everything I've seen would indicate that the only real future is with
Web - but I'm only too happy to be corrected on this! :)



Colin K. Work
Computing Services
University of Southampton

tel.  01703 593090 (direct line)