Java vs CodeBehind
When comparing Java vs CodeBehind, the Slant community recommends CodeBehind for most people. In the question“What are the best backend web frameworks?” CodeBehind is ranked 36th while Java is ranked 42nd. The most important reason people chose CodeBehind is:
CodeBehind is a modern framework with revolutionary ideas.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Verbosity
It makes it easy to debug and to read code.
Pro Mature ecosystem
The language and all its tools have enough time to age and they've aged well.
Pro Type-safe
It is easier to catch errors sooner.
Pro Modern
CodeBehind is a modern framework with revolutionary ideas.
Pro Code-Behind
Code-Behind pattern will be fully respected.
Pro Under .NET Core
Your project will still be under ASP.NET Core and you will benefit from all the benefits of .NET Core.
Pro Get output
You can call the output of the aspx page in another aspx page and modify its output.
Pro Modular
It is modular. Just copy the new project files, including dll and aspx, into the current active project.
Pro Simple
Developing with CodeBehind is very simple. You can use mvc pattern or model-view or controller-view or only view.
Pro Fast
The CodeBehind framework is faster than the default structure of cshtml pages in ASP.NET Core.
Cons
Con Memory hungry
Running the virtual machine, application server and application itself consumes significant amount of resources.
Con Unnecessarily obtuse and verbose
If you like typing 40 lines of code to open a file, Java is the language for you. If, on the other hand, you’d actually like to get something done, look elsewhere.
Con Oracle
Enough said.
In more detail: Oracle has acquired Java from Sun and continues to surround it with controversy ever since (legendary lawsuit with google, money extortion from the enterprise users etc.).