Which is a wiser choice for an IT professional to take up, Java or .NET?

[cat_dog_ass]

Java is mature...however, a beginner may not stand any chance to
compete against industry bigwigs. On the other hand, .NET is newer and
gives newbies a relatively firm foothold, since there are hardly
experienced ppl there. Also, I'm interested in computer security
involving low level coding in C, C++. Which platform will be better for
me keeping this in view?

 

[Jon Skeet [C# MVP]]

Java is mature...however, a beginner may not stand any chance to
compete against industry bigwigs. On the other hand, .NET is newer and
gives newbies a relatively firm foothold, since there are hardly
experienced ppl there. Also, I'm interested in computer security
involving low level coding in C, C++. Which platform will be better for
me keeping this in view?

Either of them should be fine. If you need to interact with native
code, .NET has a much better story than Java provides with JNI. I'm not
sure whether that was what you meant in the last couple of lines or not
though.

My *personal* view is that:

1) C# is mostly a nicer language than Java (although I crave Java's
enums in C#)

2) Eclipse provides a nicer IDE than VS

3) The Java community is more active, in that there are far more Java
open source projects, and they tend to be more mature

 

[Mark Rae]

although I crave Java's enums in C#

Maybe we'll get those in v3... ;-)

 

[Joe]

2) Eclipse provides a nicer IDE than VS

This response intrigues me. I use Eclipse to review java source code we
use elsewehere within our organization, although I don't edit any of the
java code myself. I develop C# using VS2005, and am curious what
features/functionality of Eclipse are better than the VS IDE?

Thanx

 

[SharpCoderMP]

This response intrigues me. I use Eclipse to review java source code we
use elsewehere within our organization, although I don't edit any of the
java code myself. I develop C# using VS2005, and am curious what
features/functionality of Eclipse are better than the VS IDE?

i've been using Eclipse for a while and the only thing that comes to my
mind is the code editor... but the one in vs2k5 is much better than the
previous one... so i'm also curious what's nicer in Eclipse than in VS?

 

[Jon Skeet [C# MVP]]

This response intrigues me. I use Eclipse to review java source code we
use elsewehere within our organization, although I don't edit any of the
java code myself. I develop C# using VS2005, and am curious what
features/functionality of Eclipse are better than the VS IDE?

See http://msmvps.com/blogs/jon.skeet/archive/2005/12/22/79631.aspx

 

[Jon Skeet [C# MVP]]

i've been using Eclipse for a while and the only thing that comes to my
mind is the code editor... but the one in vs2k5 is much better than the
previous one... so i'm also curious what's nicer in Eclipse than in VS?

See my other response for a reference to a longer article - but to my
mind the code editor is the single most important thing in the IDE.
It's where I spend 95% of my time, so even if that were the only thing
better in Eclipse than in VS.NET, that's still a massive item.

As it happens, there are plenty of other things too

 

[SharpCoderMP]

See my other response for a reference to a longer article - but to my
mind the code editor is the single most important thing in the IDE.
It's where I spend 95% of my time, so even if that were the only thing
better in Eclipse than in VS.NET, that's still a massive item.

As it happens, there are plenty of other things too

nice article. as to the code editor - i totally agree with you. it's the
place where i do spend most of my time. but as i said the one shipped
with VS2k5 is a bit batter than the previous one. What i always hated
about the Eclipse was the speed... or rather the lack of it it's so
damn slow. It's great but it's like using #Develop IDE - it's nice when
it comes to the editor thing but in a long run... well you just waste
some precious time waiting for this thing to move on

 

[Jon Skeet [C# MVP]]

nice article. as to the code editor - i totally agree with you. it's the
place where i do spend most of my time. but as i said the one shipped
with VS2k5 is a bit batter than the previous one. What i always hated
about the Eclipse was the speed... or rather the lack of it it's so
damn slow. It's great but it's like using #Develop IDE - it's nice when
it comes to the editor thing but in a long run... well you just waste
some precious time waiting for this thing to move on

It's funny - it seems that some people have a problem and others don't.
For me, Eclipse has always been as fast as Visual Studio - faster, when
you take into account the lack of compile time. The one thing I *do*
tweak is the memory settings, to give the JVM plenty of memory -
perhaps you were experiencing a lot of GC activity?

 

[SharpCoderMP]

It's funny - it seems that some people have a problem and others don't.
For me, Eclipse has always been as fast as Visual Studio - faster, when
you take into account the lack of compile time. The one thing I *do*
tweak is the memory settings, to give the JVM plenty of memory -
perhaps you were experiencing a lot of GC activity?

now i see where is the difference i always rebuild the project prior
to run. i had some problems when i hadn't done that. also, i don't know
why but i always had problems with their IntelliSense thing. It worked
too slow for me and i had no idea why. Maybe it was just my machine?
Never mind. I admit that last time i've been using Eclipse was about a
year ago, so maybe there were some improvements since then. Anyway it's
great IDE but i think that for my current work (beside that it is .net
based ) the VS is better

 

[Christof Nordiek]

2) Eclipse provides a nicer IDE than VS

As I know Eclipse can be used also to develop C#.
You only have to use a C#-Plugin.
See e.g.www.improve-technologies.com/alpha/esharp/

 

[William Stacey [MVP]]

I can't imagin needing to use more edit features then what is available in
VS, but I suppose some would. Plus there is a ton of stuff that folks
probably are not using, but would use if they knew about it. I just figured
out a few days ago that "cw<tab><tab>" is the snippet for
Console.WriteLine() and that made my week. I guess it just comes down to
what you want to write in.

--
William Stacey [MVP]

| Jon Skeet [C# MVP] wrote:
| > See my other response for a reference to a longer article - but to my
| > mind the code editor is the single most important thing in the IDE.
| > It's where I spend 95% of my time, so even if that were the only thing
| > better in Eclipse than in VS.NET, that's still a massive item.
| >
| > As it happens, there are plenty of other things too
| >
| nice article. as to the code editor - i totally agree with you. it's the
| place where i do spend most of my time. but as i said the one shipped
| with VS2k5 is a bit batter than the previous one. What i always hated
| about the Eclipse was the speed... or rather the lack of it it's so
| damn slow. It's great but it's like using #Develop IDE - it's nice when
| it comes to the editor thing but in a long run... well you just waste
| some precious time waiting for this thing to move on

 

[Jon Skeet [C# MVP]]

As I know Eclipse can be used also to develop C#.
You only have to use a C#-Plugin.
See e.g.www.improve-technologies.com/alpha/esharp/

Have you tried it? It's appalling - or at least, it was last time I
tried it. Put it this way - you lose pretty much all the benefits that
Eclipse gives you in terms of refactoring etc.

VS is much better than the above plug-in when developing C# - but
writing Java in Eclipse is better than writing C# in VS.

 

[Jon Skeet [C# MVP]]

I can't imagin needing to use more edit features then what is available in
VS, but I suppose some would.

Here's a really simple example: "Open Resource" and "Open Type" in
Eclipse make it *so* easy to get to a resource/type if you just know
its name - even if there are many resources/types with the same name in
different folders/packages (namespaces).

There's a plugin available for VS which does a similar thing, but it
takes a while to index a large solution.

Then there's all the code generation and refactoring stuff - VS 2005
has only just scratched the surface... read the blog entry for an
example of just how powerful Eclipse's Extract Method can be.

Eclipse just makes the actual coding side a breeze - Visual Studio
keeps interrupting my train of thought, effectively. Now, I dare say
there are plenty of tricks I don't know about VS, but I suspect the
same is also true of Eclipse. The VS team seem to have spent a lot of
effort on designers and the like, whereas the Eclipse team have spent
their energy on the editor itself. As I don't happen to like designers
in the first place, that suits me just fine.