Viewing profile — lobster_johnson

Good article about yield_self: https://zverok.github.io/blog/2018-01-24-yield_self.html

Varnish uses GCC to compile VCL into a dynamically loaded library. Not a general-purpose language, but it's done at runtime.

Thanks for the clarification. I saw the readme, and I assumed (wrongly) that each rule just receive a file name. I wonder where you draw the line between a "linter aggregator" and …

Have you looked at golangci-linter [1] at all? It's a competing project that also implement a bunch of linter rules, and was created because gometalinter is too slow. One reason go…

I've not used Berkshelf, but I suspect your problems were related to Chef and the fact that they've built their own dependency system that also interacts with Bundler/RubyGems. Ane…

Thanks for the explanation! The fact that dep parses import statements (as does Glide) is something I've never liked. It means that if you run "dep ensure --add" on something not y…

> Now Cox's solution might indeed be better (though I think it's an overkill ... vgo is actually much, much simpler than dep. The sheer number of words in Russ Cox's series of blog…

Testing and package management aren't mutually exclusive. If you're in a monorepo, all your code evolves in lockstep. A core tenet of versioned package management is to get reprodu…

Here [1] is the "dep ensure -v" output for a project of mine. It takes almost 12 seconds even when there are no changes to the actual file. I don't know why, or whether it's actual…

Every Go project I've used uses git tags prefixed with "v", e.g. v1.0.3. https://github.com/gogo/protobuf https://github.com/olivere/elastic https://github.com/golang/protobuf http…

Nothing yet. The new tools should land in 1.11, but will be an experimental opt-in, with the aim of full support in 1.12.

Cox discusses Cargo here, and why he doesn't like it: https://research.swtch.com/vgo-repro

The vgo proposal explicitly rejects the "Cargo way" [1]. There's no lock file, and the MVS algorithm requires, as far as I recall, that the go.mod file is modified whenever the dev…

Rust/Cargo had the luxury of being a greenfield project that could adopt semver from the beginning, whereas Go made the mistake of starting out, and then going years , without any …

You missed my point; I didn't say it's new, I said it was simpler than it might seem, and that thinking of it as a state machine makes it easier to understand what the core of Kube…

Google uses Borg internally, and Kubernetes is really their third container orchestration system. After Borg came Omega, which was never deployed, but ended up being a test bed for…

I would also argue that Kubernetes is less complex than it seems at first glance. Yes, if you look at all the possible parts, and at the current monolithic codebase, there's a lot …

Disagree. OpenShift and CNCF are arguably exactly that, but Kubernetes itself isn't. It came out of the engineering team at Google, and its technical merit shouldn't be confused wi…

Wonderful novel, though. The book is by the great Friedrich Dürrenmatt, and is basically a deconstruction, as well as a subversion, of the detective novel (in fact, its subtitle is…

J and K are extremely terse, though. They just chose other ASCII symbols that exist on everyone's keyboard.

I meant neuter! I studied German for three years in school, but my brain got its wires crossed there for a second.

At this point gender in most languages has almost nothing to do with the semantic meaning of the words themselves -- biological gender or whatever -- and we might as well call it s…

Sure, it might work. A binary format still has to be parsed , of course, but it would likely be a little more efficient. One question is whether that efficiency gain would be worth…

As someone who uses Go daily and enjoys it a lot, there's definitely an inflection point in many areas where Go's lack of abstraction becomes a pain point. One application I work o…

I've been waiting for something like this! Gometalinter is notoriously inefficient, and it's always bothered me that it runs every linter separately as opposed to parsing the code …