[ingas]

It's only natural that coming from such terrible mess as javascript ecosystem author is trying to solve problems he encountered in past.

I wrote comment to him:

It's only natural that you're trying to find solutions for problems you encountered in past.

But exploring new technology this way leads to absolutely natural mistakes. You're are worring about wrong things.

Dependency management This problem is not (and never was) in such terrible scale as in javascript.

You can forget about this problem while you learn go. I suppose that dep will be released offically when you will really need this.

Asynchronicity I did the same mistake as you: I thought that channels and messages are similar to Actor pattern in Erlang, Akka.

Don't try to think about promises, futures and other abstraction when you programming in go.

In fact, you need learn synchronicity now, golang already asynchronous in its nature.