There is a significant difference in practice: >95% of C#
developers use GUI builder, <5% of Java developers
use GUI builder.
This is a curious statement. Exactly what do you mean by this? That
Java for the most part works at the server side and hence no need for
a GUI except for the standard tools that you use with HTML on the
client side, like CSS style sheets etc?
But GUI builders are available for Java if somebody want
to use them.
Why? Why would 5% want to use them?
I don't think anyone stated that.
It's the logical conclusion. Given a choice, most people who know
both C# and Java would choose C#, unless their client told them
otherwise. I think objective lovers of C# would agree with me on this.
Hmm.
What do do you think the 'J' in "AJAX" stands for?
Java? I did not know that. Well I guess I do know "Java" after all,
but only for simple stuff like the Update Panel control in ASP.NET
programming, which I've used a couple of times to preserve state like
for a clock, progress bar, etc.
There are plenty of Java PaaS solutions available. From Google, VMware,
Salesforce etc.. Most of it is commercial.
Platform as a Service--yes, it figures Java PaaS is available, as
companies seek to capitalize on Java's popularity--see my comments
above about your client/boss/customer insisting on using Java (one
reason is that there are more Java programmers than C#, even though
Java is inferior to C#, so the boss naturally chooses Java since more
programmers to pick from, though in the long run I would argue that it
will take more time to do a project using Java programmers, not to
mention the excessive maintenance needed).
Thanks for your comments btw I find them quite helpful--like a free
kollege tutor where you don't get marked down for talking back.
RL