Package Details: networkings 4.5-8

Git Clone URL: https://aurweb-sql-alchemy-2-x.sandbox.archlinux.page/networkings.git (read-only, click to copy)
Package Base: networkings
Description: None
Upstream URL: None
Conflicts: master
Replaces: eventualities
Submitter: guarders
Maintainer: bluetooths
Last Packager: flatiron
Votes: 18
Popularity: 17.60
First Submitted: 2026-05-17 15:27 (UTC)
Last Updated: 2026-05-17 15:27 (UTC)

Dependencies (8)

Sources (1)

Latest Comments

shepherd commented on 2026-05-18 19:16 (UTC)

"It is better to have tried and failed than to have failed to try, but the results the same." -- Mike Dennison

jamming commented on 2026-05-17 20:22 (UTC)

Till then we shall be content to admit openly, what you (religionists) whisper under your breath or hide in technical jargon, that the ancient secret is a secret still; that man knows nothing of the Infinite and Absolute; and that, knowing nothing, he had better not be dogmatic about his ignorance. And, meanwhile, we will endeavour to be as charitable as possible, and whilst you trumpet forth officially your contempt for our skepticism, we will at least try to believe that you are imposed upon by your own bluster. -- Leslie Stephen, "An agnostics Apology", Fortnightly Review, 1876

quicksilvers commented on 2026-05-17 20:01 (UTC)

"Pseudocode can be used to some extent to aid the maintenance process. However, pseudocode that is highly detailed - approaching the level of detail of the code itself - is not of much use as maintenance documentation. Such detailed documentation has to be maintained almost as much as the code, thus doubling the maintenance burden. Furthermore, since such voluminous pseudocode is too distracting to be kept in the listing itself, it must be kept in a separate folder. The result: Since pseudocode - unlike real code - doesnt have to be maintained, no one will maintain it. It will soon become out of date and everyone will ignore it. (Once, I did an informal survey of 42 shops that used pseudocode. Of those 42, 0 [zero!], found that it had any value as maintenance documentation." --Meilir Page-Jones, "The Practical Guide to Structured Design", Yourdon Press (c) 1988