brentonashworth/one — comment on commit c0b8ccd674dccbf9b02b09ffe62bc3bc55894aa0
File:  line 0
By candera:

I don't really understand why we need to do it this way. You comment that we've crossed the line into being a framework, which I know you don't want. Having to have the one.application namespace seems to be at the root of that problem to me. But the only things in there are the config object and a function. Those could be passed around rather than having to specify that they live in a particular namespace. I could see where that might be a bit of a pain, but it seems like the tradeoff might be worth it.

Then again, I've only just looked at this for the first time this morning. Perhaps I'm missing something. Am I off base?