Put everything you need to run automatically at startup in /etc/profile or one of the other autoexec files, and you won't have to deal with a mess of init scripts or the horrors of systemd. It's like AUTOEXEC.BAT for *nix, easy and simple. If you want a GUI just put startx in there...
Name:
Anonymous2015-01-26 15:11
How should logging/monitoring be handled? If everything is just disjoint programs started from a shell script how can you hook any kind of instrumentation in? How to deal with orphaned processes? How to deal with dependencies, i.e some service A requires networking, logging and service B to be started before hand? Speaking of networking (or other high latency services), do you really wanna stall the entire boot process just because of these? Which brings up: How to deal with asynchronous/parallel startup? In particular with combination of above - parallel + dependencies.
If you consider these 'unnecessary bloat' I would question your use of a computer in the first place - computers are made to automate things and make our lives easier, why would you *not* wanna have fast, asynchronous, event based boot with automatic dependency handling?