"Ghost Of Christmas Future Taunts Children With Visions Of PlayStation 5"
http://www.theonion.com/article/ghost-of-christmas-future-ta...
There's a project on my plate right now that when I saw the requirements and specs, I immediately thought, wow, Elm in a year from now would be absolutely perfect for this.
But it's just not there yet, so I'm exploring things like Typescript that have the advantage of the Javascript ecosystem beneath it. But I really cannot wait for Elm to be production-ready across the board and not just for specific use cases.
Static type proponents sometimes like to say that unsound type systems that leave escape hatches are of little use.
The truth is that both are somewhat wrong.
Types are a tool. They help catch some errors and help code evolve - even when not completely sound, they still help catch some errors and evolve code.
They also don't understand all correct code, so sometimes they get in the way and when that happens, its important to get them out of the way in a manner that doesn't compromise things too much.
Nothing is black and white, there are only shades of grey.
The example that I was given was C++ and C, but I think TypeScript with it's gradual-typing approach is forced to remain potentially as bad as JavaScript itself - that is, if you're feeling weak and want to "get shit done", you can bypass all the goodness that TypeScript undeniably offers you.
For a language like Elm, the type-system is invariably gonna have your back - a value-proposition I think means a lot more in practice than some self-proclaimed pragmatists realize :)