|
I was wondering, how close are C# and Java, syntax?
Would be Java be "easy" to learn if I know C#?
Archchancellor Ridcully
|
|
|
|
|
Close enough.
Java is 'easy' anyway.
My two cents.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
Agreed. I found Java easy to master. But I would add a suggestion: If want to master Java, focus on JavaFX. JavaFX makes setting up a good user interface easy.
Oh, by the way: the Kotlin language is very close to Java. Kotlin is gaining popularity. Many large organizations are moving from Java to Kotlin, as it is more modern and very powerful. It is especially popular for developers who write apps for Android devices (such as cell phones)
But: I found Kotlin quite difficult to master. It has a much steeper learning curve than Java.
To do Java (including Java for Windows), I would recommend the IntelliJ IDEA IDE. For Kotlin (especially when writing Android apps) I would recommend the Android Studio IDE. The two IDEs are closely related.
Good Luck!
Get me coffee and no one gets hurt!
|
|
|
|
|
Very nice thorough and helpful answer!
(my 2 cents)
Best wishes--
|
|
|
|
|
|
C# is more powerful and is developing faster - my two cents
Nick Polyak
|
|
|
|
|
I did it the other way and found C# to be easy based on my understanding of Java. So I would say you should not find it difficult. There is a great set of tutorials at Java Tutorials Learning Paths[^].
|
|
|
|
|
It's been some years, but when I got a (corporate) Java project, I had to go shopping: Eclipse (IDE), Spring (UI), Struts, Apache (Web server), NetBeans, JBoss (app server), etc. before I could write any code.
c# (Windows; .NET framework) was "no" shopping.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
I had a similar experience. I learned Java first, then C#. For a while I was working with both languages. I had a situation occur with a project in each language that required reading and writing XML. I spent two weeks researching (and experimenting with) the multiple libraries for XML processing in Java before I found one that best fit my needs. In C#, there were only two choices (one for processing the entire DOM and one for streaming) and making the choice was obvious.
The issue was that there were hundreds of Java libraries from multiple sources but only the Microsoft official libraries for C#. This was over two decades ago. Things have changed. Research is more efficient. Both languages have matured and are more stable.
|
|
|
|
|
1996 - James Gosling invents Java. Java is a relatively verbose, garbage collected, class based, statically typed, single dispatch, object oriented language with single implementation inheritance and multiple interface inheritance. Sun loudly heralds Java's novelty.
2001 - Anders Hejlsberg invents C#. C# is a relatively verbose, garbage collected, class based, statically typed, single dispatch, object oriented language with single implementation inheritance and multiple interface inheritance. Microsoft loudly heralds C#'s novelty.
I boldest the key differences to be aware of. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
modified 2-Sep-22 17:46pm.
|
|
|
|
|
Concurrency control in the net framework is far easier to understand and correctly implement. Java implements this via Dykstra's base implementation. The net framework hides this complexity.
|
|
|
|
|
===== The Joke ====>
You
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
|
|
|
|
|
- Generics are different, weaker. The syntax sometimes feels oddly backwards too, eg
public <T> boolean containsAll(Collection<T> c);. foreach loops don't use the foreach keyword, but that takes about 10 seconds to get used to.- Since there are no real delegates, Java tends to use interfaces with a
run method (or equivalent). That also affects how events work. You can use anonymous classes that implement the relevant interface though, you don't have to create a thousand full classes. - Inner classes by default have a reference to a specific instance of their outer class. To get a "plain old inner class", it needs to be a static inner class, which is not a static class. That sounds more confusing than it is.
- Operator overloading doesn't exist. Not even for
String. Avoid == between objects (including String, but also Integer), unless you really meant to compare for reference-equality. And yes, BigInteger arithmetic is pretty painful in Java .. but also pretty efficient actually. BigIntegers in C# only recently approached how efficient they are in Java. - In terms of the framework,
List<T> -> ArrayList<T>, and Dictionary<K, V> -> HashMap<K, V> (some tutorials may mention Hashtable, disregard them). - There are no unsigned integers (except
char but we don't talk about that), which for the most part doesn't matter (many operations are independent of signedness, and there are special methods such as Integer.compareUnsigned to implement the operations that are dependent on signedness) except that Java's byte is signed and you will probably occasionally forget that and get some bugs due to unintended sign-extension.
|
|
|
|
|
Based on the above, can I simply sum this up as:
- TLDR: "Java sucks"
- Long story: "Java sucks big time"
|
|
|
|
|
it is very close. in the beginning, there is a saying that C# steals Java...
diligent hands rule....
|
|
|
|
|
Isn't it commonly known that MS and Sun were arguing about MS' right to develop their Java compiler and market it as Java? MS ended up turning their back to Sun/Java, declaring: OK, we'll forget Java and make something better, then!
According to my taste, MS succeeded; C# is and improvement over Java in several respects. But I have been working for a number of years in environments where any such opinion was highly non-PC.
|
|
|
|
|
my experience: Java components are good at cross platform because JVM. they can run on Linux and UNIX without recompile.
I have a Java component to generate Excel file on UNIX, after I copied it to Linux, it is still working well. amazing to me...
diligent hands rule....
|
|
|
|
|
I know what you mean. Now with Net5 & Net6 it just amazed me how easy it was to execute the app on linux now that most of the frameworks catched up to net5.
sudo apt-get install -y dotnet-runtime-6.0 && \
dotnet MYAPP.dll
Only thing to get used to that you "run" dlls^^
|
|
|
|
|
Which one is preferred by *nix folks?
Java at least has open versions of JDK.
With C# you're a bit stuck in the .Net ecosystem. Not sure if Mono is still a thing anymore.
I guess is python to modern take?
|
|
|
|
|
What do you mean by that? Dotnet5+ was made completely* open source, you can look at it on github GitHub - dotnet/runtime: .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
Well yes but no, there are some other alternative usages for .net with C# iirc there are JVM-C# version, C#-Embedded and some more. But yes you are more or less fixed to .net, but from my point thats fine. Everything I ever imagined I would like to do, I can with C# (in a reasonable frame). Btw, on another point, mono is the runtime for C# when running on linux nowadays, again: if i remember correctly.
|
|
|
|
|
Yep. MS built .NET first around VB, and wanted to bring Java in as one of the languages to compile to MSIL (J++). Since Java was the proprietary property of Sun, Sun sued MS that MS’s cross-licensing with Sun for Java did not allow newer versions of Java to be used, and refused to take MS’ improvements in Java, which MS was glad to share with Sun.
Once the courts ruled in Sun’s favor, combined with Sun’s refusal to cross-license any newer versions of Java (which would have benefitted Sun), MS “end of lifed” J++, and created C# (a play on the ++ of C++). After all, the intent of .NET was and is that any language (as syntactic sugar) can be used because it compiled down to language-agnostic MSIL which then gets compiled at runtime, more efficiently and performant than Java.
Of course, Sun’s intense hatred of MS led Sun to spend money on lawyers instead of innovation. At the same time, they intentionally made hardware changes in each new update to their computer hardware to prevent MS from running Windows on it. MS had a version of Windows NT compiled for Sun Sparc. But Sun’s irrational hatred of MS led them to make sure they would break Windows NT with each new hardware release. There was a good market for the Sun Sparc workstations and servers where buyers preferred Windows NT over SunOS and Solaris, but Sun would rather go out of business than have a win-win with Microsoft.
|
|
|
|
|
At the basic level, they're close. Very close. When it comes to finer nuances, C# got ways to write concise code that Java doesn't (top-level statements, switch expressions to name two examples). There's also some nice syntax sugar in C# that Java doesn't have when it comes to OOP.
But overall, they're REALLY similar. After all, they all inherit the basic C syntax. I switch between C# (my main development language) and C++ (a project of mine is a user-mode driver the binary requirements for which .NET won't fulfil without bending backwards) and the transition isn't too bad. Syntax-wise, Java fits nicely into the same family.
|
|
|
|
|
What is the question-behind-the-question, you autocondimentor you?
Paul Sanders.
If I had more time, I would have written a shorter letter - Blaise Pascal.
Some of my best work is in the undo buffer.
|
|
|
|
|
been some time since did Java, 2012. Learned Java at school/uni, first programming job java. then C# 2013, easy enough curve.
Now C#/.net 2012 vs Java 2012, a lot of programming similarities. But 2022 c#11/.net core and visual studio 2022, lots of little things, Linq.
Java probably got something similar, not sure. Main thing what in Java are you planning on doing, maths, backend, services likly similar cross over.
front end/ui stuff, that more JavaFX vs xaml maybe?#
Languages similar, frameworks stepper curve
|
|
|
|
|
There are similarities because both C# and Java (and you can throw in C++) are all in the C family
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
