I've been doing Linux admin in some fashion or another for 20+ years, so in many ways I'm part of the "old guard".
I guess we're part of a similar generation, although I have about 5 years less (started in 1997 with Linux).
The argument about small being better, making programs that do one thing well, etc is a good design element that's worked for years.
This is exactly what I'm talking about. Yes, it has worked for years, and that's why you like it. You (we?) are now that "old generation" that I was referring to, and I'm not about to become a grumpy old admin.
Let me give you another example, which is geared a bit more towards my current profession. In the last couple of years, I worked for two large vendors of networking equipment. Vendor R used your way of doing things: each network protocol has its own daemon. So you end up having ospfd, isisd, bgpd etc. Worked just fine. I also worked for vendor J, who used one big binary: rpd handles just about every routing protocol you can imagine. Is J bad and is R good? According to the market, J is doing very well, while R has been acquired and assimilated by a another company.