NateDad

43 ms·

391.
by NateDad 12y ago
> How do you list all interfaces a give type supports just by looking at it? That question doesn't make any sense. I can write a new interface that an existing type supports and then use that type as that interface. That's the
392.
by NateDad 12y ago
Gophers say idiomatic go. We don't need a fancy shorthand for it (also all the viable possibilities are terrible ;).
393.
by NateDad 12y ago
You don't think people simplify some error handling to fit code on slides?
394.
by NateDad 12y ago
I don't understand. What's wrong with this in the loop? if err != nil { continue }
395.
by NateDad 12y ago
That's not really idiomatic. You should be adding context to the error you return, or a new error.
396.
by NateDad 12y ago
Good lord, that logo's font is horrible. It's impossible to read. Don't use cursive, like ever. And certainly not for your logo.
397.
by NateDad 12y ago
There's no required package manager. By default, your VCS is your package manager. You can write code for a long long time with just the default go tool. Those are optional tools that you can use once you become comfortable with the
398.
by NateDad 12y ago
So, in theory, any particular import path should be stable. There are no "different versions" of the same import path. A different version would be a different path. So, for example, github.com/natefinch/lumberjack is
399.
by NateDad 12y ago
It doesn't matter. I'm not going to start a new project at work in either language. But I might conceivably start one in Python, Ruby, go, JavaScript, java, Scala, or another well-used language.
400.
by NateDad 12y ago
I don't know that I agree with that. Tooling bloat was specifically mentioned, and Go is quite good with respect to that. There's just the one go tool to install, which can be installed just by unzipping a zip file. From there o
401.
by NateDad 12y ago
Go's model is pretty good. This is why there's just a single $GOPATH and every package has exactly one location on disk, so even if 100 dependencies use the same subdependency... you only have to update one spot if it needs a pat
402.
by NateDad 12y ago
FWIW, Go namespaces everything by default, so if you import a package called foo, all types, functions, etc from that package are namespaced by foo, i.e. "foo.whatever" The thing I love about Go's packaging is that your VCS a
403.
by NateDad 12y ago
In Go, the dependencies only matter during development not during deployment. Let the developer hash out what specific version of each library works, and then during deployment, it's all baked into a single statically linked executa
404.
by NateDad 12y ago
Try Go, seriously. There's just the one tool. No package manager, no dependencies... And the code it produces is the same. Just a binary. "Here, have this tool, just run it." It's small, simple, and the community active
405.
by NateDad 12y ago
"modern popular languages that people actually use to write software"?
406.
by NateDad 12y ago
Thank you for the insightful response. I think you're mostly correct here, though there are, of course, subtleties. Other than C and C++, Go is one of the best languages for controlling memory. Not freeing, of course, but making it ve
407.
by NateDad 12y ago
No, just no. You can run versions of go side by side. Plus, go is really backwards compatible, so unless you need to recreate an old binary exactly, you can always just compile with a newer version. You can vendor dependencies with godep t
408.
by NateDad 12y ago
I find it fascinating. I had wondered about the YKK on zippers but never bothered to look it up.
409.
by NateDad 12y ago
Honestly, the problem is not just that the Nest thermostat and smoke detector are expensive... I could (almost) justify spending $200 on a thermostat or smoke detector once . But I have 9 heating zones and approximately 9 rooms that need
410.
by NateDad 12y ago
People who write command line tools that require me to install a runtime make me sad. Also, I thought we'd learned by now that javadoc/doxygen style comments are evil? Comments are most often read in the code in plaintext, so they
411.
by NateDad 12y ago
Anyone who intentionally throws away errors because they "got tired" of checking errors, isn't someone I'd want on my team, and their code is not something I'd want to depend on, regardless of the language. Hopefu
412.
by NateDad 12y ago
> think most of this could be solved easily by either a compiler option or golint rule You mean like errcheck? https://github.com/kisielk/errcheck I'm not sure if it can find spots where people intentionally
413.
by NateDad 12y ago
Why even move to github then?
414.
by NateDad 12y ago
> Go is very, very similar to Java 1.4 Except for multiple return values, easy concurrency, implicit interfaces, real value types, pointers, functions as first class types, closures, no inheritance, no exceptions.... but yeah, other than
415.
by NateDad 12y ago
> those usages are semantically different, and consistently so They're very close to the same syntax, and the fact that they're significantly different just shows again that the CLI is a mess. If they're so different, the
416.
by NateDad 12y ago
I have to agree that not using pull requests is missing out on the best feature of github. It's the social, low-overhead way to contribute to a repo. It seems like it must be possible to hook up a bot to github that watches for pull r
417.
by NateDad 12y ago
What?! If anything, your use of C should make Go's syntax really familiar (aside from putting the name before the type, which doesn't take long to get used to). It's exactly like any other C-like imperative language. C, C++
418.
by NateDad 12y ago
No, it's not controlled by them anymore. Possibly in the early days it was, but now it's much more community controlled. You'll never get exceptions in Go. No one who has used go for a significant period of time wants excep
419.
by NateDad 12y ago
Wait wait wait... no pull requests? There's no way you could just hook up PR's to gerrit? Using github just as a mirror seems to defeat the entire purpose of github, which is to encourage more community members to contribute.
420.
by NateDad 12y ago
The git CLI is a mess. It's inconsistent even within its own commands. For example, sometimes specifying remote and branch is done as "remote/branch" and sometimes as "remote branch". It even uses different w

More ›