Ouch, "just sad"... would be interested to hear more!

Even if you can't attend, anything you could write up as either a blog post, a Github issue, anything, would be helpful for getting some discussions going around it at the conference I'm sure.

Some people I've talked to have complained that modules aren't objects, and that throwing away the coupling of types and reuse files is "abandoning 30 years of learning" and that "I don't trust myself to be disciplined"

I think that these arguments are not strong! But what would be useful would be some detailed critical thinking on the topic.

My take is that thinking about where you put multiple dispatch parameterized type matched code components is actually a real challenge. The module structure chosen for a library requires "artful" approaches. Perhaps a good workshop on the topic would yield a guide or an approach to making these decisions? Perhaps a labeling system could be evolved to provide metadata for modules better enabling reuse and promoting discover-ability ? Perhaps static analysis of a code base might be provided that gives recommendations (and assistance) for creating good decompositions and associations?