I hope you were serious because I'm going to spend a bit of time giving you a serious answer.
Telcom Network management is a very vertical platform. We have cross-platform development issues, need to interact with many databases and needed a very strong client/server system. We bought a system from Dorado Software that did a lot of the base network management stuff (mapping, discovery, ability to add configuration, etc). We also leveraged a lot of the messaging, client/server and failover capabilities of J2EE.
This is a pretty damn hard problem space. On top of this large platform that contacted/interacted with/managed many MANY devices, you needed customers to be able to interface to their own specific devices using their devices' own little invented language which is often some off-flavor of SNMP or CMIP--for many devices you just had to programatically telnet/http to the device and interact with it as though you were a user.) We're talking many million dollar devices that take up a room and don't get updated all that often or devices where you have many million deployed... You don't change them, you learn to speak their language instead)
So as an end customer (say a large telephone company) you might have this Mangement platform from some vendor managing millions of dollars worth of room-sized T1/T2/T3/OC3 switches and terminators. It may also manage end-customer equipment like high-end routers, switches, DSUs, etc. You could even want to go down to the level of managing PCs or cable set-top boxes (imagine how many of those are hooked up to one head-end).
Now, each of those have software written by their vendor to integrate their hardware into Dorado's platform--either that or the customer has to write that software or contract it out.
Java was a real boon to this industry--When Java became popular the C stuff (which it all was up until then) pretty much VANISHED. The speed of development, vastly more controllable codebase, easier integration and ability to remove windows from the equation--Windows wasn't considered a professional platform by the Bells for a LONG time and they are slow to integrate changes. They still prefer Unix (not even Linux) for many deployments.
Java Is pretty much a perfect solution for this space. It let me scan a sparse class B network space in 15 minutes! I challenge you to do significantly better in another language. There is nothing wrong at all with the choice of language, Even with the old IO libraries I was able to singlehandedly replace the ping library with my fast one in a weekend including client/server integration relaying results, scheduling and database updates. I couldn't have done it in a month using C even with a small team, and few dynamic languages would have been quick enough.
In fact, I was in Network Management for 20+ years and from the time they moved from c to Java, things just took off. Tools started to be reusable, you could buy stuff "off the shelf" that EVERYONE previously had to spend years creating themselves, developers were available and pretty easy to find, the J2EE platform contained a bunch of powerful functionality for free, the list goes on.