3 ms·
I got started with the Go tour: https://tour.golang.org https://tour.golang.org You'll get a feel for the language constructs. Once you're ready to graduate to
by throwaway894345 6y ago
I got started with the Go tour: https://tour.golang.org https://tour.golang.org
You'll get a feel for the language constructs. Once you're ready to graduate to tinkering with your own stuff, then go install Go: https://golang.org/doc/install https://golang.org/doc/install
Some noted differences from C# (my C# knowledge is 5-10 years out of date, mind you):
* Go is a much simpler language; it lacks classes, inheritance, generics, exceptions, etc--you can be productive in a weekend, conservatively
* Go has a formatter that everyone uses, so everyone's code has the same style
* Go lacks generics, so everyone generally writes in the same imperative way (few personal, creative flourishes)--it's very boring in this regard (which is a feature for many people)
* Go has value types (like C#) but they are much more idiomatic--it also has pointers and other reference types
* Go's interfaces are implicitly satisfied, which is like statically-typed duck typing if you're familiar with any dynamic languages (no need to write `extends IFoo` or whatever, unlike C#)
* Go statically compiles everything by default (the "VM" is compiled into every individual program) so you can just pass around a single compiled artifact
* Go has lightweight threads ("goroutines")
* For web service things, you don't need a Netty or any other web-server in front of your service; the web server is just a library (part of the standard library, in fact) and it is production-grade
Go and C# occupy the same ballpark in terms of performance.
- throwaway894345 6y agoOof, sorry for the formatting. Missed the edit window. One last characterization: Go is like C with a GC, package management(and other sane tooling), and many other rough edges removed.
- lanstin 6y agoPlus an awesome multi-core solution.
- throwaway894345 6y agoPretty sure .Net does fine with multicore, or at least to the extent that it doesn't, it's down to excessive sharing/mutation resulting from OO design patterns (modulo "that's not True OO!" arguments, anyway).