Viewing profile — drewolson

Reviews are very exciting, but seem to be unable to fit the following use case: I want to setup a repo such that a subset of collaborators (or organization members) can merge revie…

Ah, thanks.

Can you reference the part of the proposal that states this? I'm reading the following points: > $GOPATH/src/foo will be imported as foo by non-main package $GOPATH/src/mypkg/p. > …

Am I understanding correctly that this proposal again side steps / ignores pinning dependencies for libraries? To me, this is the biggest current problem in the ecosystem and, as a…

How is this different from godep[1] other than being the root of its own GOPATH and having a different naming convention for the location of vendored dependencies? [1] - https://gi…

Author here. You're right. I removed references to "pure" in the article.

Does jitpack currently support repositories in Github Enterprise?

This whole "framework fatigue" thing is going reductio ad absurdum. Convenience is not bad. _Too_ much convenience traded for opacity is bad. As someone with a Phoenix app running …

I'm confused, you're questioning the author's sincerity in expressing his own enjoyment of pair programming? I deeply enjoy pairing. I know quite a few folks that do as well.

I think the point is, if you write map like this you might as well be using a dynamically typed language in the first place because you're deriving no benefit from the type checker…

Thanks (and thanks to pron). I've updated the post to include a warning against using Thread/sleep in go blocks for "real" code.

Author here. From what I've read/seen, the go blocks are lightweight thread-like processes multiplexed onto a thread pool. You may be correct about using Thread/sleep, ideally I wo…

I noticed you're using tornado but appear to be using the standard (non-evented?) python redis library. Does using this library block tornado's event loop? Did you look at other to…