Given the steps done toward registering commands as services and dependency lazy loading, I don't think we should go in this direction.
The only benefit for commands to be ContainerAware is to have very lazy dependencies (loaded only when called) but as of 3.3 we have better alternatives, the best being to make the command a service subscriber.
Actually, as of 3.4 I would consider extending ContainerAwareCommand a bad practice.

It depends on Application from the framework bundle anyway.. so that needs to be stripped; leaving you with implements ContainerAwareInterface + use ContainerAwareTrait bridging class.

You can do that in user land easily. I.e. we might as well deprecate ContainerAwareCommand once core doesnt use it anymore.

@chalasr so should we deprecate it?

@ro0NL FrameworkBundle's Application could also be moved to Console

@gnugat #21623 :) I may reopen, I think we need time for the community to be familiar with 3.3 features and best practices

👎 as is, ContainerAwareInterface is not the future, as explained by @chalasr

Closing it because of the downvotes ... and because @chalasr may reopen a related (but better) proposal in the future. Thanks!