That's why I said "bury". The basic problem here is a conflict between a mindset that builds stuff up from smaller parts, and the needs of people who need to use the higher level stuff. Building up from components is good for many reasons. But people who want to buy a car don't expect to be handed a pile of auto parts --- or to be shown them mixed in with the cars when shopping for one. (Heck, that's infuriating even for those of us who do work with parts. I can't count the number of times I go to look for a radio or w/e and amazon / google shopping / best buy have more listings for antennas than for radios. Same problem.)
On Wed, Mar 1, 2017 at 5:38 PM, Bennett Todd <bennett.e.t...@gmail.com> wrote: > Well, tastes can reasonably differ on that point. Bunging all of the > complexity, of implementation, of design tradeoffs, and of documentation, > into one big module might suit some tastes. Not mine, as either an > implementor or a user. > > Not all uses need all components, and I for myself would rather implement, > or learn to use, or need to maintain, one simpler component at a time. > -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
