I have no idea what you are actually attempting to do on Linux but I get the feeling you are "holding it wrong". What daemons are you attempting to install which requires you writing scripts? And why in the world would you have to install daemons on any sort of recurring basis with just a couple of machines on a home LAN? When you use the package managers for Linux systems that should be taken care of for you almost in the entirety, "out of the box" per-se.
I haven't had an experience anywhere remotely similar to what you are claiming except for when I've gone off the farm and have attempted to custom compile applications downloaded off the web or from a proprietary vendor (i.e. very rarely). But I knew what I was getting into and which automated management facilities wouldn't be available to me when I did. That I occasionally had any problems doing manual compilation was not unexpected and help was frequently just a simple google away.
I've been maintaining multiple (dozens of) networks of Windows, RedHat/CentOS, and Debian/(K|U)buntu servers and desktops for years now (plus tinkering with other derivatives). They are all pretty good about "easy" and "just works" installations... with the expectation that you are using their respective package managers, repositories, toolsets, methodologies, and ecosystems (or at least packaging formats) to install software.
RPM/Yum and Dpkg/Apt really do take care of most of the work and neither are obscure by definition of the fact that they manage the entire distribution (and repositories) by default. Your equivalent problem in Windows would be a failure of you to understand (or use) Windows Update and instead attempt to install all of the Windows updates including registry hacks... by hand... without using an .msi file or the like and then pondering why Windows is so convoluted when you fail to get a working machine out of the ordeal. Nobody works that way.
Besides that, most Linux application developers will release into one of these two formats anyways (deb or rpm), so I fail to see how you could possibly be stuck writing scripts "every time" you "install a new daemon app" unless you are using something like DSL (Damn Small Linux) where package managers are not necessarily present. And if that is the case you are using the wrong distro for your skill level.
I've also had the opposite experience re: log files on Linux. Text and log files are cheap and plentiful when the command line is a useful part of your operating system. Normally I get such verbose logging from a failure that it actually takes a little bit of investigative work to find the original point of failure instead of all of the effects. On the other hand I rarely get log lines (only error codes when I'm lucky) from many Windows applications when they fail however...
Not to be too harsh but your "simple fact" is not reflective of the reality on the ground. Your perspective is "off" and I think you have failed to grasp some basic computing and usage concepts instead.