3 ms·
Amusing that you talk about production support considering Go is by comparison a bit of a joke compared to the JVM. I can get detailed remote metrics through JM
by threeseed 12y ago
Amusing that you talk about production support considering Go is by comparison a bit of a joke compared to the JVM. I can get detailed remote metrics through JMX and introspect running code with Java Agent tools like New Relic or AppDynamics.
I completely get what you mean about Go being simplistic and easier to reason than your typical J2EE app. But remember you don't have to write your Java apps that way. Unfortunately "design patterns" took off a decade ago and ended up dragging Java and many other languages into the complexity quicksand.
I hope Go learns from these lessons as it matures.
- spotman 12y ago"you don't have to write you apps this way" , but that's the point in making , is that the culture and parts surrounding Java, which I end up having to support and debug as part of the job, I don't get to use my time machine to go back and fix it. I'm intimately familiar with the jvm and app dynamics and they do have wonderful tooling. but, without that tooling I would be really paddling upstream. call me old fashioned but I like simple tools, and golang I can profile faster and find bugs sooner. I have supported critical infrastructure on both platforms ( Java for many years , golang for 2) and it is not a hard choice to make for me, even with app dynamics and similar tools.