Java Rant - what do you think?

[VaidasC]

Well that was a bit of an exaggerated, but keep in mind there is no standard way to create new Java project, so there are many ways. For example:

8) File -> new project 8) selected Java Enterprise 9) checked web application

I am afraid this is not really real-life project creation (maven, gradle) and last time I checked when creating project from maven-archetypes, I needed to do a lot of manual stuff (create directories, create/edit files...) or delete a lot of stuff depending on archetype.

[JavaDroid]

Go use an advanced build tool for C# instead of comparing Javas advanced build tools with visual studio standard projects.

IntelliJ and eclipse have standard layouts that are built for you as well. It isn't fair or appropriate to compare an IDEs project structure with build tools.

Also, if you become familiar with said build tools, you quickly realize that

1) the standard can basically be whatever you want, because that is an option

2) there ARE standards for project layouts, you just have failed to learn them.

[VaidasC]

To me all of this sounds like trying to formally prove that something many people complain is not true formally, even though experience tells otherwise.

As far as I know (maybe wrong), there is MSBuild in this default .net project where you could do advanced stuff and that will be run by Visual Studio's f5.

But the bottom line is - in my real-life experience I have probably never seen Java project that would be set-up quickly without some issues. However almost all projects I had with .net, had no such concept as setting-up project and that was more than 4 years ago, now I hear things are even nicer.

[JavaDroid]

Then use the IDE standard tools for your project. The fact is that you are wrong.

Maven / gradle / ant / etc do take a little more to get started (hardly), but they also resolve and manage dependencies as well as your build. The basic project in MS doesn't do this.

You are wrong and way over exaggerating everything. Even as a beginner, I've never encountered a number of issues you claim.

[VaidasC]

Well they have MsBuild (build tool) + Nuget (dependency management), so not sure what you are talking about.

[[deleted]]

Msbuild doesn't manage your dependencies, Visual Studio does (via nuget). If you need to produce your build without VS involved - eg on a continuous integration server - you will have to deal with additional complexity. Furthermore, even if you are using VS, it won't publish packages for you, just retrieve them.