Ahaha, I definitely didn't want to be the only thing preventing Java from being declared completely unjustifiable! I'm not a massive Java user nowadays, but I use it quite regularly.
I guess that within "boring technologies" it has one of largest ecosystems, very good performance and it's quite robust.
By "boring technology" I mean something that has well-understood failure modes, so I don't have think a lot about the tool itself and just focus on the end result.
@elmiko @ruivieira @jmtd To be slightly more serious than the rest of the thread my main concern/issue is that without additional tooling/hacks Java is not especially resource conscientious in containerized environments. With something like go you compile static and throw it on scratch: small and fast and done.
I've got plans to further improve the JVM's behaviour in container environments, hopefully I'll carve out time to work on them in the near future. The problem is partially accounting for other processes (e.g. readiness probes, liveness probes) that might be occasionally launched in the same cgroup, so we can't eat 100% of the memory limit. Gauging what % is tricky
- replies
- 0
- announces
- 0
- likes
- 0