21–30 of 57 posts
Java is stable, has plenty of libraries, lots of tools, is friendly to refactoring, testing, and it is not such a bad language. Just take a look at the tools developed in java by good teams (eclipse, apache, joss, spring and so on..)
Most of these answers don't seem to be written by anyone actually involved in "enterprise" development. Here are our simple reasons: * The JVM is fast. * The JVM can take proper advantage of multiple cores directly (no GIL). * The JVM is efficient compared to other runtimes. * Java is type-safe. * There's a library for everything , and libraries are generally well-documented, unit-tested, and provide stable releases…
The reality is that most enterprise projects are generally so many layers of lasagna code that JVM performance is about 20 down on the list of things to blame for poor performance.
So as a common-denominator for large codebases with average-quality developers it makes sense in the long term, although it's not terribly fun.
There are a plethora of reasons that the enterprise uses Java and many of them are really good reasons but the main reason now is inertia, so many enterprises and vendors are invested in Java that to divest of Java just does not have a good value proposition, given the fact that their has not been a major revolution in languages or run-times, no one has had the stomach to try to move off in a serious attempt. To unde…
No it won't, JVM usage will just shift to wherever the need for massively scalable systems goes. If that domain shifts from in-house enterprise development to SaaS companies like Salesforce, the JVM will still be a top contender for those kinds of projects, wherever they're housed.
Removes some uncertainty around planning maintenance & operational costs. Java developers are plentiful and framework training/certification programs are out there for the 'feel goods'.
Also... turns out, .NET is adopted for the above reasons as well.
Most of these answers don't seem to be written by anyone actually involved in "enterprise" development. Here are our simple reasons: * The JVM is fast. * The JVM can take proper advantage of multiple cores directly (no GIL). * The JVM is efficient compared to other runtimes. * Java is type-safe. * There's a library for everything , and libraries are generally well-documented, unit-tested, and provide stable releases…
Nah. Those are the reasons that an organization would like to list for using Java. But "kls" nailed it above. It's mainly inertia and labor availability at this point. The reality is that most enterprise projects are generally so many layers of lasagna code that JVM performance is about 20 down on the list of things to blame for poor performance.
Statically typed languages are favoured when you're working on a team with 40 other developers and you want the idiotic changes being made 5 desks over to break before they check in, not after you've pulled their changes. Autocomplete also makes life staggeringly easier, as do strong refactoring tools. Not having to deal with memory management is also a big plus. When you put those requirements together you end up wi…
On the other hand, maybe you wouldn't need 40 developers on the project if you weren't building it in Java...
Most of these answers don't seem to be written by anyone actually involved in "enterprise" development. Here are our simple reasons: * The JVM is fast. * The JVM can take proper advantage of multiple cores directly (no GIL). * The JVM is efficient compared to other runtimes. * Java is type-safe. * There's a library for everything , and libraries are generally well-documented, unit-tested, and provide stable releases…
Nah. Those are the reasons that an organization would like to list for using Java. But "kls" nailed it above. It's mainly inertia and labor availability at this point. The reality is that most enterprise projects are generally so many layers of lasagna code that JVM performance is about 20 down on the list of things to blame for poor performance.
... except those are the reasons our organization uses Java.
Unfortunately, it seems like this doesn't fit the narrative that some people want to have about the JVM and Java.
Most of these answers don't seem to be written by anyone actually involved in "enterprise" development. Here are our simple reasons: * The JVM is fast. * The JVM can take proper advantage of multiple cores directly (no GIL). * The JVM is efficient compared to other runtimes. * Java is type-safe. * There's a library for everything , and libraries are generally well-documented, unit-tested, and provide stable releases…
* There are a number of alternative languages to choose from that can interoperate on the JVM (Scala, Clojure, JRuby, ...)