-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy path2015-11-19_This-is-not--no-UI----it-s--text-based-UI---c4e5991b7edb.html
72 lines (72 loc) · 5.32 KB
/
2015-11-19_This-is-not--no-UI----it-s--text-based-UI---c4e5991b7edb.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
<!DOCTYPE html><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><title>This is not ‘no UI’ — it’s ‘text-based UI’.</title><style>
* {
font-family: Georgia, Cambria, "Times New Roman", Times, serif;
}
html, body {
margin: 0;
padding: 0;
}
h1 {
font-size: 50px;
margin-bottom: 17px;
color: #333;
}
h2 {
font-size: 24px;
line-height: 1.6;
margin: 30px 0 0 0;
margin-bottom: 18px;
margin-top: 33px;
color: #333;
}
h3 {
font-size: 30px;
margin: 10px 0 20px 0;
color: #333;
}
header {
width: 640px;
margin: auto;
}
section {
width: 640px;
margin: auto;
}
section p {
margin-bottom: 27px;
font-size: 20px;
line-height: 1.6;
color: #333;
}
section img {
max-width: 640px;
}
footer {
padding: 0 20px;
margin: 50px 0;
text-align: center;
font-size: 12px;
}
.aspectRatioPlaceholder {
max-width: auto !important;
max-height: auto !important;
}
.aspectRatioPlaceholder-fill {
padding-bottom: 0 !important;
}
header,
section[data-field=subtitle],
section[data-field=description] {
display: none;
}
</style></head><body><article class="h-entry">
<header>
<h1 class="p-name">This is not ‘no UI’ — it’s ‘text-based UI’.</h1>
</header>
<section data-field="subtitle" class="p-summary">
However, this doesn’t mean that traditional UI concerns are irrelevant to text-based UIs, or that there are no special UI concerns to…
</section>
<section data-field="body" class="e-content">
<section name="aecf" class="section section--body section--first section--last"><div class="section-divider"><hr class="section-divider"></div><div class="section-content"><div class="section-inner sectionLayout--insetColumn"><p name="f16f" id="f16f" class="graf graf--p graf--leading">This is not ‘no UI’ — it’s ‘text-based UI’. Human written language is a set of technologies that have been under active, heavy development for four thousand years — compared to GUIs, which were under active and heavy development at Xerox PARC for about five years and have barely changed since. I agree that text-based UIs are the future — the competent ones among us never switched away from them in the first place, because they have features and nuances that GUIs would not be able to compete with even had they been truly under active development for the forty years of their existence.</p><p name="3d8e" id="3d8e" class="graf graf--p graf-after--p">However, this doesn’t mean that traditional UI concerns are irrelevant to text-based UIs, or that there are no special UI concerns to consider. It’s very easy to screw up a text-based UI — compare the MS-DOS command shell with a modern UNIX shell like zsh, and the vast gulfs of difference are obvious; even so, MS-DOS is by far not the least competent text-based UI in existence.</p><p name="ff16" id="ff16" class="graf graf--p graf-after--p graf--trailing">Conversational interfaces, by catering almost exclusively to new users and eschewing efficiency, nuance, and a rich feature set in favor of a shallow learning curve, are almost universally unusable for genuinely complex real-world tasks and gain their popularity from the novelty element of a computer behaving like a person. A well-designed conversational interface would eventually, in the hands of a habitual user who has become comfortable with it, resemble a traditional command-line interface: it would efficiently execute unambiguous and richly expressive queries while making use of shortened mnemonic forms of those queries. However, the novelty of a conversational interface to a new user depends upon a cynical assumption about that user’s willingness and ability to learn new skills: the conversational interface must accommodate a user who knows nothing and has made no effort to learn, and to interpret ambiguous requests as their simplest possible evaluation — to complain about the ambiguity or request it to be resolved would be to suggest the user learn a <em class="markup--em markup--p-em">programming language</em> and to interpret any resolution other than the simplest would be to suggest that the system is either unreliable (like a human) or sensitive to subtle details (like a programming language). Assuming users are stupid and unwilling to learn how to perform simple tasks is part of good UI design in GUIs, but it works against you even moreso in text-based interfaces; conversational interfaces that do not take advantages of UI advances in command line interface design can never become any more than toys.</p></div></div></section>
</section>
<footer><p>By <a href="https://medium.com/@enkiv2" class="p-author h-card">John Ohno</a> on <a href="https://medium.com/p/c4e5991b7edb"><time class="dt-published" datetime="2015-11-19T14:06:13.109Z">November 19, 2015</time></a>.</p><p><a href="https://medium.com/@enkiv2/this-is-not-no-ui-it-s-text-based-ui-c4e5991b7edb" class="p-canonical">Canonical link</a></p><p>Exported from <a href="https://medium.com">Medium</a> on January 21, 2025.</p></footer></article></body></html>