Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Maybe a 100 devs Go is fine, but it gets to be a nightmare as you scale beyond that.

Language abstractions exist to prevent having developers build their own ad-hoc abstractions, and you find this time and time again in languages like Go. You can read the Kubernetes code and see what I mean, they go out of their way to work around some of the missing language features.



Yeah, and that nightmare gets even worse in other languages; one motivation for creating Go was the use of C/C++ by thousands of developers at Google.

Can you link to some of these workarounds? I'm curious to see whether they actually make a lot of difference. In theory (and I have no experience with any software project with more than ten developers working on it), they only made it more difficult by adding cleverness.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: