1ML is a user-friendly surface syntax for System Fω
in the paper's abstract. I think Fω lives inside Scala. But, as the stackexchange article you cite shows, I should have been more careful in my statement.
Scala is complex, and SML is pretty simple. (I haven't studied 1ML beyond the elevator pitch, which claims it's "minimal and uniform".) A very complex language with a large installed base can't offer simplicity.
Even more than being complex, it is also a JVM language. That has both benefits and drawbacks. Interaction with the Java language and runtime brings complexities to it.
Granted, I haven't used Scala since, err, 1.7 days? I think. I liked it, and did a lot of work in it in fact, but more as an alternative to Java.
If I didn't have to worry about compatibility with Java or the proven nature of the JVM, or satisfy sysadmins and management with the orthodox Java-ness of my runtime, I'm not sure I'd pick Scala.
I'd never have left the ML world had it not been for the lack of an ecosystem that's comparable to what the JVM has to offer. And my Scala programs mostly just use ML-like features, but I can't live without all those rich libraries that are lacking in ML.