|
|
|
|
|
by chasote
3030 days ago
|
|
I'm on the side of why don't you just let Evan do his thing? Maybe a big part of why Elm is kind of really awesome already is because it's being developed differently. Just let a cool language develop differently this time! It might turn out to be great. And for people who supposedly have so many lines of an alpha language in production, why are you confused about how Elm is being developed? I'm not even using it, but just an interested follower, and it's been pretty clearly explained how he plans on developing it. A couple highly visible threads here and there (some in quite poor taste too) and you are bound to have been given solid, well thoughout references to why Elm is developed this way. I've seen tons of disclaimers that you are using an alpha language in production at risk. No one was misled. |
|
But honestly to me it seems the elm community wants to have their cake and eat it too. Of course that is not a trait unique to them.
As somebody not involved with elm I mostly get to hear about the language from the marketing side. And it does get advocated as production ready (or as least as production ready as anthingthing else in the js world, to paraphrase some talk) and the alpha status, it being still a young language and use in production at own risk only ever seems to really come up when there is some push back.
E.g. I can't see any mention of being "alpha" or warnings on the elm website, besides the version number indicating it. Instead it says things like "elm guarantees no run time exceptions in practice", but when I go to Github issues, I find several of them, including intentional and accepted ones.
It seems to be a neat language, but for now I'll just stay away from it and let them do their thing.
edit: grammar, wording.