7 ms·
I think there are a number of reasons why you would. - Built on top of the JVM - Large number of 3rd libraries, i.e. Jackson, Jetty, Spring Boot, Hibernate, e
by dstainer 5y ago
I think there are a number of reasons why you would.
- Built on top of the JVM
- Large number of 3rd libraries, i.e. Jackson, Jetty, Spring Boot, Hibernate, etc.
- Mature, can find support in numerous areas
- Dependency management, I'm sure many will disagree but I've found Maven to work well enough for what i need it to do both from dependency management and releasing
- It's the language I'm the most efficient with and if I'm building something brand new I favor speed of iteration over having to stumble over learning a new language. NOTE: I'd say the same thing about C#, Swift, Javascript, etc. If that either of those were my primary language I'd do the project in that because speed is your friend when starting out.
- jamesfinlayson 5y agoOn the library front too - plenty of companies offer a Java SDK.