Oyak posted:

Well, every Veterans Administration hospital in the US still makes its employees use a program with a command line interface in order to request vacation time or sick days. This means learning to program a few lines of code if you want time off. God Bless America!

Casimir Radon posted:

When did you become Dr. Quarex?

woodch posted:

(Maelstrom)
Well, there goes my weekend. Thanks!

laserghost posted:

EVIL Gibson posted:

Sometimes I compile linux open source or kernels just because I think my CPU isn't working hard enough and I want to watch it burn.

Police Automaton posted:

Run Seti@Home or something like that (and then wonder why it's so warm in the room [don't get brain damage] and about your power bill)

quote:

spending millions on modernizing something to then resemble the Windows 8 UI and then have more bugs

quote:

I bought an IBM PS/2E

quote:

DOM Module

Buttcoin purse posted:

???

klafbang posted:

Unicode is a mess. It's better than the good ol' code pages, but ho boy is the video wrong about it solving all issues. Aside from the unicode domains that for a short time was every phishers dream, it's also a coding nightmare: https://eev.ee/blog/2015/09/12/dark-corners-of-unicode/

Police Automaton posted:

I'm more of an ascii type of guy

Jerry Cotton posted:

Is this you?

code:

     #####
    #### _\_  ________
    ##=-[.].]| \      \
    #(    _\ |  |------|
     #   __| |  ||||||||
      \  _/  |  ||||||||
   .--'--'-. |  | ____ |
  / __      `|__|[o__o]|
_(____nm_______ /____\____

klafbang posted:

While UTF8 is incredibly clever for many things, it should just die horribly and be replaced by UCS4 little endian.

Unctuous Cretin posted:

This and the ongoing adventures of John McAfee (https://en.wikipedia.org/wiki/John_McAfee) are my favorite Where Are They Now? of crazy tech people to check in on from time to time.

Heath posted:

Just quoting this for the new page

klafbang posted:

Merging of the two standards is also the reason we have both the UCS and UTF encodings (obviously in both little and big endian versions). While UTF8 is incredibly clever for many things, it should just die horribly and be replaced by UCS4 little endian.

FilthyImp posted:

Computer Relics - Before the Age of Autism we were just Nerds.


Somehow typing that out made me remember how much fun it was to Telnet into the LA Public Library catalog system to see if the book I wanted was at my local branch. Sweet sweet command line interfaces.

Regular Nintendo posted:

Wtf is a phlog

Kaizoku posted:

goPHer Log, as opposed to weblog

because this isnt the web its the gopherspace

WebDog posted:

Regular Nintendo posted:

Wtf is a phlog

kilogram posted:

Man, I feel kinda sorry for this old man, it's like we're disappointing him every time we open up a web page

But I'm kinda confused as to what makes this significantly different from HTML with links except for being ten times harder to read

BOOTY-ADE posted:

It's what happens to taggers in Singapore

quote:

The computer world is not just technicality and razzle-dazzle. It is a continual war over software politics and paradigms. With ideas which are still radical, WE FIGHT ON.

We expect vindication, the last laugh, and a redefinition of electronic literature-- and at the least, that our format will join the others as a standard that does not imitate paper.



FUNDAMENTAL CONCEPTS

A new kind of writing-- PARALLEL PAGES, VISIBLY CONNECTED.
Markup is not embedded; links are separate, applied to clean permanized content. Thus all links, by everyone, are to original data and its shared addresss space.
Sale of clean content to pay artists and authors, with a copyright doctrine to match, permitting mashup with author micropayment.

quote:

Conventional electronic documents were designed in the 1970s by well-funded conventional thinkers at Xerox PARC, who asked, "How can we imitate paper?" The result is today's electronic document-- Microsoft Word format and the printout format PDF. They imitate paper and emphasize appearance and fonts.

But much earlier, in 1960, the Xanadu project started with a completely different idea: since interactive screens are coming (who else knew?), we asked a different question: How can we IMPROVE on paper?

We foresaw a new screen literature of parallel, interconnected documents.


Above is a picture from a paper we published in 1972.*

* Theodor H. Nelson, “As We Will Think." Proceedings of Online 72 Conference, Bruanel University, Uxbridge, England, 1972.

A closeup below, from that same paper, shows visible interconnection between two screen windows. Thus an author may show the exact connection between writings on different pages.

The visible connection becomes a structural part of the writing, as fundamental as a paragraph or heading.

Note that this provides a generalized way of representing parallel documents and their precise connections-- such as the Talmud, legal commentary, or the comments on the long poem in Nabokov's "Pale Fire" by his fictitious literary critic, Charles Kinbote..



(Since this was in 1972, these pictures were of a mockup, not a functioning system. There were no office computers then.)


IMPOSSIBLE ON MAC, WINDOWS AND LINUX

When Xerox PARC released their first computer with a "modern" interface, the Alto, they did not offer visible connections between windows, though such connections would have been possible.* But when the Alto was imitated by the Apple Macintosh and then Microsoft Windows, such connections became impossible. And needless to say, the further imitations of these windows on Linux don't make such connections possible either.

* Alan Kay, personal communication.
IMPOSSIBLE ON THE WEB
The World Wide Web took part of our concept, the "hyperlink" (we called it the jump-link, since you can't see where you're going), and left out the visible interconnections (which would allow you to see where you'e going). In his 1989 proposal for the World Wide Web, Tim Berners-Lee said:

There are few products which take Ted Nelson's idea of a wide "docuverse" literally by allowing links between nodes in different databases. In order to do this, some standardisation would be necessary.*
* http://www.w3.org/History/1989/proposal.html
The standardization he allowed in his document format only allowed jump-links, with no visible bridges between them.

A PARALLEL LITERATURE OF INTERCONNECTED DOCUMENTS

We have continued to pursue these ideas, with no funding and no support, and despite ridicule and attack. Here follow screen shots of some of our functioning prototypes.

Two Versions of the Declaration of Independence, by Ka-Ping Yee (1999). Yee's graphical interface, Pyxi, connects directly to the Xanadu Green server. Work on Xanadu Green, a server designed for parallel documents, has been continuing under Roger Gregory.


CosmicBook™, Nelson with Ian Heath (2003)-- Windows only. Heath's method bypasses Microsoft's windowing system, creating an overlay for the entire screen on which he draws the connection-lines.


XanaduSpace™, Nelson with Robert Adamson Smith (2007)-- Windows only, unchangeable contents. Smith's system represents all pages as slabs within a 3D space, moving between 3D positions on user command. Highlighted sections of text are separate 3D objects ("tetroids", named after a shape in the game of Tetris) connected by beams. Pages, tetroids and beams are all objects sworfing (swooping and/or morphing) together. The system was intended in principle to fetch contents from the net, but did not reach that stage.

OpenXanadu™, Nelson with Nicholas Levin, 2014 (various mechanisms inside the web browser). Using cascading style sheets and other browser methods, Levin scrolls the various text sources (note that the entire Old Testament is in the column on the left) and their connecting bridges to the central article. Only the origins of quotations (transclusions) are shown; xanalinks could be added, but we do not consider this approach worth pursuing. This prototype actually does fetch contents from the net, should users want to show their own data. However, we have no time to document it.


With our limited resources we can only go slowly, unlike today's Red Bull-fueled young teams.
Though our ideas have been pushed out of the way, they are still good. We expect vindication, and eventual acceptance as a fundamental document type and format that will stand tall against the paper imitations.

No one else is pursuing this approach; everyone is hypnotized by the Web browser, which is basically crippled for these purposes.


PAGE AND DOCUMENT LOGIC

What we need is not just visible connection, but a rational and extensible structure behind it-- a way of grouping parallel documents and managing their visible interconnections. That is defined bythe data structure, which we will publish when ready.

We fight on.