Brian
writes of stack installers (as opposed to component installers):
If I were a business and not a developer that would make a lot of sense.
It seems to me that this makes just as much sense for software developers, especially those with limited time for their projects - and especially those for whom development is a hobby and not (just) a full-time job.
I have a handful of hours over a weekend for my hobby, and if I spend even 1 hour doing simple system or stack maintenance, that's one hour less for whatever project I really wanted to work on. And when I was a full-time developer, well, I didn't have much free time or slack in my schedule then either. :/
So yes, I'm fully capable of composing and installing a stack, but I choose to not do that, simply for the ability to focus on my chosen problem. Just as I don't compose my own Linux distro, or write my own compilers. And when I'm woodworking I don't build my own bench tools. Focus. Efficiency.
links: digg this del.icio.us technorati reddit