Jef Raskin's The Humane Interface

Tasks become habits. No modes, only chording. Only one way to do things. No warning screens, everything is undoable.

Reliable. Everything saves automatically. Content resistant to crashes.

Efficient and simple. Tasks don't take time to perform. Tasks don't take time to learn.

No icons. Purely text.

Zooming UI. No filenames.

No applications. Only commands.

Well tested.

Visually attractive.

final destination

>>1

Reliable. Everything saves automatically. Content resistant to crashes.

Welcome to Mac OSX!

You forgot the last one, faggot:

Doesn't exist, and never will.

>>4
The only thing that doesn't exist and never will is that of you achieving something.

>>5
fuck you you little queer faggot.

Tasks become habits

i don't get it

No modes, only chording. Only one way to do things.

BSx2

Purely text.
Zooming UI.

wut

Purely text.
Visually attractive.

wut
.
agree on evertything else.

How does no filenames work with text only?

>>8

An end to directories and file names - "the content of a text file is its own best name." Every document should be identifiable by its contents, so there should not be need for directories or names for user-generated documents; Raskin argues that these names tend to be cryptic and make files difficult to find afterwards.

>>7
People develop habits. Habits are good because then you can focus on other tasks. Thus, asking for confirmation is bad because users will develop a habit of confirming the command, or the interface will be obnoxious to use. Thus, commands must be undoable. Furthermore, adaptive user interfaces are bad, if the adaptation interferes with habits formed.

If there is only one way of doing things, then people develop habits and feel secure and in control. If there are too many choices, it is difficult to teach, and difficult to use because you have to decide how you will do something.

>>7
What is ``BSx2''?

>>10
Not everybody is ``people'' and I will not create interfaces catering to retards.

>>10
I don't necessarily entirely agree with everything in >>1 but I really like the universal "undo" idea as a replacement for confirmation dialog galore.

>>9
So I have to run grep everytime I want a specific file? What about images, video or some arbitrary data file?

>>13
I still want to use file names myself, but you could label the file with meta data. And this data could be used for search.

>>14
retarded

>>1
I've loved this concept ever since I read about it ten years ago. I've been meaning to write a free software implementation for years but never dedicated any time to it. One day, I'll write a free humane interface with the principles taught by Raskin.

>>1
This post is one of the most retarded things I've read in months.

>>13
You could run a grep command if you wished but a simple search would probably suffice for 90% of what you want to find. If you want to search for non-text data, you can't search for it using text search. Instead, you can leave a label near that data and search for that label. For example, you could put a title to the video along with a short description of the contents of the video. You would think of keywords to search for and the system can create a search report that returns the links to the documents that the search program had found.

>>18

So it would be like that Mac file attribute crap, no thanks.

>>18
Nice job, you've just invented filenames. Shitass.

>>20
Filesystem filenames are limited in what characters to use and it is also mandatory to use a unique name for the file and directory path. This traditional organization system was how it worked in the past but there's no good reason why users should have to suffer through maintaining the tradition - the only reason for this is that it is traditional to work that way! Every document should be identifiable by its contents, so there should not be need for directories or names for user-generated documents. These names tend to be cryptic and make files difficult to find afterwards. Rather than impose requirements to set a filename and directory for the file, we should change the system so that users don't need to set any filename; the user can search directly for the content rather than abstracting the content through a cryptic filename.

>>19

Mac file attribute crap

I have no idea what this is.

>>22
http://en.wikipedia.org/wiki/Extended_file_attributes

>>23
so that's why iphone has no filenames and fucks everything up

>>24
False!

For anyone interested, there is an entire book which explains these concepts:
https://en.wikipedia.org/wiki/The_Humane_Interface
http://www.amazon.com/The-Humane-Interface-Directions-Interactive/dp/0201379376

The author implemented some of these ideas in a custom computer he sold in the late 70s called the Canon Cat which only worked with text (which may explain some of the apparent shortcomings of his ideas). Its filesystem was one continuous text document
with the only means of separation being the ability to insert horizontal separator lines. It had no applications, but allowed the user to implement new functions in Forth. The hardware was custom, so he designed the keyboard to have two "leap" buttons under the spacebar that a user could hold down with either thumb and start typing for a user-friendly incremental search.
https://en.wikipedia.org/wiki/Canon_Cat

He also attempted to make a modern implementation of his ideas, but he died of cancer before he could complete it. His team, which included his son, dropped the project shortly after he died and decided to work on making Firefox extensions instead.
https://en.wikipedia.org/wiki/Archy

Also, in case you didn't know, he was the creator of the Macintosh.

>>1

Reliable. Everything saves automatically. Content resistant to crashes.

How about using RAM only as a cache for persistent storage?
You wouldn't need stuff like config files, separate database files, save files, everything would automatically and transparently be persistend. Hell, you could keep every emacs buffer open forever because it wouldn't make a difference if you closed them or not.

I'm sure it would be slower, and you'd need battery backed storage for it to work properly, but damn it's a cool idea.

No filenames.
No warning screens, everything is undoable.

What the fuck is this retarded shit and why is everyone praising this?

>>1-27,29-
Go eat a bag of nigger dicks.

>>28

no argument given

>>29
Who are you quoting, nigger dick eater?

My argument is: who the fuck wants anything to be undoable? I'm sure your retarded ass is now sorry for making the stupid mistake of quoting bullshit that hasn't been said, but guess what, you can't undo it.

>>30

implying I can't undo my naked selfi I accidentally uploaded to my facebook.

>>27
An alternative to that is having journaled apps and automatic file versioning. VMS does this to some extent.

>>30

who the fuck wants anything to be undoable?

who the fuck doesn't?

>>32
Why call programs ``apps''? You're supposedly a technologically mature person but you don't act like it.

>>31

implying I can't undo my naked selfi I accidentally uploaded to my facebook.

HOLY SHIT EPIC MEME /B/RO!!! XDDDd

>>32
Sounds like abstraction inversion.

>>34
Why constantly bitch about something as insignificant as people using the term "app"? You're supposedly a technologically mature person but you don't act like it.

>>34
I've been using the term “app” since the 1980's. They were called “killer apps”.

>>28,30
White racist pig.

>>39
Nigger.

>>40
Okay let's take this to /lounge/ you piece of shit.