John Yani

> will require all dependencies, even dependencies of just the implementation details, to finish building first. Let's analyze an example. ``` // main.carbon import { PublicInterface } from './PublicInterface.carbon'; new...

> I like namespaces. They allow me to collect free functions with short names that I want to use unqualified into a sub-namespace that can be used where I need...

> Imports only inject the package name into the namespace. i.e., import Math only adds one name, But the combination of "`import Math` and `use namespace Trigonometry` is effectively the...

> This seems to assume both the build system using a language-specific tool to separate the interface from the implementation details (including analyzing and separating dependencies), and the build system...

> it's sometimes nice to put functions into a child namespace instead of having them hanging out in the same scope as a library's classes. You don't have such a...

Let's put it that way: it seems like Carbon at its current design treats a compilation unit (file) as an independent entity. That is, a source file is still treated...

FWIW: I've build this a year ago https://hub.docker.com/r/vanuan/ckan-datapusher/dockerfile

A, wait. I don't see why you would need it: https://hub.docker.com/r/clementmouchet/datapusher/dockerfile Just don't use an image, put the Dockerfile locally. Change this line to build specification by copying the dockerfile...

I think you're supposed to have a single load balancer container in your swarm cluster. This way it'd always go to this container, since there's only one.

Ah, but requests from load balancer would still go to different hosts...