Hi Frank. Good question!
Short answer: no, no really, because the consumer of the component doesn’t care anyway so why should we?
Long answer: I think we’re all kind of used to information flowing in a tree-like shape. In Redux however, pretty much all of our components can have their own light-weight connection to the store, so we don’t end up with these big bundles of information (or “root” components). Thus, a distinction between a component and container becomes redundant. Why would you need to know? If you think an existing component might need something from the store, it will take a couple of lines of code to turn it into a wrapped component and its consumers will be none the wiser. There’s no reason for us to limit connections to the store and having a clear distinction between component and container only makes it harder to convert one to another.