6 comments

[ 5.1 ms ] story [ 29.3 ms ] thread
Yes, Java got complicated.

It's about time to simplify things (in the java universe & enterprise) and this is a good first effort, all the best!

I honestly find sdkman makes installing and managing basic java tooling a breeze. To me that's a solved problem, it's pretty danged nice.

This goes way beyond that; a whole set of dependencies that are very thoughtfully designed. If they maintain backwards compatibility, as the JDK stdlib does, for essentially ever, I might bite. I've seen a lot of these type of things come and go.

Btw, at first sight it's unclear what the scope of this is. It seems to be one project, but then it's actually multiple smaller libraries and "Latte" is just the organisation? Also is the dependency management not it's own project?
About time.

My biggest gripe with Java has always been the tooling ecosystem, almost every java engineer I know solves this with the attitude of "just use intellij".

No. I won't, I refuse to use that, and I refuse to give a company money just to use a language as efficiently as other languages.

I am very happy to see that there's progress being made here. I wish you the best of luck!

I don't think java itself is the problem, the real problem is the overengineered, hard to debug libraries like spring.
Personally I would just use SDKMan & generate a Maven or Gradle build profile from a getting started page of Spring, Vert.x, Quarkus (or whatever library/framework your main work will be on).. . Many of them have interactive starter pages where you click all the things you think you will need and download the project that builds with a single command.

I don't find Java tooling at all difficult, compared to say Python or JavaScript.. but then again I've been using it for quite a while now so I may not be the best judge