On 01/26/2011 07:13 PM, Damion Alexander wrote: > David Lang wrote: >> I think there is also a bit of the unix world being 'here are the >> tools, build exactly what you want' and people need to ask for help >> (or get blueprints or cheat sheets for doing things) where on >> windows the options tend to be much more tightly constrained, and >> only the vendor can help you do anything. > > I agree with David Lang on this. Though I think it points to > something more generic. I think *nix, and even Mainframe people feel > a bit of ownership over every install they do because they have > options to make things the way they want. Now matter how much you > paid for the object, or the rules surrounding it, if you can tweak it > to your hearts content it feels more like yours. And when you have > something you enjoy you tend to share that joy with others. > > Windows tends to be more 'this is the way you do it'. And without > that emotional attachment it ends up being just a tool. And not many > people get together to talk about their joys of hammers. > > The thought also crossed my mind that the Windows GUI gets in the > way.
I think this may explain a bunch. I have certainly seen many admins who know how to do things in the GUI without knowing/thinking about what's happening down the stack. I don't see that with people who primarily use a command line for management/configuration. -- Thanks Jefferson Cowart j...@cowart.net _______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
