3 ms·

As a counter example: As someone that worked for years in .Net and started trying to develop some projects in the Java ecosystem... what a fucking mess. Days o

As a counter example: As someone that worked for years in .Net and started trying to develop some projects in the Java ecosystem... what a fucking mess. Days of work to try and get projects to BUILD. Do I have to use Gradle, Maven, or something else? Which IDE to use? The IDE isn't working with whatever version of Gradle or Maven I'm using. Dependency hell. Restarting my IDE repeatedly, re-downloading dependencies, trawling through the horrible Maven site trying to work out what version of a certain dependency I need. Keeping massive amounts of notes because I'm sure in two weeks I'm going to forget which arcane command I need to keep my Java build environment working. The horrible verbosity of Java making it way harder to read then C#. Realising that there's no standard equivalent of tasks and async and I have to work out which of the 10 3rd party implementations is the "good one" and then realising that the recommended one is again verbose, ugly, and more complex to write and understand than Tasks and Async in .Net. Having to work out which Java runtime environment I need. Having to register on the Oracle website to download their runtime, then finding out that maybe an open source runtime is better, then finding out nothing is supported for ARM macs. Then realising that this runtime means my IDE ends up breaking. Multiply all these problems if you decide to write Scala instead. The Java and JRE environment in general is a huge mess in comparison to Microsoft's .Net platform. .Net "just works." There is no confusion of how to build, what IDE to use, what package manager, everything works together seamlessly. I can get a new engineer setup to write and deploy .Net in minutes. Our company literally has to have three engineers gather around someone's computer for half a day to get a Java or Scala environment working correctly and often it ends up working seemingly by magic, i.e. we can't deterministically understand why it ended up working. Java was actually my first programming language in college but Oracle has radically mismanaged it. I would not recommend it unless you really need some specific library that only exists in the Java ecosystem.

vips7L 5y ago
Oracle has done wonders for Java. It has kept it from languishing like it was under Sun. Most of this just sounds like complaints from someone who doesn't know the ecosystem and doesn't want to learn it. Someone who thinks your choice of IDE matters for a project, when in fact it doesn't. > Keeping massive amounts of notes because I'm sure in two weeks I'm going to forget which arcane command I need to keep my Java build environment working. gradle build mvn package > Having to work out which Java runtime environment I need Do you not have to figure out which version of .net core, .net framework, .net whatever for each project? > Having to register on the Oracle website to download their runtime, brew install openjdk@<YOUR_VERSION> > I can get a new engineer setup to write and deploy .Net in minutes Here's what I do, and it takes 3 minutes: my_package_manager install openjdk_version_i_need my_package_manager install maven my_package_manager install vscode code --install-extension vscjava.vscode-java-pack code /path/to/the/project > recommended one is again verbose, ugly, and more complex to write and understand than Tasks and Async in .Net. This is probably your only valid criticism until Loom is launched.
zvrba 5y ago
I use eclipse. Never had problems with it. As for building, I figured out how to use maven to download dependencies to a separate folder and then I use eclipse features to add jars to the project. (Eclipse has maven plugin, but I couldn't get it to work. Something or else made trouble, so I gave up.) Quite pleasant setup. > Realising that there's no standard equivalent of tasks and async There is: Executor and CompletableFuture.

vips7L 5y ago

Oracle has done wonders for Java. It has kept it from languishing like it was under Sun. Most of this just sounds like complaints from someone who doesn't know the ecosystem and doesn't want to learn it. Someone who thinks your choice of IDE matters for a project, when in fact it doesn't. > Keeping massive amounts of notes because I'm sure in two weeks I'm going to forget which arcane command I need to keep my Java build environment working. gradle build mvn package > Having to work out which Java runtime environment I need Do you not have to figure out which version of .net core, .net framework, .net whatever for each project? > Having to register on the Oracle website to download their runtime, brew install openjdk@<YOUR_VERSION> > I can get a new engineer setup to write and deploy .Net in minutes Here's what I do, and it takes 3 minutes: my_package_manager install openjdk_version_i_need my_package_manager install maven my_package_manager install vscode code --install-extension vscjava.vscode-java-pack code /path/to/the/project > recommended one is again verbose, ugly, and more complex to write and understand than Tasks and Async in .Net. This is probably your only valid criticism until Loom is launched.

zvrba 5y ago

I use eclipse. Never had problems with it. As for building, I figured out how to use maven to download dependencies to a separate folder and then I use eclipse features to add jars to the project. (Eclipse has maven plugin, but I couldn't get it to work. Something or else made trouble, so I gave up.) Quite pleasant setup. > Realising that there's no standard equivalent of tasks and async There is: Executor and CompletableFuture.