I do like go, but really this arguments start to be a little unprofessional if you ask me.
All those arguments are fine and correct in small projects or libraries, there go is perfect.
But they really don't hold on big project like docker or containerd.
While it is clear what lines of code does, at a tactical level, it is extremely difficult to follow what happen in the big picture, the strategic level. Where the values comes from and where they go? When? How and why?
Honestly I keep seeing this in all big go project, despite the lack of generics.
Again if you need a small micorservice, use go! It is the best option right now. But I wouldn't bet any big codebase on it.
All those arguments are fine and correct in small projects or libraries, there go is perfect.
But they really don't hold on big project like docker or containerd.
While it is clear what lines of code does, at a tactical level, it is extremely difficult to follow what happen in the big picture, the strategic level. Where the values comes from and where they go? When? How and why?
Honestly I keep seeing this in all big go project, despite the lack of generics.
Again if you need a small micorservice, use go! It is the best option right now. But I wouldn't bet any big codebase on it.