|
|
|
|
|
by rstarast
1405 days ago
|
|
It seems to address the important problems with Elm, around its overly restrictive project management, by 1. introducing more flexible package management (e.g. you can depend on a fork of a core package, or a private git repo etc.) 2. being open to adding various missing web APIs (e.g. while I'm not sure it's there yet, I expect websockets to make a return, which were dropped with Elm 0.19) 3. generally going for an open development model (even just not having to wait years to fix trivial crippling bugs in the compiler is a step forward...). The other part is that I have a good impression of the person/people behind it and could see it sticking, for whatever that's worth. |
|
Just wanted to add that both websockets and indexed-db is being worked on by members of the community. I'm hopeful we'll have them ready for the 0.2.0 release in December, alongside preliminary nodejs support.
Since the 0.1.0 release, we've added support for local- and session-storage, which was another often-requested feature for Elm.