That's mostly because nobody cares enough to optimize it, but if you split code into modules so your number of classes, including dependencies, is smaller, then your tests will start quickly. Usually it's dependencies and DI that's the cause of this I think.
Aren't Go's compile times about the same as Java's? Of course it depends on what tooling you use to package the jars.
Aren't Go's compile times about the same as Java's? Of course it depends on what tooling you use to package the jars.