5 ms·
I've started experimenting with the Bazel-like https://please.build/ https://please.build/ , which has actual support for incremental builds. I also advocate a
by oftenwrong 5y ago
I've started experimenting with the Bazel-like https://please.build/ https://please.build/ , which has actual support for incremental builds.
I also advocate avoiding a lot of the typical dependencies in the Java ecosystem. There is a lot of bloated garbage that you'll miss less than you might think.
- EdwardDiego 5y agoWhat are the typical dependencies, in your mind?
- oftenwrong 5y agoI should say lots of typical dependencies are fine, but some are common "problem children" or ways to shoot yourself in the foot. The Spring ecosystem comes to mind. With regard to the development cycle, Spring seems to turn things that normally would be compile-time errors into runtime errors. If I've wired up my components incorrectly, I'd prefer to find out sooner rather than later, so as not to waste my time.
- EdwardDiego 5y agoAh yep, thought you might have been referring to Spring, and totally agree on runtime vs. compile time. I've switched to Micronaut of late for that precise reason - all the injection happens at compile time, so far quicker to pick up. Downsides though are that Micronaut sometimes doesn't provide super-helpful error messages - or silently fails to do DI when `micronaut-inject-java` isn't in the dependencies.