Are you a programmer? What languages?

> Where your code is located on the filesystem is incidental complexity.

Incidental complexity is still complexity to deal with.

It isn't easy for me as a developer to find such and such routine if you've thrown everything into a big bucket named "main".

You also omitted the fact that I didn't only refer to files. I mentioned the size of functions, too. Now functions ARE logical units of code, and if you need to scroll ten screens and names are as vague as "ProcessEvent" (which is not broken down into subroutines), this doesn't speak very well about the overall design.

Thanks for the links - but it's hard not to notice that they both refer to FP languages, however (Erlang and Scala).

I wouldn't step out to judge the quality of an Erlang codebase, because that's not a paradigm I'm well familiar with.

Go, however, doesn't belong to that family. I see no reason why SRP and other oldschool principles wouldn't apply here. I'd be happy if someone told me (that's why I asked at the beginning - "or is that the language"?).

The other commenter (@mod) implied that since the project is experimental, it's done quick and dirty but that's because it's prototyping.

Note that I've never said the author of the project is a sloppy programmer, I only wondered at the code being so messy.