6 ms·
The Author touches on a lot of nice points, but does not address some of the problems with using Go. Anecdotally, from using Go for a number of projects... As
by chris_va 13y ago
The Author touches on a lot of nice points, but does not address some of the problems with using Go.
Anecdotally, from using Go for a number of projects...
As a rough approximation, I think Go's marginal return tops out at about 1000 lines of code. Past that point, syntactically it is hard to do abstraction (interfaces or generics).
As a result, I use it for scripting but not for larger projects.
What about you all?
- shurcooL 13y agoCompare: https://github.com/shurcooL/Conception-go https://github.com/shurcooL/Conception-go - Go, 7'500 lines https://github.com/shurcooL/Conception https://github.com/shurcooL/Conception - C++, 15'000 lines Which would you rather work with? You can look at the commit activity to see my preference.
- frowaway001 13y agoIf you are rewriting your original code in a new language and only get a 50% reduction, the new language clearly sucks.
- shurcooL 13y agoThey are not feature equivalent, so it's hard to compare directly. That said, excluding code reuse, to me Go feels like 75%-100% of verbosity of C++ without header files. Also, I don't agree with your statement. If it were true, it would mean every language clearly sucks.
- yohanatan 13y agoI think part of his point is that the mere re-write itself should save a huge chunk of that. Quite probably if you were to re-write it in the original language you could still get 25-30% decrease in code size (or more).
- frowaway001 13y agoExactly.
- NateDad 13y agoI work on Juju. It's over 200k lines of Go code. It works just fine. Generics have only been missed in a small handful of places, and nothing at all critical.