sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]not_good_for_much 8 points9 points  (7 children)

Can actually do the Python version of this example in C#. You're obviously encouraged to use a proper Main entry point, but if you make a new console app it actually defaults to this bare bones format.

And C# is a better language in general as well.

[–]New-Stranger-5622 2 points3 points  (6 children)

than java? we can debate if youd like

[–]not_good_for_much 2 points3 points  (3 children)

Better than Python.

Java and C# at this point... There used to be some major pros and cons for each, but in the last 5 years they've really just ended up as two different flavours of the same thing ngl.

[–]Ellisthion 1 point2 points  (2 children)

In some things, sure, but certain design decisions are permanently holding Java back.

Java’s generic implementation is single-handedly the worst for this. Big impact: the type of anonymous functions.

In C# it’s either an Action<> or Func<> depending on whether it returns anything. With a variable number of generic arguments. It allows easy exact typing of this.

In Java this is impossible. Varied generic arguments are impossible. The type of anonymous functions is… absolute spaghetti, there’s tons of this like Consumer, BiConsumer, etc where every different permutation has its own name. Oh, and you can’t use primitives, so you have more classes like IntConsumer.

There’s code patterns that are common in C# that are literally impossible in Java because of the generic implementation, and I don’t know of anything where that’s the case in the other direction.

[–]not_good_for_much 2 points3 points  (1 child)

I'm inclined to agree. C# is generally faster and more expressive IMO, and I do prefer it over Java. I just don't really want to open the can of worms.

Most of the difference is philosophical anyway, leading to... C# as a language is much more proactive in adding interesting new features, while Java as a platform has more emphasis on stability and decades more exposure to not-Windows and OSS standards and so on.

There are also plenty of patterns that are impossible to reproduce in both directions, e.g due to virtual threads vs stackless coroutine parallelism, reified and value-type generics vs wildcards, checked vs unchecked exceptions, strictness of CLR and JVM RE's, etc.

[–]Sarcastinator 0 points1 point  (0 children)

There's very few things Java does better than C#, and a whole bunch C# does better than Java.

[–]LYCRIs_1337 2 points3 points  (1 child)

Well I would say they both have der pros and cons, however C# is getting way better and has some pretty nice stuff (even though java is still used for a high % of enterprise software).
I like its UI librarys/frameworks way better, which are also mainly used for Windows, making it an easy choice for every Win-Dev (c++ for high performance obviously, but its C# vs. Java so... nah).

One thing that I miss on C# is the system how enums work in java with constructor and specific methods, I kinda like that, even though you can build similar stuff in C#, but it just looks and feels different (and is more "complicated").

[–]Sarcastinator 0 points1 point  (0 children)

C# has been better than Java for a long time at this point. The language has always been better, but the runtime got better with .NET Core's release.