3 ms·
The biggest thing stopping me from using other compile-to-Javascript languages is that almost none of them fully support async-await. Many of them have some su
by eatonphil 5y ago
The biggest thing stopping me from using other compile-to-Javascript languages is that almost none of them fully support async-await.
Many of them have some support for async/await but few can handle all cases such as async-await within try-catch and so on.
Scala.js async-await is not part of the standard libary I think and has this limitation: https://github.com/scala/scala-async#limitations https://github.com/scala/scala-async#limitations.
Kotlin.js might support async-await but I find their JavaScript documentation so confusing/non-existent I can't tell. But also, Kotlin is too similar to JavaScript already anyway. It doesn't have ML-style pattern matching for example.
The Java-to-JavaScript and C#-to-JavaScript compilers both are too underused as far as I can tell. The latter, Blazor, is too focused on ASP.NET for me to be able to understand if I could write it the way I write React apps.
Elm, ReScript, and other ML/Haskell-influenced languages are too niche even though I'm a big Standard ML fan.
I'm not sure what else there is to look at.
And I really don't want to go back to using promises and callbacks.
- cutler 5y agoClojurescript's core.async is a game changer.