"One of NLS's most revolutionary features, the Journal, was developed in 1970 by Australian computer engineer David A. Evans as part of his doctoral thesis.[6] The Journal was a primitive hypertext-based groupware program which can be seen as a predecessor (if not the direct ancestor) of all contemporary server software that supports collaborative document creation (like wikis). It was used by ARC members to discuss, debate, and refine concepts in the same way that wikis are being used today."
A wiki in 1970. I feel like we've forgotten so much.
Interesting post, but could use a [1995] in the title.
For those that are interested in some radical proposals to try and move things forward, I recommend having a look at the work that's being done at the Viewpoints Research Institute (with among others, Alan Kay):
[edit: Sadly, as far as I've been able to figure out, the kscript and ksworld software mentioned in the last few reports, isn't available anywhere. But I did discover a port of squeak to the lively (js) kernel system:
Can someone recommend a book that would talk about all this stuff in more detail? By all this stuff, I guess I mean all the dreams about personal computing that never came to fruition. Ideally with little fluff and a lot of technical detail.
It was the most radical computer dream of the hacker era. Ted Nelson's Xanadu project was supposed to be the universal, democratic hypertext library that would help human life evolve into an entirely new form. Instead, it sucked Nelson and his intrepid band of true believers into what became the longest-running vaporware project in the history of computing - a 30-year saga of rabid prototyping and heart-slashing despair. The amazing epic tragedy.
Vaporware might be too strong a description, but an "amazing epic tragedy" that chewed up three decades of very smart people's effort is correct, from what I've heard from a friend who looked at what they produced.
Besides taking way way too long, as not uncommon in stealth mode projects they failed make sure their system was end to end usable. My fried said trying to make a browser/viewer/whatever for Xanadu required using an API that was impossibly complicated, and while I don't remember the specifics now, he cited them in detail.
There used to be some kind of implementation (a mock-up, really) on-line with a text one could zoom out and in and surf from "things" to "things" but I can't find it anymore.
I have enough knowledge of this material to write two books on this subject. I'd love to write it, I maybe have three chapters written already. With some effort we could even include some demo's of these systems (see my hn profile for my email).
It is so important that something like this happens. The mental image of all the knowledge workers of the world riding tricycles because a real bike is "too difficult", is absolutely perfect.
I got to meet Ted Nelson a couple of years ago when he gave a talk at a designer/developer conference in Brookyln [0]. He was talking about hypermedia document transclusion, and directed graph mapping of hyperlinked documents. I was one of the ~5 people in the room who got really excited. The other 200 or so... well, let's say they didn't get it.
A lot of the things these guys talk about are really, really abstract concepts, and it takes a special kind of creativity to realize what a big deal they could be. Since most people don't have that (and since it's even rarer among people who market products)... we get repackaged word processors.
> "Education is a process of ruining subjects for you and the last subject to be ruined determines your profession"
that makes a lot of sense to me, and partly explains why I'm in IT / computers now
Being unemployed for most of my life, that quote sounds way out of touch.
One of the best ways to ruin a subject is to tell someone who has been studying very hard at said subject and also has made spectacular progress, that they should stick to what they are capable of - and then tell them they are just wasting their time and should stick to sweeping streets and cleaning shit stained toilets. It's even more of an insult to receive criticisms in writing, with poor spelling and grammar.
If, unlike myself, you have a full time job and don't get treated like a retard, rejoice.
It's striking how all those GUI discussions and moaning about Microsft seems totally irrelevant now. I remember those days well and I can't recall anybody envisioning the way we interact with information via mobile devices now. Interestingly, I hear a lot less complaining about the state of computing now although there's plenty of complaining about what mobility has done to human interaction in general.
mobile UI isn't very powerful, compared to Kay & Engelbart's applications either, though. They were focused on quick and powerful editing of content - mobile apps hardly allow you to edit anything at all.
One gem: "So the way I hope that it will work for the Web protocols and the WWW standards which I hope will be able to evolve from their kludgy current state towards that beautiful golden dream is that in any case where you lay down a standard, you also allow there to a second and you show a path whereby is a third one comes up that is better you can move in that direction on the heels of the first, keeping it honest and you have a hook in it to be able to hook it all together later on." (Tim Berners-Lee)
After Doug Engelbart died I poked around and found a clone of his Augment software. It's a Windows 3.0 application, this company still uses it and sells copies for $150:
Comes with a decent manual. I've played around with it a bit but not too much so far.
It's limited to 8-character filenames, and seems more mouse-dependent than I prefer, though maybe I just don't know all the tricks. These days, emacs with org-mode and evil-mode might be a more productive implementation of similar ideas. But it's still pretty interesting. Curiously, one thing that people have criticized as unintuitive is its modal verb-noun command structure, which as a Vim user I find completely natural.
How well this software really captures NLS, I can't say.
I would think that a piece of software which intends to have a markedly different user-interaction with the computer would show, in concrete terms, what that interaction looks like - through the technology of photographics or videography. Especially when wanting $150 for it. I guess I ask too much.
There was something which worked well enough to produce the 2006 screencast http://vimeo.com/81336768 . But the project http://hyperscope.org/ seems to be abandoned and the download page is missing.
"One of NLS's most revolutionary features, the Journal, was developed in 1970 by Australian computer engineer David A. Evans as part of his doctoral thesis.[6] The Journal was a primitive hypertext-based groupware program which can be seen as a predecessor (if not the direct ancestor) of all contemporary server software that supports collaborative document creation (like wikis). It was used by ARC members to discuss, debate, and refine concepts in the same way that wikis are being used today."
A wiki in 1970. I feel like we've forgotten so much.