I think aliasing imports is a nice feature for dealing with conflicts, but otherwise they introduce confusion because in order to know what type something is, you need to first scroll to the top of the file to see the imports, and when looking at API docs or other code samples etc you need to mentally transpose the names in the documentation to what your alias is.  Hence, our preference should be to avoid situations where you need to alias imports, not create situations where you need to alias imports.  Since we control both APIs here, we can easily avoid it.