4 ms·
Maybe? I found Go pretty stifling and ran into corners where I was faced with having to copy/paste a lot, write a code generator, or resort to ditching type saf
by bfrog 4y ago
Maybe? I found Go pretty stifling and ran into corners where I was faced with having to copy/paste a lot, write a code generator, or resort to ditching type safety. None of those options are very satisfying. I know generics are now there so maybe this has changed since I last used it. Good if so! 100kloc go program was fast to compile, but awful to modify.
It was amusing to me that often times the answer in Go to avoiding repeating yourself was creating a code generator though, because the language didn't have the native abilities in macros/generics/meta programming itself to do it.
- aliqot 4y agoLook, I'm not trying to start a holy war, I'm just relating my experience of more than just a toe being dipped in. Find the argument somewhere else.
- bfrog 4y agoSame! I’ve written reasonably large programs in both. Go definitely has a lower learning curve and there’s absolutely value in that and it’s faster compile times. In a team with mixed experience and backgrounds making web or network services? Maybe go is the right way to go. Not everyone wants or is willing to climb the rust learning curve. I do think the quick iteration tapers off though the larger the code base gets due to the points I mentioned.