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?
It's an ecosystem that includes a number of tools, libraries, etc. The organization (include the GitHub org) is called Latte. Each project is a GH repository under that.
The dependency management system is part of the `cli` tool. And the repository management is the `app` project and published to https://app.lattejava.org.
The `cli` tool is the foundation though. It's how projects start, build, run, release, and publish.
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!
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
9 comments
[ 3.3 ms ] story [ 24.3 ms ] threadThis 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.
The dependency management system is part of the `cli` tool. And the repository management is the `app` project and published to https://app.lattejava.org.
The `cli` tool is the foundation though. It's how projects start, build, run, release, and publish.
Hope that helps clarify things.
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 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
Certainly those projects are solid, but I think there is a lot of room for improvement, and that's what I'm working on.