I wonder how much of this is just that Julia is more composable than most people are used to, and the community hasn't yet developed the patterns and culture th

I wonder how much of this is just that Julia is more composable than most people are used to, and the community hasn't yet developed the patterns and culture that are needed to avoid these kinds of problems. I'm thinking, for example, of the way that Smalltalkers often create parameters with type-evocative names, such as "aString". Or Objective-C with two-letter prefixes to work around lack of namespaces. Or even the Java "EntityAdaptorFactoryFactory" design aesthetic. (Some of you will shudder, and I'm with you, but it did solve real problems that the Java world was facing.) Julia is still a pretty young language, and it's probably only recently that the ecosystem has gotten big enough to hit these problems. Edit: come to think of it, one of the issues that the Java folks were dealing with was lack of composability. :-/