I work with Java on a daily basis on a big project for a customer. We serve daily over 50 million requests worldwide, we run in 4 AWS regions.
Java has a bad reputation, which I think is mostly coming from being taught extremely poorly. Besides, it might not be the prettiest language, in my opinion. Moreover, being an old language, it has the burden to carry of some questionable decisions in the language design done in the past.
Having to write modern Java is not bad, in fact it can be way more pleasant than dealing with other "fancier" technologies.
First of all, Java is fast. The JVM implementations are as optimal as they can be, plus the JIT magic does a great job.
In terms of frameworks, Spring is pretty good and it can simplify a lot the development. It comes with everything you need out of the box.
For the downsides, unfortunately the industry is still kind of stuck at Java 1.8. which is really old at this point. In addition, there is a lot of legacy stuff to deal with, like application servers, badly written Java EE projects, etc.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I work with Java on a daily basis on a big project for a customer. We serve daily over 50 million requests worldwide, we run in 4 AWS regions.
Java has a bad reputation, which I think is mostly coming from being taught extremely poorly. Besides, it might not be the prettiest language, in my opinion. Moreover, being an old language, it has the burden to carry of some questionable decisions in the language design done in the past.
Having to write modern Java is not bad, in fact it can be way more pleasant than dealing with other "fancier" technologies.
First of all, Java is fast. The JVM implementations are as optimal as they can be, plus the JIT magic does a great job.
In terms of frameworks, Spring is pretty good and it can simplify a lot the development. It comes with everything you need out of the box.
For the downsides, unfortunately the industry is still kind of stuck at Java 1.8. which is really old at this point. In addition, there is a lot of legacy stuff to deal with, like application servers, badly written Java EE projects, etc.