Topic
shar
About: shar is a research topic. Over the lifetime, 35 publications have been published within this topic receiving 533 citations. The topic is also known as: .shar & .sha.
Papers
Book•
1 Jan 2003
TL;DR: This book brings together for the first time the philosophy, design patterns, tools, culture, and traditions that make UNIX home to the world's best and most innovative software, and shows how these are carried forward in Linux and today's open-source movement.
Abstract: "Reading this book has filled a gap in my education. I feel a sense of completion, understand that UNIX is really a style of community. Now I get it, at least I get it one level deeper than I ever did before. This book came at a perfect moment for me, a moment when I shifted from visualizing programs as things to programs as the shadows cast by communities. From this perspective, Eric makes UNIX make perfect sense." --Kent Beck, author of Extreme Programming Explained, Test Driven Development, and Contributing to Eclipse"A delightful, fascinating read, and the lessons in problem-solvng are essential to every programmer, on any OS." --Bruce Eckel, author of Thinking in Java and Thinking in C++Writing better software: 30 years of UNIX development wisdomIn this book, five years in the making, the author encapsulates three decades of unwritten, hard-won software engineering wisdom. Raymond brings together for the first time the philosophy, design patterns, tools, culture, and traditions that make UNIX home to the world's best and most innovative software, and shows how these are carried forward in Linux and today's open-source movement. Using examples from leading open-source projects, he shows UNIX and Linux programmers how to apply this wisdom in building software that's more elegant, more portable, more reusable, and longer-lived.Raymond incorporates commentary from thirteen UNIX pioneers: Ken Thompson, the inventor of UNIX. Ken Arnold, part of the group that created the 4BSD UNIX releases and co-author of The Java Programming Language. Steven M. Bellovin, co-creator of Usenet and co-author of Firewalls and Internet Security. Stuart Feldman, a member of the Bell Labs UNIX development group and the author of make and f77. Jim Gettys and Keith Packard, principal architects of the X windowing system. Steve Johnson, author of yacc and of the Portable C Compiler. Brian Kernighan, co-author of The C Programming Language, The UNIX Programming Environment, The Practice of Programming, and of the awk programming language. David Korn, creator of the korn shell and author of The New Korn Shell Command and Programming Language. Mike Lesk, a member of the Bell Labs development group and author of the ms macro package, the tbl and refer tools,lex and UUCP. Doug McIlroy, Director of the Bell Labs research group where UNIX was born and inventor of the UNIX pipe. Marshall Kirk McKusick, developer of the 4.2BSD fast filesystem and a leader of the 4.3BSD and 4.4BSD teams. Henry Spencer, a leader among early UNIX developers, who created getopt, the first open-source string library, and a regular-expression engine used in 4.4BSD.
357 citations
36 citations
26 citations
Journal Article•
TL;DR: The purpose of this paper is to describe how the Guide hypertext system has been designed to exploit the UNIX environment and to claim that it has been able to gain a lot of value from it.
Abstract: Hypertext is concerned with on-line documentation. Over the past two years, interest in hypertext has grown dramatically and there has been a corresponding explosion in the number of hypertext systems, journal articles and, indeed, hypertext experts. One of the deficiencies of many of today's hypertext systems is that they are closed systems: they do not work well with their fellow tools. Though it may be possible to exchange information with other tools, this needs to be done via conversion utilities or the like. As Meyrowitz Ir9s7] highlighted in his influential contribution to the Hypertext 87 conference, this drains the blood out of the hypertext system. If hypertext systems are to realise their full potential, they must aim for a seamless interface with other tools, thus making the whole greater than the sum of the parts. Such a philosophy is, of course, one of the cornerstones of UNIX. The purpose of this paper is to describe how the Guide hypertext system has been designed to exploit the UNIX environment. The word "seamless," like the world "user-friendly," is wantonly applied to almost all software: it is fast becoming a noise-word. If we are to stick to the true meaning of seamlessness, Guide cannot claim to have attained it. Nevertheless the claim of this paper is that it has been able to gain a lot of value from @ Computing Systems, Vol. 2 . No. I . Winter 1989 37 interchanging information with its UNIX environment. It is no use writing a paper about integration unless readers understand what is being integrated. Since some readers will be unfamiliar with hypertext in general and Guide in particular, so we shall introduce these frrst.
26 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2021 | 2 |
| 2020 | 1 |
| 2017 | 2 |
| 2016 | 4 |
| 2014 | 2 |
| 2011 | 1 |