51–60 of 85 posts
Earlier quoted context omitted.
What is the Go way to implement a generic data structure that can't be trivially realised by wrapping a couple maps and arrays into a struct (without using interface{} and throwing away the safety Go's type system, such as it is, provides)?
You first reconsider your need to make a generic data structure and evaluate on a case by case basis.
Earlier quoted context omitted.
You first reconsider your need to make a generic data structure and evaluate on a case by case basis.
That's a glib answer. You end up with a bunch of duplicated code when you do this.
1. Strict Enforcement of the Google Code Guidelines People who are undisciplined typically don't like discipline when they first encounter it. This doesn't restrict "Coding style" like the author suggests. Coding style and code format shouldn't be conflated. 2. Broken Package Management It's not broken; it's intentionally limited. A "vendor" directory is natively supported by Go to account for this; use Glide or simi…
Go appears to have all but monopolized most of the really exciting / modern Cloud Infrastructure open source projects, and from what I can tell it's going to be a joy to work with given the number of solid web frameworks that exist.
I'm learning Go for working with distributed systems and blockchains, but I'm basically another C#/.NET dude. Apart from the requirements to follow and maintain certain Google Guidelines, I don't mind the language to be honest. Looks neat to me.
Haven't used Go in about a year and change, is Google going to pull an Angular and pull the rug out from under developers for Go 2.0?
I certainly hope not. Can't speak for Angular, but in Python land, ~9 years later, people are still cleaning up the fallout of the changes from Python 2 to Python 3. It wouldn't bode too well for such a young language as Go to go through the same process. My personal observations are that Go is gaining a lot of steam in many places. Announcing that they will break compatibility would make those places strongly recons…
Umm, they've actually announced the opposite. Not sure why you say that.
Earlier quoted context omitted.
That's a glib answer. You end up with a bunch of duplicated code when you do this.
How often do you implement generic data structures in your code? The last time you wrote one was probably in your data structures class.
Effective use of Golang is really teaching yourself to think that anything beyond the language is a useless distraction or some kind of academic pretension. I won't go so far as to call it S________ S_______, but this is textbook Blub.
I disagree with the authors feelings on code formatting. Gofmt is one of the best features of Go, especially when reading others code.
I can agree with gofmt being great, but I can't agree that a simple newline before a brace should be treated as a syntax error. You're forced to use Google's coding style, whether you like it or not. Preferred coding style is subjective, and Go ignores the fact that not everyone works for Google.
Go's most impressive feature to me is it's build ecosystem. Took one of Tyler Treat's experiments and had it running within 30 minutes, no real previous Go build experience. The language itself? Meh. Python/Haskell/C/LLVM IR cover my use cases. I see Go as another wrapper on top of LLVM IR when it is convenient and that is it.