4 ms·
> because of languages like Java or Go Sounds like you haven't spun up a large project recently :) Anything Maven build times are terrible and Go isn't much be
by e4e78a06 5y ago
> because of languages like Java or Go
Sounds like you haven't spun up a large project recently :) Anything Maven build times are terrible and Go isn't much better once you start bringing in a ton of dependencies and codegen frameworks for stuff like protobuf and dependency injection. Java builds can easily take 30 mins and Go at least 3-4 mins.
Don't even get me started on MacOS Docker IO performance. Every time something gets faster we fill it up with more inefficiency.
- Ancapistani 5y agoOh, that's a good point, and one that I've forgotten about. These days most of my work is in Python, with some Terraform and shell scripting thrown in. In 2019 I was working on JVM projects: both Clojure and Kotlin. The JVM build tooling is painful, even on a very powerful machine. > Don't even get me started on MacOS Docker IO performance. This seems to have gotten much better for me. It sucked for a while with the introduction of the M1, but it seems to have gotten back to about where it was, even when using x86_64 containers. I've been playing with aarch64 containers on my personal M1, and they seem to be significantly faster. I'm expecting (and looking forward to) ARM making big inroads into the SaaS hosting arena. It seems like it would have significant benefits in terms of power consumption at the datacenter level, and with more and more developers moving to ARM (via Apple Silicon), it will only get easier to develop for.
- karmakaze 5y agoI did mention working on Spring projects, which was a monolith that did use Maven. The slow part wasn't Maven or the dependencies, it was the Spring startup with all the dependency injection and filter loading taking most of the 2 minutes. There was also some Thrift generation but again that was rather quick. I would classify this as self-inflicted as I don't believe there's anything intrinsic to what's going on for it to be as slow as it is, only poor implementation of extensibility or other ideas (maybe JPQL, idk).
- sliken 5y agoJust curious, how big is a project that requires a single source file edit to take 3-4 minutes? Do you have a NVMe disk? At least a quad core CPU? I've seen some pretty big projects compile way faster than 3-4 minutes, even with protobufs.