Since you didn’t actually read it , essentially it says that in large projects where multiple packages depend on a commonly-used utility package, you can’t expect all dependencies to upgrade at once. There have to be different versions of the utility in the same linked binary. And to do this, they include the version in the import statement.
While I wouldn’t go so far as suggesting a change in import syntax, have people thought about the problem of conflicting dependencies in Elm? … More broadly, there’s a lot of experience with package managers wrapped up in the blog post, and I want to share it and make sure we’re learning from other communities’ work.