Things We Love About Java
blog.jetbrains.com
Things We Love About Java
1–10 of 11 posts
Re: Things We Love About Java
#2Re: Things We Love About Java
#3https://blog.joda.org/2018/09/do-not-fall-into-oracles-java-...
Re: Things We Love About Java
#4download link: https://adoptopenjdk.net/
license link: https://adoptopenjdk.net/about.html
Re: Things We Love About Java
#5Java is definitely not free. https://blog.joda.org/2018/09/do-not-fall-into-oracles-java-...
I'm sure Jetbrains more than anybody knows about Java's licensing...
Re: Things We Love About Java
#6Java and Kotlin are both great languages. I do wish it was simple to build / run like Go though. Dealing with gradle is a huge pain. The only reason I use Go over Kotlin for personal projects is that setting up and maintaining a gradle project is quite a chore.
Re: Things We Love About Java
#7Java and Kotlin are both great languages. I do wish it was simple to build / run like Go though. Dealing with gradle is a huge pain. The only reason I use Go over Kotlin for personal projects is that setting up and maintaining a gradle project is quite a chore.
Re: Things We Love About Java
#8Java is definitely not free. https://blog.joda.org/2018/09/do-not-fall-into-oracles-java-...
The article specifically mentions Java 11. I'm sure Jetbrains more than anybody knows about Java's licensing...
Re: Things We Love About Java
#9Java and Kotlin are both great languages. I do wish it was simple to build / run like Go though. Dealing with gradle is a huge pain. The only reason I use Go over Kotlin for personal projects is that setting up and maintaining a gradle project is quite a chore.
Just use Maven. Works very well w/ Kotlin.
Re: Things We Love About Java
#10Earlier quoted context omitted.
Just use Maven. Works very well w/ Kotlin.
Maven is IMO the best choice for Java and Kotlin, but even maven is stupidly complex. It's sort of maddening that all JVM languages seem to suffer from clunky build tooling, though I'm certainly glad that they work as well as they do.
For one of my clients, we created lots of similar microservices, similar setup but slightly differ. What I did was creating a template using maven archetypes so spinning up a new microservice for a new piece of work or simply to try something out or an ad-hoc job is a matter of seconds, so setup time is stopped being a hindrance to start something new.
Also these days there are quite few tooling that supports project generators which can give you a bit of setup to start from.