TAOUP early translations: the version
[1] and the efforts of a tradition. Writing this book is that once you understand the traditional Unix engineering, master its design patterns will help you become better programmers and designers.
Cultures consist of people, and the traditional way to learn Unix culture is from other people and through the folklore, by osmosis. This book is not a substitute for person-to-person acculturation, but it can help accelerate the process by allowing you to tap the experience of others.
Composed by the culture, learning the habit of Unix culture is: from other people, from the legend, imperceptible to learn. The book not a substitute for direct human cultural heritage, but the book so that you can use the experience of others, so that they may accelerate the process.
[2].
To make this book more accessible to less technical readers, we invited some non-programmers to read it and identify terms that seemed both obscure and necessary to the flow of exposition. We also use footnotes for definitions of elementary terms that an experienced programmer is unlikely to need.
For less-technical readers, in order to make it easier to understand the book, we have invited a number of non-programmers reading this book, marking out those who seem obscure but is explained by the need to terms. We also use footnotes to define basic terms, experienced programmers may not need these definitions.
[3] (especially the "Road construction of the eternal", "Building Pattern Language"), I learned from the "Gang of Four" (the Gang of Four), as well as from Other members of the school they benefited greatly from where they told me that: a high-level discussion on how to use the software design Alexander thinking, to avoid ambiguity, no value general discussion. Introduction to Design Mode, interested readers should read "design mode: Reusable Object-Oriented Software Foundation" (Design Patterns: Elements of Reusable Object-Oriented Software) [GangOfFour].
The title of this book is, of course, a reference to Donald Knuth's The Art of Computer Programming. While not specifically associated with the Unix tradition, Knuth has been an influence on us all.
The book's title, of course, made reference to the Donald Knuth's "Art of Computer Programming." Although the Unix tradition, and there is no special relationship between Knuth or affect us all.
Editors with vision and imagination aren't as common as they should be. Mark Taub is one; he saw merit in a stalled project and skillfully nudged me into finishing it. Copy editors with a good ear for prose style and enough ability to improve writing that isn't like theirs are even less common, but Mary Lou Nohr makes that grade. Jerry Votta seized on my concept for the cover and made it look better than I had imagined. The whole crew at Prentice-Hall gets high marks for making the editorial and production process as painless as possible, and for cheerfully accommodating my control-freak tendencies not just over the text but deep into the details of the book's visual design, art, and marketing.
With foresight and imagination editors, and not as common as expected. Mark Taub is one of them; he has seen the value of the project was stalled, it is pushing to promote skill I completed it. This text editor - have paid writing style, and have sufficient capacity to improve their own writing style of the text - much less common, but Mary Lou Nohr is. Jerry Votta I grasped the idea of the cover, making the cover looks than I expected even better. I Prentice-Hall to the entire staff played high, they make editing and production process as smooth as possible, is happily accepted my control paranoid trend, and this is not only to control the text, but also to the in-depth design books , illustrations and marketing trends control.
The first part of the background
[4]. Unix has also experienced a number of similar change.
—
<author> KenThompson </ author>
At least one of Unix's central technologies - the C language - has been widely naturalized elsewhere. Indeed it is now hard to imagine doing software engineering without C as a ubiquitous common language of systems programming. Unix also introduced both the now-ubiquitous tree - shaped file namespace with directory nodes and the pipeline for connecting programs.
At the very least, the core technology of Unix - C language - has been widely transplantation. In fact, it is difficult to imagine such software engineering, it is not done by the C programming system universal, common language. Unix also introduced with the now ubiquitous in the directory tree node documents, the introduction of the pipeline connecting the technical procedures.
Unix's durability and adaptability have been nothing short of astonishing. Other technologies have come and gone like mayflies. Machines have increased a thousandfold in power, languages have mutated, the industry practice has gone through multiple revolutions - and Unix hangs in there, still producing , still paying the bills, and still commanding loyalty from many of the best and brightest software technologists on the planet.
Unix-lasting and adaptation, let us always amazing. Like other technologies like mayflies come again returned to the. Machine's performance has been upgraded on the thousands of times, language variation in the industrial practice has also experienced a number of revolutionary - Unix still stands there, still functioning of the production, is also dealing with bills, still had many of the planet the best most intelligent software technology experts loyal support.
One of the many consequences of the exponential power-versus-time curve in computing, and the corresponding pace of software development, is that 50 percent of what one knows becomes obsolete over every 18 months. Unix does not abolish this phenomenon, but does do a good job of containing it. There'sa bedrock of unchanging basics-languages, system calls, and tool invocations-that one can actually keep using for years, even decades. Elsewhere it is impossible to predict what will be stable; even entire operating systems cycle out of use. Under Unix, there is a fairly sharp distinction between transient knowledge and lasting knowledge, and one can know ahead of time (with about 90% certainty) which category something is likely to fall in when one learns it. Thus the loyalty Unix commands.
Consider computing power - time exponential curve, consider the corresponding pace of software development, the results of one of the inference is: you know what, every 18 months there will be 50 per cent outdated. Unix observe this phenomenon is not an exception, but in good agreement. No change is the foundation - language, system calls and the use of tools - they can use several years, even decades. Elsewhere, it is impossible to predict which will be stable and even, the entire operating system may no longer be used. Under Unix, short-term and lasting knowledge, the distinction between knowledge was quite obvious, you learn something, the basic advance inferred (about 90% certainty) of your knowledge of a temporary or lasting knowledge. This is supported by the reasons for Unix.
Much of Unix's stability and success has to be attributed to its inherent strengths, to design decisions Ken Thompson, Dennis Ritchie, Brian Kernighan, Doug McIlroy, Rob Pike and other early Unix developers made back at the beginning; decisions that have been proven sound over and over. But just as much is due to the design philosophy, the art of programming, and technical culture that grew up around Unix in the early days. This tradition has continuously and successfully propagated itself in symbiosis with Unix ever since.
Unix stability and success, largely attributed to its inherent strength, attributed to Ken Thompson, Dennis Ritchie, Brian Kernighan, Doug McIlroy, Rob Pike, as well as other early Unix developers from the beginning to the design of decision-making; the correctness of the decision-making has been repeatedly proven. However, early on the Unix grew up thinking of the design, programming art, technology and culture of the same great contribution. This tradition will continue to successfully succeed, and always with Unix interest income dependencies.
[1] The three and a half decades between 1969 and 2003 is a long time. Going by the historical trend curve in number of Unix sites during that period, probably somewhere upwards of fifty million man-years have been plowed into Unix development worldwide.
1969-2003 is the first of the 35 paragraphs long time. During this period, along with a number of historical sites Unix growth trend line, probably more than 50 million years, the energy input to the development of the global Unix.
[2] This particular footnote is dedicated to Terry Pratchett, whose use of footnotes is quite inspiring ….
This particular footnote dedicated to the Terry Pratchett, he is a footnote to the use of…… instructive.
[3] An appreciation of Alexander's work, with links to on-line versions of significant portions, may be found at Some Notes on Christopher Alexander [http://www.math.utsa.edu/sphere/salingar/Chris. text.html].
Appreciation of the work of Alexander, as well as an important part of his book at the online version of the link, can Some Notes on Christopher Alexander web site to find [http://www.math.utsa.edu/sphere/salingar/Chris.text.html] .
[4] In fact, Ethernet has already been replaced by a different technology with the same name - twice. Once when coax was replaced with twisted pair, and a second time when gigabit Ethernet came in.
In fact, Ethernet has been to have the same name replaced by the different techniques - and replaced twice. Twisted-pair is replaced by a coaxial cable, and the second was the emergence of Gigabit Ethernet.
0 Comments to “TAOUP early translations: the version”
No Comments. Send your comment.
Leave a Reply
You must be logged in to post a comment.