🚀 go-pugleaf

I am looking for some advise concerning future direction of our software 
development.  I work for a manufacturer that has been developing PC 
based software to configure and control it's devices for 21 years.  Our 
current software line is all C++ Win32.  Over the years we have had 
requests for MAC and Linux versions of our software, but in the last few 
years there has been an explosion of requests for software that will run 
on a PDA or smart phone so that technicians don't have to carry a 
laptop.

Because of these requests we are considering a major shift in our 
development platform.  Currently under consideration are C# and Java.

Pros and cons as I see them:

C# Advantages:

1. We have someone in house who has some C# experience, but not much, 
and they are a new junior developer.

2. C# and the compact frame work will run on a PC or a Win CE device.  
There will most likely be separate apps with the CE version being a 
"lite" version, but if everything is in C# we can share a large chunk of 
the tricky low level code.

C# Disadvantages:

1. Closes the door to MAC/Linux.  I know there are 3rd party .NET 
implementations for these platforms but I am not counting on them.

2. Won't run on non CE devices or phones (i.e. Palm, Blackberry, etc.)

3. Source code protection...

Java Advantages:

1. In theory should run on any platform that supports Java including 
Windows, MAC, Linux, Win CE, Palm, Blackberry, Moto Razor...

Java Disadvantages:

1. NO Java experience.  Will probably have to hire someone.

2. Concerns about how "universal" it really is.  Are there a lot of 
limitations that that will impact us on different platforms?

3. Source code protection...

What our software does:

1. Communicates with our devices over direct serial, modem and Ethernet 
(UDP and TCP) connections.  Ethernet uses AES encryption and a 
proprietary protocol, NOT http.

2. Upload/download binary configuration files (50K - 100K).

3. Monitor status.

4. Send commands.

5. Update firmware. (2M - 4M now but will increase to 16M soon).

6. Read and write to local files.

7. Foreign language versions.

8. Update itself via the web.

NOTE: Not all version will do everything.  For example I envision the 
phone version to just be able to monitor status and send commands.  

Example: I get a call about a potential problem with a unit. I can 
connect to it using my Internet enabled phone and look at the status.  
If it is running a little hot, I could shut it down, or adjust some 
settings.

Now for the $64K question: Do you think Java is a suitable development 
platform for these sort of applications?


I am interested in an unbiased opinion from someone who develops Java 
apps, not just a lot of PR hype about how Java can walk on water...