What about debugging? This is the major pain point for me. I've tried using GDB, but... > GDB does not understand Go programs well. The stack management, threading, and runtime contain aspects that differ enough from the execution model GDB expects that they can confuse the debugger, even when the program is compiled with gccgo. As a consequence, although GDB can be useful in some situations, it is not a reliable deb…
Have you tried out Delve? https://github.com/derekparker/delve I've only used it for simple cases, so I don't know if it helps with your criticisms, but it was designed for Go. I mention this because it seems like many gophers aren't aware of Delve.
Program your next server in Go
21–30 of 384 posts
Re: Program your next server in Go
#22Re: Program your next server in Go
#23You lost me at not being able to navigate your slides with my mouse. That a Go feature?
Re: Program your next server in Go
#24">50% of code base changes every month" I wonder what unit is being counted here. I don't think it's possible to actually review and rethink 50% of what has been created before. That's just not sustainable.
That's an enormous amount of manpower.
Re: Program your next server in Go
#25I love Go. It has become the default Go-To (pun intended) language for me for almost anything that needs to be small and portable. However, I don't see myself writing a full server with it, I would still prefer a dynamic language like Ruby/Python for that and use Go for micro-services CLIs and the rest. For example: Our main application is Rails, it communicates with SOLR as the search index, in between the applicati…
Also to add on this... All of my lambda functions are a thin Node wrapper on top of Go applications. The go application is simply a command line accepting JSON via stdin (from the Node wrapper). It is a Joy to test, you can run it locally/independently etc... [Edit]: Typos fix
Re: Program your next server in Go
#26Re: Program your next server in Go
#27I love Go. It has become the default Go-To (pun intended) language for me for almost anything that needs to be small and portable. However, I don't see myself writing a full server with it, I would still prefer a dynamic language like Ruby/Python for that and use Go for micro-services CLIs and the rest. For example: Our main application is Rails, it communicates with SOLR as the search index, in between the applicati…
Re: Program your next server in Go
#28">50% of code base changes every month" I wonder what unit is being counted here. I don't think it's possible to actually review and rethink 50% of what has been created before. That's just not sustainable.
> 5000+ developers across 40+ offices That's an enormous amount of manpower.
If you add code and revise 50% of it every month, the code base is bound to grow and the share of time spent on maintaining the old code grows as well until development of new code grinds to a halt.
Unless of course there is massive growth in hiring. But that isn't sustainable.
[Edit] Well, I forgot one possibility: Deleting code.
Re: Program your next server in Go
#29">50% of code base changes every month" I wonder what unit is being counted here. I don't think it's possible to actually review and rethink 50% of what has been created before. That's just not sustainable.
> 5000+ developers across 40+ offices That's an enormous amount of manpower.
Re: Program your next server in Go
#30What are some cases where I would choose to write a server in Go instead of in Erlang?
http://20bits.com/article/erlang-a-generic-server-tutorial
That's just ridiculous. Erlang looks like php and python had an unholy child.