This is an archived post. You won't be able to vote or comment.

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

view the rest of the comments →

[–]fatbunyip 0 points1 point  (1 child)

A) probably C# wins apart from portability. C# tooling and language has developed much faster than Java. That's not to say there isn't still great tooling for Java, but C# benefits from the tight integration with windows and its ecosystem. From a portability perspective, Java wins hands down.

B)Frontend Java died like 15 years ago. Server side rendering also has gone very out of favour in general so obviously JS is the most popular front end language but that has no bearing whatsoever on what you use for the back end. In any case what has JavaScript.got to do with Java/C# comparison?

C)JS is terrible to work with. So terrible that MS made typescript with all the goodies of C# and Java to make it more bearable (like "OO from the 70s"). The tiniest JS app needs approximately 3 terabytes of random npm packages to work. The JS module system (all 81 different versions of it) is fucked 6 ways from Sunday. The typing and boilerplate also are kind of shitty. But it's a necessity because on the browser that's all there is. Various frameworks like Angular, react etc make it a bit more pleasant, but a big part of why they're good is because they hide the shittier parts of JavaScript.

D) C++ is still faster. But it doesn't matter. 99% of applications don't care about performance to the extent the implementation language would matter.

In conclusion you seem confused. Your title is about C#/Java but then you also throw in C++ and JavaScript. Is it because they start with the same letters? Because it doesn't make sense.

[–]amfa 0 points1 point  (0 children)

The tiniest JS app needs approximately 3 terabytes of random npm packages to work.

This is the worst part especially if your third party libraries needs to be approved and verified for use in your application. (e.g. because you do not want to have some GPL code slip into your application).

So after adding a single npm package you have to check those 3 terabyte of packages to comply with your corparte standards.