←back to thread

One year after switching from Java to Go

(glasskube.dev)
257 points pmig | 1 comments | 18 Feb 25 16:55 UTC | HN request time: 0s | source
Show context
pjmlp ◴[19 Feb 25 07:30 UTC] No.43099587[source]▶
This looks like one of the typical "we switched from A to B, whithout actually mastering A, so B is alright" kind of posts.

Just on the monitoring part, Go has nothing even close to VisualVM, Flight Recorder, JRebel, VM agents, JMX.

No mention of AOT compilers, JIT caches, and so forth.

replies(9): >>43099839 #>>43099850 #>>43100755 #>>43100882 #>>43101164 #>>43101267 #>>43101355 #>>43102589 #>>43102655 #
zipy124 ◴[19 Feb 25 10:51 UTC] No.43100755[source]▶
I like to think of these problems as having skill ceilings and skill floors like in video games. For large companies often the skill floor is more important than the skill ceiling. If it is easier to start in B than A, even though after years of experience A can be much better, it might still be a better choice to use B.

When you have lots of junior devs, you are more concerned with this upstart time, and I think in this case for example, Java makes it very easy to write poor code, or use poor packages. Yes a master in Java can take advantage of the extremely mature ecosystem with tools like those you have mentioned, but for those who are not experienced like you, they may get better productivity out of what you see as the less powerfull tool.

replies(1): >>43102131 #
ivan_gammel ◴[19 Feb 25 13:50 UTC] No.43102131[source]▶
I do have experience of managing junior teams and I think Java is actually great for them. You only need one senior person to kick off the project and put down the rails - a relatively small effort if you use frameworks instead of bespoke solutions. The team just needs to follow the lead. It is extremely cost efficient and good enough for business in terms of quality/security/performance.
replies(1): >>43104081 #
zipy124 ◴[19 Feb 25 16:36 UTC] No.43104081[source]▶
Another re-phrasing of my comment is that perhaps using Go they do not require the strong senior to kick it off.

Otherwise yes there is always the argument of "they're just using it wrong" etc...

ultimately: ¯\_(ツ)_/¯

replies(1): >>43107420 #
1. ivan_gammel ◴[19 Feb 25 20:44 UTC] No.43107420{3}[source]▶
No. Go is worse simply due to lack of established design patterns. Spring (just like Angular) forces to build things in a certain way and has a lot of reasonable defaults. E.g. CSRF protection is enabled by default in Spring Security. CORS configuration is trivial. Magic? Yes. In Go juniors won’t even think it is necessary and may not figure out that they need a 3rd party library for that (or build it correctly).