Choice of language on .NET

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm headed back to school to retool. I have enrolled into a .NET programming
certificate program. We have a choice of Java or Visual Basic on the .NET
platform. Of course its not described this way. The Java is described as for
web development and the Visual Basic is described as programming.

Of those of you that actually program in Java and VB on the .NET platform,
which do you prefer? What are your opinions on the lanuages I have to choose
between? Is one more usable then the other? What are the pro's and Con's ?
 
Well, I assume they mean J# rather than Java?
have a look at the number of posts in the VB.NET newsgroup compared to the
J# one and you wil see which is more popular.

btw I have never actually met a J# developer!
 
Morpth said:
I'm headed back to school to retool. I have enrolled into a .NET programming
certificate program. We have a choice of Java or Visual Basic on the .NET
platform. Of course its not described this way. The Java is described as for
web development and the Visual Basic is described as programming.

Of those of you that actually program in Java and VB on the .NET platform,
which do you prefer? What are your opinions on the lanuages I have to choose
between? Is one more usable then the other? What are the pro's and Con's ?
Click to expand...

When you say Java, do you really mean J# (Microsoft's abomination of Java)?
If those are your choices, then I would recommend VB.Net.
If C# is an option, this would be my overall recommendation, especially if
you have plans of programming in .NET professionally, but VB.Net would be a
good second choice.

C# is much more Java like than Microsoft might care to admit.
If you had a desire to really learn Java, you would be much better served to
take a real Java class. Microsoft's attempts to unseat Sun in the Java arena
have been, um, abysmal. IMHO, they should abandon the attempt all together
and work on better things.

Given a choice between C#, J#, and VB, I personally do know know a single
person who has, or would, choose J#.

Gerald
 
Morpth said:
I'm headed back to school to retool. I have enrolled into a .NET programming
certificate program. We have a choice of Java or Visual Basic on the .NET
platform. Of course its not described this way. The Java is described as for
web development and the Visual Basic is described as programming.

Of those of you that actually program in Java and VB on the .NET platform,
which do you prefer? What are your opinions on the lanuages I have to choose
between? Is one more usable then the other? What are the pro's and Con's ?
Click to expand...

If you're going to learn Java, use *real* Java rather than J#. Java has
come on leaps and bounds since the version which Microsoft effectively
stuck at.

If you want to learn .NET, I'd suggest learning VB.NET or C#
(preferably C# IMO, but it sounds like that isn't an option).
 
Being somewhat of a pragmatist I made it easy for myself to make the
choice...

Web developers have to master JavaScript which is used on the client. The
lexical syntax and grammar for JavaScript was derived from C and is nearly
exactly the same for C# and Java both of which are used on the server. Learn
one language and you learn three. Now is that pragmatic or what?

I've also observed that all newer languages from research.microsoft.com are
developed using the legacy characteristics of the C language and are being
implemented using C#. It has also been my observation that all other
languages on all other platforms also in whole or in a significant part also
derive from C or use C or C++ directly.

When somebody asks this question when first becoming involved with ASP.NET I
can't help but wonder how they can possibly become confused when the answer
should be so clearly evident.


<%= Clinton Gallagher
METROmilwaukee (sm) "A Regional Information Service"
NET csgallagher AT metromilwaukee.com
URL http://metromilwaukee.com/
URL http://clintongallagher.metromilwaukee.com/
 
Clinton,

That was for me a reason as well, however most ASP (not a minor part)
serverside programming is done with VBS.

Two languages on one page is with Net 1.1 not allowed.

Therefore the path you show is maybe logical however in my opinion not
always the best when migrating from asp to aspnet.

Just my opinion

Cor
 
Back
Top