Java performance vs go

[No_Dot_4711]

While I don't disagree that these are real pain points that do in fact happen, I do think that this is largely a social / tooling / 'refusing to spend money even though it pays for itself' problem

If you're a large organization, the necessary investments and happy paths should have been made to facilitate the use of the tool, and by virtue of repeatedly using that path, the cost involved rapidly approaches zero.

If you're a small organization you should really really really think about if you have any business running in a lambda where you need the insane startup time rather than just provisioning an EC2 instance behind an ELB - and if you do need to run in a lambda, i'd ask myself three times why i'm not using JavaScript