3 ms·
This was my complaint about a go port at my employer. There was an old C++ service that was really slow, so the Go advocate made a bug-for-bug compatible versi
by dekhn 6y ago
This was my complaint about a go port at my employer. There was an old C++ service that was really slow, so the Go advocate made a bug-for-bug compatible version of it in Go, and they migrated over to that system. A lot of work went into touting how awesome it was, until I asked "so, you could have done this in C++, or really any other compiled language?" and they said "yeah, I just wanted to help build enthusiam for go. there's nothing specific about the language that made the resulting system any better"
- acdha 6y agoThere's always a tension between maintaining an existing codebase and trying something new but in that case I'd personally jump on a Go codebase instead of C/C++ in a heartbeat just for the maintainability improvements. There is a meaningful difference between “can a turing-complete language do this?” and “how much time will you spend dealing with avoidable problems or overhead?” and in the case of unsafe languages I find the arguments relatively compelling for picking anything safer to use in practice.
- vmception 6y agoand obviously they can now get hired for Go and you can't. what's the complaint, stop falling for these pedantic loops and win the game
- ravi-delia 6y agoThe complaint is that as long as you're transparently wasting employer resources on a resume gambit you may as well just embezzle anyway and avoid inconveniencing your coworkers.
- dekhn 6y agoNeither that code author nor I has any trouble being employed. I learned go and then stopped using it because (in my field) C++ and Python are what is used most commonly.