It's really a question you should be asking someone in your company. There is no general answer to this question, and every company has it's own reasons for doing something like this. It could be that the CTO is a moron and wasting engineering time chasing a fad, it could be that staying on Java presents some sort of risk to the company, it could be that Java simply isn't a good fit for the problems the company is solving, there are a million reasons for doing something like this. It doesn't necessarily mean that Java is bad, just that Java isn't really fit for the company's purpose.
It's really a question you should be asking someone in your company. There is no general answer to this question, and every company has it's own reasons for doing something like this. It could be that the CTO is a moron and wasting engineering time chasing a fad, it could be that staying on Java presents some sort of risk to the company, it could be that Java simply isn't a good fit for the problems the company is solving, there are a million reasons for doing something like this. It doesn't necessarily mean that Java is bad, just that Java isn't really fit for the company's purpose.
save