NateDad

22 ms·

181.
by NateDad 11y ago
Gofmt your code. Run errcheck, golint, and go vet, and make sure they don't complain. Run go test -race and make sure it doesn't complain. The best Go code uses built-in types and small interfaces in its APIs. Use interface{} as
182.
by NateDad 11y ago
The lack of generics (and operator overloading and type hierarchies) makes it hard to write grandiose frameworks and all but impossible to write DSLs. I consider this a good thing. You're definitely pushed in the direction of writing
183.
by NateDad 11y ago
This is an awesome point. I feel like programmers using Go care less about the language and more about the process of creating and maintaining a product .
184.
by NateDad 11y ago
Your argument seems to rely on go being the first language someone has learned. Very few people learn go as a first language. Most people I know in the Go community have 10+ years of professional development experience in a variety of th
185.
by NateDad 11y ago
Which is fantastic. Thank you!
186.
by NateDad 11y ago
I really like this proposal. It's basically the best of all current dependency tools - you get reproducibility without needing external configuration files, without hugely long vendor import statements, and still supporting raw go-get
187.
Experimental Dependency Vendoring in Go 1.5(groups.google.com)
174 points by NateDad 11y ago|47 comments
188.
by NateDad 11y ago
There's a million companies using Java, I doubt it'll stop being a good addition to your CV for a long time.
189.
by NateDad 11y ago
Which, uh, has been very successful for java.
190.
by NateDad 11y ago
Yes, but it had the One True Format, which is the only way it can possibly work. I've used a formatter at other jobs in other languages, and you end up having your formatter fighting with everyone else's, unless they're confi
191.
by NateDad 11y ago
The coverage tool is fine. He didn't really explain the problem well. Coverage is per package, and only counts coverage from tests in that package. This makes sense because packages are independent and you can't count on another
192.
by NateDad 11y ago
Really, all I need is gofmt on save, and even that is mostly because I've gotten so used to it that I drop ugly unformatted dreck into my editor and let gofmt clean it up. I worked full time for year without go to definition, mostly be
193.
by NateDad 11y ago
Most Gophers just get tired of defending against the same arguments over and over. At least this guy actually used it for more than an afternoon... Though anyone who says they don't understand go's pointers after that length of ti
194.
by NateDad 11y ago
Sorry, I didn't think of it. I've mentioned it multiple times on HN, but you're right, I should have added a disclosure. Seriously didn't mean to be pushing Juju, I was just surprised at how similar it was to Juju. I ha
195.
by NateDad 11y ago
Very exciting to see an official SDK for AWS. We'll be looking into using this for Juju.
196.
by NateDad 11y ago
Wow, you could totally s/kubernetes/juju/ in this article and still be 100% correct. ( https://jujucharms.com for those not aware of juju)
197.
by NateDad 11y ago
Dell XPS 15. Awesome build quality, very very similar to the Macbook, but slightly cheaper, and still had an option for a hi red screen. And you won't have everyone assuming you're running OSX.
198.
by NateDad 11y ago
This just changes the default, which anyone can do in their OS. If your program breaks when run by someone who set gomaxprocs.. that's a bug in your program.
199.
by NateDad 11y ago
I believe you know what you're talking about, and so are right about what's best (or really, even possible) in rust, but I can still be sad that there's not some magic way to have my cake and eat it too.
200.
by NateDad 11y ago
Nothing gets imported into the namespace when you import a package in go, except a reference to the package itself. The only way to pollute the namespace is to use import "foo" . which is strongly discouraged.
201.
by NateDad 11y ago
Not really? That doesn't seem like it has anything to do with static linking vs. shared libraries. My point was rather that a 3MB executable used to be "large" and now it's not, even if you have 100 of them.
202.
by NateDad 11y ago
Related - Openstack Swift investigating using Go: http://lists.openstack.org/pipermail/openstack-dev/2015-Apri...
203.
by NateDad 11y ago
That's very sad for Rust, because Go's goroutines are amazingly awesome.
204.
by NateDad 11y ago
There was a big push from the linux distros as the maintainers had anneurisms thinking they'll need to rebuild hundreds of Go applications when/if a big bug is found in the Go standard library. They also don't like the idea
205.
by NateDad 11y ago
Source?
206.
by NateDad 11y ago
I've heard that Mark has money put away in the event of an IPO to reward employees for their loyalty (based on seniority), but I have no way of verifying that.
207.
by NateDad 11y ago
Go is way easier to learn than Python for real applications. Python might be easier for your first few times playing with a programming language, but the complexity ramps up fast. There are a lot of features in python - classes, decorators
208.
by NateDad 11y ago
I've been paid to write go for the last two years :). From the articles I've read, a lot of companies are starting to use go for part of their systems.
209.
by NateDad 11y ago
As jerf said - the embedded struct, while exposed to users of the external struct, still has no access to anything in the external struct. You can't override the methods it calls, etc. All the methods it calls will always be its own
210.
by NateDad 11y ago
These are exactly the contortions I'm talking about. You're building a whole history of reboots and states and stuff, and I just build an RPC function call named "Reboot" and move on, without cluttering my API with crud

More ›