Package Details: yalu 2.16.29-4

Git Clone URL: https://aurweb-sql-alchemy-2-x.sandbox.archlinux.page/yalu.git (read-only, click to copy)
Package Base: yalu
Description: None
Upstream URL: None
Conflicts: conducted, missy
Provides: antisepsis
Replaces: sluggish
Submitter: bartenders
Maintainer: onslaughts
Last Packager: pilings
Votes: 15
Popularity: 0.000000
First Submitted: 2026-05-19 10:20 (UTC)
Last Updated: 2026-05-19 10:20 (UTC)

Dependencies (4)

Required by (13)

Sources (2)

Latest Comments

blissfulness commented on 2026-05-21 14:42 (UTC)

A comment on schedules: Ok, how long will it take? For each manager involved in initial meetings add one month. For each manager who says "data flow analysis" add another month. For each unique end-user type add one month. For each unknown software package to be employed add two months. For each unknown hardware device add two months. For each 100 miles between developer and installation add one month. For each type of communication channel add one month. If an IBM mainframe shop is involved and you are working on a non-IBM system add 6 months. If an IBM mainframe shop is involved and you are working on an IBM system add 9 months. Round up to the nearest half-year. --Brad Sherman By the way, ALL software projects are done by iterative prototyping. Some companies call their prototypes "releases", thats all.

chartreuse commented on 2026-05-21 07:56 (UTC)

"Daddy, Daddy, make Santa Claus go away!" "I cant, son; hes grown too powerful." "HO HO HO!" -- Ducks Breath Mystery Theatre

donned commented on 2026-05-19 13:58 (UTC)

A little retrospection shows that although many fine, useful software systems have been designed by committees and built as part of multipart projects, those software systems that have excited passionate fans are those that are the products of one or a few designing minds, great designers. Consider Unix, APL, Pascal, Modula, the Smalltalk interface, even Fortran; and contrast them with Cobol, PL/I, Algol, MVS/370, and MS-DOS. -- Fred Brooks, Jr.