3 ms·
It wasn't mentioned as a criterion, and OpalRuby, Python variants, and Coffeescript all got significant discussion in the article. The ClojureScript omission on
by stijlist 10y ago
It wasn't mentioned as a criterion, and OpalRuby, Python variants, and Coffeescript all got significant discussion in the article. The ClojureScript omission on all the axes other than "superficial similarity to JavaScript" is still pretty glaring.
- tel 10y agoIt was mentioned as a criterion. Actually, multiple: - "Perfect IDE support" when described hinges on types - "Static Optimizability" specifically mentions enjoying type-driven AOT optimizations - "Solving Real Problems" mentions types in the "Refactoring is Painful", "'Non-trivial' abstractions", and, briefly, in "Scala.js Solves Real Problems" Furthermore, all of OpalRuby, Python, and CoffeeScript were explicitly dinged on their failures to have statically analyzed types. But yeah, it does feel like he didn't give ClojureScript as much examination.
- lihaoyi 10y agoIf you read the whole post and didn't come out thinking "types are a surprisingly big deal", I have failed as a writer.