- Not a "replacement"
- Treating them like classes. No smart name resolution.
- Giving every file its own idiom by reflex (what is part of the idiom at hand? what needs to be isolated? is this code reusable? keep in mind that 2nd-order imports aren't imported!)
- Paragraphs (make it private, or think about factoring it better)
- Plato's "perfect forms"
- Modules that make their public words as "unique" as possible and/or that you don't import except only where "used" (i.e. missing the point - idioms should complement each other not fight for land space)
- Idioms designed to be switched in and out of frequently. Use a wordlist.