Mint: A new language designed for building single page applications(stackoverflow.blog) |
Mint: A new language designed for building single page applications(stackoverflow.blog) |
[1]: https://262.ecma-international.org/11.0/#sec-abstract-equali...
Elm has great developer experience, but it being a purely functional language leads to some boilerplate code and makes it harder to learn. Also, it's not possible to contribute or influence the language in any meaningful way.
fun increment { next { counter = counter + 1 } }
Something doesn't add up.
The `=` is rebinding, what that mean is the original value doesn't change. If you pass that counter variable somewhere, it has its original value. the `count = counter + 1` here mean that a new memory block is allocated, get a value, and the `counter` in this scope is point to it. The old value in the original memory block won't change.
At least, that's the case of Erlang/Elixir.
Question: When is it safe to throw the old value away?
That totally won't encourage an overwhelming amount of JS transpiled languages.
I do agree that the number of tools and solutions out there for creating web applications is overwhelming at times. I just don't know if this a valid approach, especially when people keep churning out tech to replace old tech instead of improving on said old tech.
We don't need this.
There are the big 3 (react vue angular), there are the old and great (meteor, angularjs, elm, polymer)
Do not want.