While I agree with Steve on a philosophical level, there are a lot of merits to command lines and direct editing of configuration, there also comes a time when "just getting the job done" is benefited by a nice point-n-click.
I have found in my career that I may spend a month neck deep in a project, such as implementing Asterisk, then for the following 6 months never have to touch it again. During those 6 months away, I would have been implementing a new intrusion prevention system, probably doing a bit of programming, managing my 300+ Linux servers, or helping our DBA setup new MS-SQL clusters. When I'm asked to do something like, say reroute all incoming calls through a new IVR with several new queues, it sure helps to have a gui to help out instead of having to relearn the guts of the system. But these are just my thoughts on the subject. And so far during my month of being neck deep in implementing Asterisk I have used FreePBX. Jeremy > None. I'm a command line weenie. > > ) GUIs don't let you annotate your changes -- who did what (or what they > thought they were doing), when, and why. > > ) GUIs don't support any sort of "versioning." > > ) GUIs don't support any sort of configuration rollback. > > All of these are essential when something that used to work suddenly > doesn't. (Sometimes, client's don't notice something isn't working for > months -- way beyond my short term memory.) > > I'm sure I could come up with dozens more, these were just the first 3. > (Probably not even the most important 3.) > > Oh. Here's 1 more -- GUIs impede truly understanding a system. > _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
