News for hackers. Stuff that matters.
Re:Lisp OS: what has been lost: Kent Pitman by joe_the_user on Sunday December 27, 2009 @03:15PM (#1017526)
It's (relatively) easy to write a GUI that puts all the information in the machine "at your finger tips".

What hard and requires GUI designers as well as programmers, is writing a GUI that puts the relevant information at the users finger tips in a way that's understandable, that users can easily take-in.

Relevant, relevant, relevant! Understandable, understandable, understandable!

These are just two words but implementing them is a hard, cross-discipline problem. What's telling is these consideration often don't even enter programmer's discussions about GUIs.

Re:Lisp OS: what has been lost: Kent Pitman by Hexstream on Sunday December 27, 2009 @06:59PM (#1017824)
"It's (relatively) easy to write a GUI that puts all the information in the machine "at your finger tips"."

I don't think so. In most cases the relevant information doesn't even have a formal representation (ex: it's "hidden" in turing-complete code) at the application level so it's literally impossible to get at this information unless you rewrite that application. What you need is support from the OS that lets you write "semantics-preserving" programs easily.

Re:Lisp OS: what has been lost: Kent Pitman by joe_the_user on Sunday December 27, 2009 @07:45PM (#1017874)
Wait, you said "relevant information"... Respectfully, let me point that original context of the quote should show I was contrasting merely displaying information with organizing it into some degree of relevance.
Re:Lisp OS: what has been lost: Kent Pitman by wglb on Sunday December 27, 2009 @04:49PM (#1017691)
Curiosity has the better of me: What other GUI puts all the information at your fingertips besides the one noted here?
Re:Lisp OS: what has been lost: Kent Pitman by blasdel on Monday December 28, 2009 @01:55AM (#1018251)
Any modern Unix Shell -- just because they're character-addressed doesn't make them not a GUI -- they have interactive screen-level features using curses. If it wouldn't work via teletype, it's a GUI.

All of the state information is available via the filesystems (including procfs/sysfs) and environment variables -- on a modern system you don't even need to exec.

Re:Lisp OS: what has been lost: Kent Pitman by asciilifeform on Monday December 28, 2009 @07:42AM (#1018495)
> Any modern Unix Shell

Can I stop a Unix kernel, view + modify the line of source corresponding exactly to where it halted, and resume?

Re:Lisp OS: what has been lost: Kent Pitman by wglb on Monday December 28, 2009 @11:01AM (#1018728)
By "all the information at your fingertips" i meant the things that Genera can do. So you look in /proc/core and find the bytes, but it won't show you the source that produced that, or even the program. The Unix Shell and curses doesn't cut it.
Re:Lisp OS: what has been lost: Kent Pitman by j_baker on Monday December 28, 2009 @11:06AM (#1018744)
Take a look at this stackoverflow question: http://stackoverflow.com/questions/238177/worst-ui-youve-eve...

Notice something? Poorly designed UIs tend to cram every bit of information as densely as they can.

Re:Lisp OS: what has been lost: Kent Pitman by wglb on Monday December 28, 2009 @12:21PM (#1018890)
Are you saying that the Genera interface is badly designed?
Re:Lisp OS: what has been lost: Kent Pitman by joe_the_user on Monday December 28, 2009 @02:53PM (#1019234)
I was only saying that in discussion of Genera, the only argument for Genera's superiority was how much information it presented. I've never Genera's interface but the criteria of amount of information presented seemed a bit off.
Re:Lisp OS: what has been lost: Kent Pitman by joe_the_user on Sunday December 27, 2009 @07:32PM (#1017863)
Regedit and bsh