History Origins and History of Unix, 1969-1995 Genesis: 1969–1971 Exodus: 1971–1980 TCP/IP and the Unix Wars: 1980-1990 Blows against the Empire: 1991-1995 Origins and History of the Hackers, 1961-1995 At Play in the Groves of Academe: 1961-1980 Internet Fusion and the Free Software Movement: 1981-1991 Linux and the Pragmatist Reaction: 1991-1998 The Open-Source Movement: 1998 and Onward The Lessons of Unix History 3. The Unix Philosophy in One Lesson Applying the Unix Philosophy Attitude Matters Too 2. Rule of Extensibility: Design for the future, because it Rule of Diversity: Distrust all claims for Rule of Generation: Avoid hand-hacking write programs to write Rule of Economy: Programmer time is expensive conserve it in Must fail, fail noisily and as soon as possible. Rule of Repair: Repair what you can - but when you Rule of Silence: When a program has nothing surprising
Rule of Least Surprise: In interface design, always do So program logic can be stupid and robust. Rule of Representation: Fold knowledge into data, Rule of Robustness: Robustness is the child of transparency and simplicity. Rule of Transparency: Design for visibility to make Rule of Parsimony: Write a big program only when it isĬlear by demonstration that nothing else will do. Rule of Simplicity: Design for simplicity add complexity only where you must. Rule of Separation: Separate policy from mechanism Rule of Composition: Design programs to be connected with other programs. Rule of Clarity: Clarity is better than cleverness. Philosophy Culture? What Culture? The Durability of Unix The Case against Learning Unix Culture What Unix Gets Wrong What Unix Gets Right Open-Source Software Cross-Platform Portability and Open Standards The Internet and the World Wide Web The Open-Source Community Flexibility All the Way Down Unix Is Fun to Hack The Lessons of Unix Can Be Applied Elsewhere Basics of the Unix Philosophy Rule of Modularity: Write simple parts connected by clean interfaces.
PROGRAMMIER BUCH HOW TO
Table of Contents Preface Who Should Read This Book How to Use This Book Related References Conventions Used in This Book Our Case Studies Author's Acknowledgements I. 2021-2048 and is reproduced with the permission of Bell The epigraph on the Portability chapter is from theīell System Technical Journal, v57 #6 part 2 (July-Aug. The photograph of Ken and Dennis in Chapter 2 appears courtesy of Bell Labs/Lucent
PROGRAMMIER BUCH PDF
PDF and PostScript are trademarks of Adobe, Inc. Informix is a trademark of Informix software. SPARC is a trademark of SPARC international.
PROGRAMMIER BUCH CODE
This online book is freely available for personal use only. It remains largely relevant for later versions, but there are some differences.Ĭopyright © 2003–2004 Roberto Ierusalimschy. This is the online version of the first edition of the bookĪ detailed and authoritative introduction to all aspects of Lua programming written by Lua's chief architect.