I remember working through Appel's compiler textbook in school, in SML and Java editions side by side, and the SML version was of course laughably more concise. It felt like cheating, because it practically was.
The difference is that I get to use Java at work, and never will be able to use SML, perfection usually fails in mainstream adoption, as proven by the whole worse is better mindset languages.
I rather have Java, C#, C++, Kotlin, Rust,.... with their imperfections to ML, Smalltalk, and Lisp ideas, than hoping for getting the right languages at the workplace.
> Good enough wins. Worse is better rules. Release early... and so on.
None of that applies to this case, where ML is not only a fair bit older than Java, but abides the principle of "worse is better" far more.
> While scheme, standardml and numerous other perfect little languages are mostly just Wikipedia pages now.
Frankly, I'm thankful I work in an environment with creative autonomy and can choose (and create) my own tools, rather than being forced to work with ones I don't particularly care for because they had a large marketing push.
Why do you think ml is on the worse side of the principle when compared to java?
Sml is a superpolished language, very well-defined formally, being a culmination of years of design effort and uniting a family of academia-born languages. It took 40 years of research to release the final version in 1997.
Java is on the industry side of thing: semi-formalized, numerous omissions when created, a bunch of ad hoc ideas, released in 1995. Not sure it took more than 3-4 years to get the first official version out.
"Worse is better" is an extremely misleading phrase. It's supposed to be ironic, not sarcastic. Unfortunately, the authors of "Unix Haters Handbook" exercised terrible judgement used it as a sarcastic pejorative. Now nobody understands what anybody is actually saying when they use it. I mean it in the original sense, where it's basically another way to express "Less is more."
SML is borderline minimalist, it's "worse" because it doesn't try to solve everybody's problems with a bunch of ad hoc language features and a stdlib and formalization larger than the entire legal code of the United States. It's "worse" because it comes with "less". You can't just import solution and start writing AbstractFactoryManager2 garbage. It's not actually worse to anybody but beancounters.
Also, lucky you:-) the logic of software development usually means that beginning with mid-size companies it doesn't make sense to have more than 2 major languages, usually on the boring side.
But... I feel that this will not matter all that much soon
