Why the fuck Cisco can't do the same with their 1KB but omfg-they're-ultra-critical-to-the-whole-goddamned-enterprise config files I just don't understand. Maybe they're trying to save precious bytes...
They've started to in IOS 15.x. They even have started (gasp) to take mac address formats other than xxxx.xxxx.xxxx on some of their show commands.
(This day and age all network ready equipment should take pretty much any mac address format from IETF to colon delimited to even less seen stuff like xxxxxx-xxxxxx, but yet still does not, it's pathetic)
Having worked with a bunch of cisco-like devices I have to say cisco still has the best CLI I've seen so far among the major vendors. Being able
to pipe commands and output through a grepish utility is rarer than you might think, and a lot of the ciso workalikes do not have nearly the
discipline Cisco has about making sure you can paste or copy the text config file in and have an identically functioning device (minus just the private keys.)
Then again I haven't had a chance to work with Juniper yet which I've been told is pretty good.
* Behind the Scenes. Some GUIs have 1:1 mappings with some sort of underlying command-line or protocol. Consoles based on PowerShell such as most Microsoft and Citrix products come to mind, most Linux/Unix GUIs, and Database admin tools. The better ones will have a "tab" or a pop-up somewhere which shows the "script equivalent" of whatever you're doing in the GUI. This is very useful, particularly for beginners, and we're all beginners with every product at least once.
Not only that but in the NMS sector it would be super nice if they'd stop trying to just push all the configs out to switches and started allowing mods to be made on the CLI and the NMS to notice and integrate them. Sometimes you just want to have certain portions of the config controlled by switch-local configs, because they are easier to administer that way.
I'd add auto rollback to your list. All interfaces to networking equipment should offer the ability to apply changes, and have them take effect and then, if you do not confirm to make them permanent, revert the changes in a X minute window, like unto what the PC user does when changing a video mode. It's an essential last line of defense against human error, because most networking equipment can strand itself because it is managed in-band to save cash. (The number of NMS's that don't know how to renumber the far side of an interface first before the near side is like 99% of them, BTW)