Mercurial > docs > unix-phil
annotate unix-phil.ms @ 6:a6b837d822b7
rewrote ch02
| author | meillo@marmaro.de |
|---|---|
| date | Thu, 18 Feb 2010 11:24:36 +0100 |
| parents | 48f1f3465550 |
| children | 606f0ffca834 |
| rev | line source |
|---|---|
|
2
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
1 .\".if n .pl 1000i |
| 0 | 2 .de XX |
| 3 .pl 1v | |
| 4 .. | |
| 5 .em XX | |
| 1 | 6 .\".nr PI 0 |
| 7 .\".if t .nr PD .5v | |
| 8 .\".if n .nr PD 1v | |
| 0 | 9 .nr lu 0 |
| 10 .de CW | |
| 11 .nr PQ \\n(.f | |
| 12 .if t .ft CW | |
| 13 .ie \\$1 .if n .ul 999 | |
| 14 .el .if n .ul 1 | |
| 15 .if t .if !\\$1 \&\\$1\f\\n(PQ\\$2 | |
| 16 .if n .if \\n(.$=1 \&\\$1 | |
| 17 .if n .if \\n(.$>1 \&\\$1\c | |
| 18 .if n .if \\n(.$>1 \&\\$2 | |
| 19 .. | |
| 20 .ds [. \ [ | |
| 21 .ds .] ] | |
| 1 | 22 .\"---------------------------------------- |
| 0 | 23 .TL |
| 6 | 24 Why the Unix Philosophy still matters |
| 0 | 25 .AU |
| 26 markus schnalke <meillo@marmaro.de> | |
| 27 .AB | |
| 1 | 28 .ti \n(.iu |
|
2
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
29 This paper discusses the importance of the Unix Philosophy in software design. |
| 0 | 30 Today, few software designers are aware of these concepts, |
| 3 | 31 and thus most modern software is limited and does not make use of software leverage. |
| 0 | 32 Knowing and following the tenets of the Unix Philosophy makes software more valuable. |
| 33 .AE | |
| 34 | |
|
2
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
35 .if t .2C |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
36 |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
37 .FS |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
38 .ps -1 |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
39 This paper was prepared for the seminar ``Software Analysis'' at University Ulm. |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
40 Mentor was professor Schweiggert. 2010-02-05 |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
41 .br |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
42 You may get this document from my website |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
43 .CW \s-1http://marmaro.de/docs |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
44 .FE |
|
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
45 |
| 0 | 46 .NH 1 |
| 47 Introduction | |
| 48 .LP | |
| 49 Building a software is a process from an idea of the purpose of the software | |
| 3 | 50 to its release. |
| 0 | 51 No matter \fIhow\fP the process is run, two things are common: |
| 52 the initial idea and the release. | |
| 3 | 53 The process inbetween can be of any shape. |
| 54 The the maintainance work after the release is ignored for the moment. | |
| 1 | 55 .PP |
| 0 | 56 The process of building splits mainly in two parts: |
| 57 the planning of what and how to build, and implementing the plan by writing code. | |
| 3 | 58 This paper focuses on the planning part \(en the designing of the software. |
| 59 .PP | |
| 60 Software design is the plan of how the internals and externals of the software should look like, | |
| 61 based on the requirements. | |
| 62 This paper discusses the recommendations of the Unix Philosphy about software design. | |
| 63 .PP | |
| 64 The here discussed ideas can get applied by any development process. | |
| 65 The Unix Philosphy does recommend how the software development process should look like, | |
| 66 but this shall not be of matter here. | |
| 0 | 67 Similar, the question of how to write the code is out of focus. |
| 1 | 68 .PP |
| 3 | 69 The name ``Unix Philosophy'' was already mentioned several times, but it was not explained yet. |
| 1 | 70 The Unix Philosophy is the essence of how the Unix operating system and its toolchest was designed. |
| 3 | 71 It is no limited set of rules, but what people see to be common to typical Unix software. |
| 1 | 72 Several people stated their view on the Unix Philosophy. |
| 73 Best known are: | |
| 74 .IP \(bu | |
| 75 Doug McIlroy's summary: ``Write programs that do one thing and do it well.'' | |
| 76 .[ | |
| 77 %A M. D. McIlroy | |
| 78 %A E. N. Pinson | |
| 79 %A B. A. Taque | |
| 80 %T UNIX Time-Sharing System Forward | |
| 81 %J The Bell System Technical Journal | |
| 82 %D 1978 | |
| 83 %V 57 | |
| 84 %N 6 | |
| 85 %P 1902 | |
| 86 .] | |
| 87 .IP \(bu | |
| 88 Mike Gancarz' book ``The UNIX Philosophy''. | |
| 89 .[ | |
| 90 %A Mike Gancarz | |
| 91 %T The UNIX Philosophy | |
| 92 %D 1995 | |
| 93 %I Digital Press | |
| 94 .] | |
| 95 .IP \(bu | |
| 96 Eric S. Raymond's book ``The Art of UNIX Programming''. | |
| 97 .[ | |
| 98 %A Eric S. Raymond | |
| 99 %T The Art of UNIX Programming | |
| 100 %D 2003 | |
| 101 %I Addison-Wesley | |
|
2
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
102 %O .CW \s-1http://www.faqs.org/docs/artu/ |
| 1 | 103 .] |
| 0 | 104 .LP |
| 1 | 105 These different views on the Unix Philosophy have much in common. |
| 3 | 106 Especially, the main concepts are similar for all of them. |
| 1 | 107 But there are also points on which they differ. |
| 108 This only underlines what the Unix Philosophy is: | |
| 109 A retrospective view on the main concepts of Unix software; | |
| 110 especially those that were sucessful and unique to Unix. | |
| 6 | 111 .\" really? |
| 1 | 112 .PP |
| 113 Before we will have a look at concrete concepts, | |
| 114 we discuss why software design is important | |
| 115 and what problems bad design introduces. | |
| 0 | 116 |
| 117 | |
| 118 .NH 1 | |
| 6 | 119 Importance of software design in general |
| 0 | 120 .LP |
|
2
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
121 Why should we design software at all? |
| 6 | 122 It is general knowledge, that even a bad plan is better than no plan. |
| 123 Ignoring software design is programming without a plan. | |
| 124 This will lead pretty sure to horrible results. | |
| 125 .PP | |
| 126 The design of a software is its internal and external shape. | |
| 127 The design talked about here has nothing to do with visual appearance. | |
| 128 If we see a program as a car, then its color is of no matter. | |
| 129 Its design would be the car's size, its shape, the number and position of doors, | |
| 130 the ratio of passenger and cargo transport, and so forth. | |
|
2
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
131 .PP |
| 6 | 132 A software's design is about quality properties. |
| 133 Each of the cars may be able to drive from A to B, | |
| 134 but it depends on its properties whether it is a good car for passenger transport or not. | |
| 135 It also depends on its properties if it is a good choice for a rough mountain area. | |
| 136 .PP | |
| 137 Requirements to a software are twofold: functional and non-functional. | |
| 138 Functional requirements are easier to define and to verify. | |
| 139 They are directly the software's functions. | |
| 140 Functional requirements are the reason why software gets written. | |
| 141 Someone has a problem and needs a tool to solve it. | |
| 142 Being able to solve the problem is the main functional requirement. | |
| 143 It is the driving force behind all programming effort. | |
| 144 .PP | |
| 145 On the other hand, there are also non-functional requirements. | |
| 146 They are called \fIquality\fP requirements, too. | |
| 147 The quality of a software is about properties that are not directly related to | |
| 148 the software's basic functions. | |
| 149 Quality aspects are about the properties that are overlooked at first sight. | |
|
2
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
150 .PP |
| 6 | 151 Quality is of few matter when the software gets initially built, |
| 152 but it will be of matter in usage and maintainance of the software. | |
| 153 A short-sighted might see in developing a software mainly building something up. | |
| 154 Reality shows, that building the software the first time is only a small amount | |
| 155 of the overall work. | |
| 156 Bug fixing, extending, rebuiling of parts \(en short: maintainance work \(en | |
| 157 does soon take over the major part of the time spent on a software. | |
| 158 Not to forget the usage of the software. | |
| 159 These processes are highly influenced by the software's quality. | |
| 160 Thus, quality should never be neglected. | |
| 161 The problem is that you hardly ``stumble over'' bad quality during the first build, | |
| 162 but this is the time when you should care about good quality most. | |
| 163 .PP | |
| 164 Software design is not about the basic function of a software; | |
| 165 this requirement will get satisfied anyway, as it is the main driving force behind the development. | |
| 166 Software design is about quality aspects of the software. | |
| 167 Good design will lead to good quality, bad design to bad quality. | |
| 168 The primary functions of the software will be affected modestly by bad quality, | |
| 169 but good quality can provide a lot of additional gain from the software, | |
| 170 even at places where one never expected it. | |
|
2
fbd7baf6a61f
added content about sw design; some formating
meillo@marmaro.de
parents:
1
diff
changeset
|
171 .PP |
| 6 | 172 The ISO/IEC 9126-1 standard, part 1, |
| 173 .[ | |
| 174 %I International Organization for Standarization | |
| 175 %T ISO Standard 9126: Software Engineering \(en Product Quality, part 1 | |
| 176 %C Geneve | |
| 177 %D 2001 | |
| 178 .] | |
| 179 defines the quality model as consisting out of: | |
| 180 .IP \(bu | |
| 181 .I Functionality | |
| 182 (suitability, accuracy, inter\%operability, security) | |
| 183 .IP \(bu | |
| 184 .I Reliability | |
| 185 (maturity, fault tolerance, recoverability) | |
| 186 .IP \(bu | |
| 187 .I Usability | |
| 188 (understandability, learnability, operability, attractiveness) | |
| 189 .IP \(bu | |
| 190 .I Efficiency | |
| 191 (time behaviour, resource utilisation) | |
| 192 .IP \(bu | |
| 193 .I Maintainability | |
| 194 (analysability, changeability, stability, testability) | |
| 195 .IP \(bu | |
| 196 .I Portability | |
| 197 (adaptability, installability, co-existence, replaceability) | |
| 198 .LP | |
| 199 These goals are parts of a software's design. | |
| 200 Good design can give these properties to a software, | |
| 201 bad designed software will miss them. | |
| 0 | 202 |
| 203 | |
| 204 .NH 1 | |
| 205 The Unix Philosophy | |
| 4 | 206 .LP |
| 207 The origins of the Unix Philosophy were already introduced. | |
| 208 This chapter explains the philosophy and shows concrete examples of its application. | |
|
5
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
209 |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
210 .SH |
| 4 | 211 Examples |
| 0 | 212 .LP |
| 4 | 213 Following are some examples to demonstrate how applied Unix Philosophy feels like. |
| 214 Knowledge of using the Unix shell is assumed. | |
| 215 .PP | |
| 216 Counting the number of files in the current directory: | |
| 217 .DS | |
| 218 .CW | |
| 219 ls | wc -l | |
| 220 .DE | |
| 221 The | |
| 222 .CW ls | |
| 223 command lists all files in the current directory, one per line, | |
| 224 and | |
| 225 .CW "wc -l | |
| 226 counts how many lines they are. | |
| 227 .PP | |
| 228 Counting all files that do not contain ``foo'' in their name: | |
| 229 .DS | |
| 230 .CW | |
| 231 ls | grep -v foo | wc -l | |
| 232 .DE | |
| 233 Here, the list of files is filtered by | |
| 234 .CW grep | |
| 235 to remove all that contain ``foo''. | |
| 236 The rest is the same as in the previous example. | |
| 237 .PP | |
| 238 Finding the five largest entries in the current directory. | |
| 239 .DS | |
| 240 .CW | |
| 241 du -s * | sort -nr | sed 5q | |
| 242 .DE | |
| 243 .CW "du -s * | |
| 244 returns the recursively summed sizes of all files | |
| 245 -- no matter if they are regular files or directories. | |
| 246 .CW "sort -nr | |
| 247 sorts the list numerically in reverse order. | |
| 248 Finally, | |
| 249 .CW "sed 5q | |
| 250 quits after it has printed the fifth line. | |
| 251 .PP | |
| 252 The presented command lines are examples of what Unix people would use | |
| 253 to get the desired output. | |
| 254 There are also other ways to get the same output. | |
| 255 It's a user's decision which way to go. | |
|
5
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
256 |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
257 .SH |
| 4 | 258 Pipes |
| 0 | 259 .LP |
| 4 | 260 The examples show that a lot of tasks on a Unix system |
| 261 are accomplished by combining several small programs. | |
| 262 The connection between the single programs is denoted by the pipe operator `|'. | |
| 263 .PP | |
| 264 Pipes, and their extensive and easy use, are one of the great | |
| 265 achievements of the Unix system. | |
| 266 Pipes between programs have been possible in earlier operating systems, | |
| 267 but it has never been a so central part of the concept. | |
| 268 When, in the early seventies, Doug McIlroy introduced pipes for the | |
| 269 Unix system, | |
| 270 ``it was this concept and notation for linking several programs together | |
| 271 that transformed Unix from a basic file-sharing system to an entirely new way of computing.'' | |
| 272 .[ | |
| 273 %T Unix: An Oral History | |
|
5
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
274 %O .CW \s-1http://www.princeton.edu/~hos/frs122/unixhist/finalhis.htm |
| 4 | 275 .] |
| 276 .PP | |
| 277 Being able to specify pipelines in an easy way is, | |
| 278 however, not enough by itself. | |
|
5
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
279 It is only one half. |
| 4 | 280 The other is the design of the programs that are used in the pipeline. |
|
5
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
281 They have to be of an external shape that allows them to be be used in such a way. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
282 |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
283 .SH |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
284 Interface architecture |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
285 .LP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
286 Unix is, first of all, simple: Everything is a file. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
287 Files are sequences of bytes, without any special structure. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
288 Programs should be filters, which read a stream of bytes from ``standard input'' (stdin) |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
289 and write a stream of bytes to ``standard output'' (stdout). |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
290 .PP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
291 If our files \fIare\fP sequences of bytes, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
292 and our programs \fIare\fP filters on byte streams, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
293 then there is exactly one standardized interface. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
294 Thus it is possible to combine them in any desired way. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
295 .PP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
296 Even a handful of small programs will yield a large set of combinations, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
297 and thus a large set of different functions. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
298 This is leverage! |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
299 .PP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
300 If the programs are orthogonal to each other \(en the best case \(en |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
301 then the set of different functions is greatest. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
302 .PP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
303 Now, the Unix toolchest is a set of small programs that |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
304 are filters on byte streams. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
305 They are to a large extend unrelated in their function. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
306 Hence, the Unix toolchest provides a large set of functions |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
307 that can be accessed by combining the programs in the desired way. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
308 |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
309 .SH |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
310 Advantages of toolchests |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
311 .LP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
312 A toolchest is a set of tools. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
313 Instead of having one big tool for all tasks, one has many small tools, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
314 each for one task. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
315 Difficult tasks are solved by combining several of the small, simple tools. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
316 .PP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
317 It is easier and less error-prone to write small programs. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
318 It is also easier and less error-prone to write a large set of small programs, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
319 than to write one large program with all the functionality included. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
320 If the small programs are combinable, then they offer even a larger set |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
321 of functions than the single large program. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
322 Hence, one gets two advantages out of writing small, combinable programs. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
323 .PP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
324 There are two drawbacks of the toolchest approach. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
325 First, one simple, standardized, unidirectional Interface has to be sufficient. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
326 If one feels the need for more ``logic'' than a stream of bytes, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
327 then a different approach might be of need, or, more likely, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
328 he just did not came to a design where a stream of bytes is sufficient. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
329 The other drawback of a toolchest affects the users. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
330 A toolchest is often more difficult to use for novices. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
331 It is neccessary to become familiar with each of the tools, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
332 to be able to use the right one in a given situation. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
333 Additinally, one needs to combine the tools in a senseful way on its own. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
334 This is like a sharp knive \(en it is a powerful tool in the hand of a master, |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
335 but of no good value in the hand of an unskilled. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
336 .PP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
337 Luckily, the second drawback can be solved easily by adding wrappers around the single tools. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
338 Novice users do not need to learn several tools if a professional wraps |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
339 the single commands into a single script. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
340 Note that the wrapper script still calls the small tools; |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
341 the wrapper script is just like a skin around. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
342 No complexity is added this way. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
343 .PP |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
344 A wrapper script for finding the five largest entries in the current directory |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
345 could look like this: |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
346 .DS |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
347 .CW |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
348 #!/bin/sh |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
349 du -s * | sort -nr | sed 5q |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
350 .DE |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
351 The script itself is just a text file that calls the command line |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
352 a professional user would type in directly. |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
353 |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
354 |
|
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
355 |
| 4 | 356 |
| 357 | |
| 0 | 358 |
| 359 .NH 2 | |
|
5
48f1f3465550
new content about interfaces and toolchests
meillo@marmaro.de
parents:
4
diff
changeset
|
360 foo |
| 0 | 361 .LP |
| 362 standalone vs. tool chain | |
| 363 .LP | |
| 364 software leverage | |
| 365 .LP | |
| 366 possiblities | |
| 367 | |
| 368 .NH 2 | |
| 369 Results | |
| 370 .LP | |
| 371 The unix phil is an answer to the sw design question | |
| 372 .LP | |
| 373 tool chains empower the uses of sw | |
| 374 | |
| 375 .NH 1 | |
| 376 Case study: nmh | |
| 377 | |
| 378 .NH 2 | |
| 379 History | |
| 380 .LP | |
| 381 MH, nmh. | |
| 382 They are old. | |
| 383 | |
| 384 .NH 2 | |
| 385 Contrasts to similar sw | |
| 386 .LP | |
| 387 vs. Thunderbird, mutt, mailx, pine | |
| 388 .LP | |
| 389 flexibility, no redundancy, use the shell | |
| 390 | |
| 391 .NH 2 | |
| 392 Gains of the design | |
| 393 .LP | |
| 394 | |
| 395 .NH 2 | |
| 396 Problems | |
| 397 .LP | |
| 398 | |
| 399 .NH 1 | |
| 400 Case study: uzbl | |
| 401 | |
| 402 .NH 2 | |
| 403 History | |
| 404 .LP | |
| 405 uzbl is young | |
| 406 | |
| 407 .NH 2 | |
| 408 Contrasts to similar sw | |
| 409 .LP | |
| 410 like with nmh | |
| 411 .LP | |
| 412 addons, plugins, modules | |
| 413 | |
| 414 .NH 2 | |
| 415 Gains of the design | |
| 416 .LP | |
| 417 | |
| 418 .NH 2 | |
| 419 Problems | |
| 420 .LP | |
| 421 broken web | |
| 422 | |
| 423 .NH 1 | |
| 424 Final thoughts | |
| 425 | |
| 426 .NH 2 | |
| 427 Quick summary | |
| 428 .LP | |
| 429 good design | |
| 430 .LP | |
| 431 unix phil | |
| 432 .LP | |
| 433 case studies | |
| 434 | |
| 435 .NH 2 | |
| 436 Why people should choose | |
| 437 .LP | |
| 438 Make the right choice! | |
| 439 | |
| 440 .nr PI .5i | |
| 441 .rm ]< | |
| 442 .de ]< | |
| 443 .LP | |
| 444 .de FP | |
| 445 .IP \\\\$1. | |
| 446 \\.. | |
| 447 .rm FS FE | |
| 448 .. | |
| 449 .SH | |
| 450 References | |
| 451 .[ | |
| 452 $LIST$ | |
| 453 .] | |
| 454 .wh -1p |