Java vs. C#
-
Following up on the previous post, the funny thing is, when I looked at Java years ago, I thought, "what is this crapola?", but when I looked at C#, I liked it. But they're not too different. As usual, I think presentation is everything. I started poking around C# on my own, whereas I was introduced to Java by a couple very annoying, egotistical, opinionated programmers (erm...). It's too bad I couldn't see past my own nose, but I was really biased toward Java because of the people that were expounding its merits were quite without merit themselves. What's your take? Is it easier to go from Java to C#, or from C++ to C#? Is it easier to learn Java after having C# experience? Marc My website
Latest Articles: Object Comparer String HelpersWhen I saw C# for the first time and the "Microsoft evangelist" presented it's new features, I kept repeating "Just like Java". He didn't like my "contributions". I didn't like Java for one reason: performance. From the beggining it was too slow and a black hole for memory (AWT and Swing in particular). They say it is better by now, but I don't care anymore: I have C#. Another annoyance of Java is how it forces you to do the things O.O. I got spoiled from C, Perl and Python; sometimes I just want to do it differently. But I agree with you: it is easier to go from Java to C# and the people/environment where you learn make a big difference. Rui A. Rebelo De perto, ninguém é normal. (At a close look, no one is normal) C. Veloso
-
Following up on the previous post, the funny thing is, when I looked at Java years ago, I thought, "what is this crapola?", but when I looked at C#, I liked it. But they're not too different. As usual, I think presentation is everything. I started poking around C# on my own, whereas I was introduced to Java by a couple very annoying, egotistical, opinionated programmers (erm...). It's too bad I couldn't see past my own nose, but I was really biased toward Java because of the people that were expounding its merits were quite without merit themselves. What's your take? Is it easier to go from Java to C#, or from C++ to C#? Is it easier to learn Java after having C# experience? Marc My website
Latest Articles: Object Comparer String HelpersAfter programming in C++ for years both Java and C# are equally easy. That's why I tell newbies to start with C++ first ... it's all down hill from there. C# is better (and easier to learn) than Java simply because the MS IDE is so superior to anything I've used for Java.
-
Navin wrote: One word: Eclipse[^]. It is a great tool. And I love the name. I'm just surprised that IBM would openly take a jab at Sun Microsystems like that.... Chris LaQuerre eBusiness Projects Leader
-
Following up on the previous post, the funny thing is, when I looked at Java years ago, I thought, "what is this crapola?", but when I looked at C#, I liked it. But they're not too different. As usual, I think presentation is everything. I started poking around C# on my own, whereas I was introduced to Java by a couple very annoying, egotistical, opinionated programmers (erm...). It's too bad I couldn't see past my own nose, but I was really biased toward Java because of the people that were expounding its merits were quite without merit themselves. What's your take? Is it easier to go from Java to C#, or from C++ to C#? Is it easier to learn Java after having C# experience? Marc My website
Latest Articles: Object Comparer String HelpersI started using C# for work almost 2 years ago and I liked it a lot. My masters program is forcing us to use Java though. I have seen and read Java programs before, but I went into the program cold turkey (no real Java experience). I found the transition easy and sometimes a little frustrating. I so badly wanted to find a int i.toString() method, but of course in Java it's Integer.toString(i). Little things like that pop up all the time but once you know the libraries and what's available it is just the same as C# IMO. j
-
Following up on the previous post, the funny thing is, when I looked at Java years ago, I thought, "what is this crapola?", but when I looked at C#, I liked it. But they're not too different. As usual, I think presentation is everything. I started poking around C# on my own, whereas I was introduced to Java by a couple very annoying, egotistical, opinionated programmers (erm...). It's too bad I couldn't see past my own nose, but I was really biased toward Java because of the people that were expounding its merits were quite without merit themselves. What's your take? Is it easier to go from Java to C#, or from C++ to C#? Is it easier to learn Java after having C# experience? Marc My website
Latest Articles: Object Comparer String HelpersIt's not about the language, it's about the libraries and environment with which you use the language. I'll take Visual Studio any day. cheers, Chris Maunder
-
Following up on the previous post, the funny thing is, when I looked at Java years ago, I thought, "what is this crapola?", but when I looked at C#, I liked it. But they're not too different. As usual, I think presentation is everything. I started poking around C# on my own, whereas I was introduced to Java by a couple very annoying, egotistical, opinionated programmers (erm...). It's too bad I couldn't see past my own nose, but I was really biased toward Java because of the people that were expounding its merits were quite without merit themselves. What's your take? Is it easier to go from Java to C#, or from C++ to C#? Is it easier to learn Java after having C# experience? Marc My website
Latest Articles: Object Comparer String HelpersMarc Clifton wrote: whereas I was introduced to Java by a couple very annoying, egotistical, opinionated In my case the next word is zealots. So I suffered from the same bias when it came to actual usage. However I really have no unacceptable issue with the language. The one item I really hate is how the class path is defined. Same code same platform just who ever installed the app server changed the loading order and the code no longer works. I see this all (well more than once a year) the time. The little I have done with C# I do not see this. But then again I am only using it to write testing apps versus anything for production delivery. I do not mind getting old. It beats all the other options that I can think of.
-
Following up on the previous post, the funny thing is, when I looked at Java years ago, I thought, "what is this crapola?", but when I looked at C#, I liked it. But they're not too different. As usual, I think presentation is everything. I started poking around C# on my own, whereas I was introduced to Java by a couple very annoying, egotistical, opinionated programmers (erm...). It's too bad I couldn't see past my own nose, but I was really biased toward Java because of the people that were expounding its merits were quite without merit themselves. What's your take? Is it easier to go from Java to C#, or from C++ to C#? Is it easier to learn Java after having C# experience? Marc My website
Latest Articles: Object Comparer String HelpersI have an assembler, starting with I8080 and Z80, C and C++ background (with jobs done in Fortran, Pascal, Foxbase, VB, Paradox PAL, Perl and plenty of other things along the way) My encounter with Java was hate at first sight. I hated, in no particular order: - the tools - the documentation (sorry guys, nothing compares to MSDN!) - the community attitude (I'm not a M$ lover, but I don't have religious convictions about it either) - the slowness - the garbage collection idea (I still believe that it makes destructors useless and it's a step back in time) - the no-multiple-inheritance-because-you're-an-idiot-and-you'll-misuse-it idea - swing - the fact that it is path-related, one class per file, the class name has to match the file name (and case sensitive when the OS doesn't enforce it!) - the fake portability - the dependency on the run-time engine (no delimitation between language, environment and libraries) My C# experience was nowhere as bad, but a large part of it was that by the that time I accepted that C++ requires too much time to code and a Java/C# like language is the way to go. And it feels a lot like MFC with garbage collection on top, which made is easier for me. C# also has (just IMHO, don't flame me!), a few other advantages: - as a much more recent language it builds on the experience gained since Java came along - you can feel the Borland Delphi influence (I don't like using Pascal, but Delphi was a jewel way ahead of its time. Yes, I know it had bad points as well, but it had so many good ones). I used to work with Borland tools for a very long time (till the M$ monopoly games put too much pressure on them), and I still believe that M$ tools have a long way to go to reach the level of the old Turbo Debugger. I cannot judge for others, but I don't think that the transition to Java would be any different coming from C++ or from C#. As for moving to Java from C#, I think this is a false question. The first language is always harder to learn, as you don't have an experience to build on. And more dangerous as well, without experience you are very likely to accept language mistakes or limitations as being "the truth" and miss the "larger picture". Any time you move from one language to another you use what you already know. Moving between similar languages (C to C++, C++ to C#, C++ to Java) also takes a lot of effort to do it properly (check out "The Principle of the Procrustean Bed in Programming": http://www.codeguru.com/Cpp/misc/samples/basicprogramming/article.php/c
-
Following up on the previous post, the funny thing is, when I looked at Java years ago, I thought, "what is this crapola?", but when I looked at C#, I liked it. But they're not too different. As usual, I think presentation is everything. I started poking around C# on my own, whereas I was introduced to Java by a couple very annoying, egotistical, opinionated programmers (erm...). It's too bad I couldn't see past my own nose, but I was really biased toward Java because of the people that were expounding its merits were quite without merit themselves. What's your take? Is it easier to go from Java to C#, or from C++ to C#? Is it easier to learn Java after having C# experience? Marc My website
Latest Articles: Object Comparer String HelpersI learned Java first and when I first downloaded the C# spec (mid 2000) I couldn't help but laugh at the striking similarity between the two :)
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
-
It's not about the language, it's about the libraries and environment with which you use the language. I'll take Visual Studio any day. cheers, Chris Maunder
Chris Maunder wrote: It's not about the language, it's about the libraries and environment with which you use the language Objection, your honor. No libraries and environments can fix a bad language, and if you have a good language, there is always a possibility to make good libraries and environments later.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
-
It's not about the language, it's about the libraries and environment with which you use the language. I'll take Visual Studio any day. cheers, Chris Maunder
Maybe it is more about packaging (IDE, setups, ease of development-machine-setup) and documentation. In both cases the last time I looked at Java, it was horrible. The last time I looked at C#, it was absolutely fantastic :-) -- Affordable Windows-based CMS for only 99 €: try www.zeta-producer.com for free!