The efficient use of memory in Go makes it an interesting option for serverless services. There is no comparison in start-up time in the posts - just guessing here also Go might do a bit better.
Also, the initial stack size for goroutines seems to be 2 KB now, not 8 KB ( source <https://golang.org/src/runtime/stack.go> line 7). Huge maps in Go could cause some problems for GC before - at the time it could be improved by partitioning the huge map. Most probably this also is improved in newer versions. Easy(er/ish) packaging and deployment is another plus for Go. Of-course these days it is not that obvious, because most things are containerized. (I have used .NET for almost 14 years until 2015 and have nothing against it) On Thursday, December 17, 2020 at 8:20:57 PM UTC+1 Jeff Mangan wrote: > > > https://alexyakunin.medium.com/go-vs-c-part-1-goroutines-vs-async-await-ac909c651c11 > > Interesting article, only had time to skim but seems to lean towards C#. > > Thoughts? > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/5532a38b-bb71-466b-ae08-d70305ed5353n%40googlegroups.com.
