I think the /other directory (as currently implemented) is an antipattern

[cha0s]

Let me start by saying I like the idea of having configuration cleanly in its own folder! I get what the /other directory is trying to do. I've done it in a lot of my own projects (and had to wrestle with --config-location=... a multitude of times)

The problem is that unless you can truly cram everything in there, the meaning is muddled and in my opinion only introduces more cognitive load/confusion. You're asking yourself

• Wait, where is that config again? Is that one of the ones that's temperamental or is it one of the ones in /other?"
• Did something happen to my config for [...]? Where the f... (10 minutes later) oh right, it's in /other...

My take is: consistency is most important and if we can't manage to finesse everything into /other then we should leave the configs as everything expects them to be (and, importantly, as users of X library will expect) to promote the least confusion.

P.S. I think that /other is a bad, meaningless name, but that's tangential

[kentcdodds]

Thanks for sharing your feedback. I appreciate the poll, but I want to make sure that it's clear that this project is a representation of the best way I personally feel to build applications and so even if the entire community disagrees with me on this point, nothing gets into the Epic Stack without me being convinced.

Show me with an example and a pull request. Then try to convince me. Believe me, I've considered alternatives and I'm happy with the way things are now, but I have changed my mind about things in the past so I'm open to ideas.

[cha0s]

Understandable! Never bad to have some data to guide decision making. People seem to not care and like it the way it is.

I don't believe a PR will be any more illuminating than the explanation above, so I'm not going to press the issue.