3 ms·
One jvm, one way to monitor it, one way to deploy it, one way to upgrade it, one way to recover it. These are some of the things about code that stays inside t
by mey 13y ago
One jvm, one way to monitor it, one way to deploy it, one way to upgrade it, one way to recover it.
These are some of the things about code that stays inside the jvm bounding box that I personally find valuable. It's one of the ways we keep our operational burden down.
It's a high price, but the community has surprisingly deep solutions.
- justincormack 13y agoYes, it took many years, and there are good technical reasons. Other communities rewrite everything in their language for less technically good reasons. It divides all the code into JVM, Posix and Windows (and a few other things) that don't share ideas much; some of the better ideas get ported in one direction or the other, many do not.