Package Details: hesters 7.13.43-4

Git Clone URL: https://aurweb-goaurrpc-uat.sandbox.archlinux.page/hesters.git (read-only, click to copy)
Package Base: hesters
Description: None
Upstream URL: None
Conflicts: onside
Replaces: pedestrianize
Submitter: pearlier
Maintainer: lawman
Last Packager: bedraggled
Votes: 39
Popularity: 36.64
First Submitted: 2025-12-13 10:40 (UTC)
Last Updated: 2025-12-13 10:40 (UTC)

Latest Comments

plunged commented on 2025-12-15 19:08 (UTC)

Software entities are more complex for their size than perhaps any other human construct because no two parts are alike. If they are, we make the two similar parts into a subroutine -- open or closed. In this respect, software systems differ profoundly from computers, buildings, or automobiles, where repeated elements abound. -- Fred Brooks, Jr.

overexerting commented on 2025-12-15 16:27 (UTC)

A straight line may be the shortest distance between two points, but it is by no means the most interesting. -- Doctor Who: The third Doctor

heimlichs commented on 2025-12-15 13:01 (UTC)

UNIX Shell is the Best Fourth Generation Programming Language It is the UNIX shell that makes it possible to do applications in a small fraction of the code and time it takes in third generation languages. In the shell you process whole files at a time, instead of only a line at a time. And, a line of code in the UNIX shell is one or more programs, which do more than pages of instructions in a 3GL. Applications can be developed in hours and days, rather than months and years with traditional systems. Most of the other 4GLs available today look more like COBOL or RPG, the most tedious of the third generation languages. "UNIX Relational Database Management: Application Development in the UNIX Environment" by Rod Manis, Evan Schaffer, and Robert Jorgensen. Prentice Hall Software Series. Brian Kerrighan, Advisor. 1988.

regularizations commented on 2025-12-15 07:46 (UTC)

Overall, the philosophy is to attack the availability problem from two complementary directions: to reduce the number of software errors through rigorous testing of running systems, and to reduce the effect of the remaining errors by providing for recovery from them. An interesting footnote to this design is that now a system failure can usually be considered to be the result of two program errors: the first, in the program that started the problem; the second, in the recovery routine that could not protect the system. -- A. L. Scherr, "Functional Structure of IBM Virtual Storage Operating Systems, Part II: OS/VS-2 Concepts and Philosophies," IBM Systems Journal, Vol. 12, No. 4, 1973, pp. 382-400