"We'll now have to learn a whole new language other than Cisco's IOS standard when our directors decide Juniper might be a good idea to implement......"

Cisco IOS a standard? I must have missed the news from ISO. Ahh, you mean in the sense that IBM's JCL was once the typical way of running a program, although I notice I don't use JCL much anymore :-)

Seriously, I use both Cisco and Juniper and the commit/rollback and "move" features of the JUNOS configuration language just rock. Those features are also in Cisco's next-generation IOS XR, but you won't be seeing that on switches.

There is a learning curve with the JUNOS language, mainly with the odd way used to edit the configuration (more like SNMP than programming). Juniper's stateless "set" commands work nicely with Expect scripts.

Of course, you don't edit the configuration on switches these days anyway -- who wants to log into a few hundred switches, even using Expect. So you might want to look at if/how much Juniper charge for their element manager. Not sure is they give it away for free like Cisco Works or charge like a wounded bull like the SDH/DWDM manufacturers.

An interesting question to ask is why are Juniper so late to this market, and to enterprise networking in general? It's a much larger market than backbone ISPs and even at the launch of the first Juniper router at NANOG potential customers were asking when enterprise use would be supported.