Reading through your points, it seems that this is not a pitch but rather a 
list of highly emotional responses to their concerns the first time around.

Alot of your statements are unqualified and comes across to me as being 
weakly backed up or unnecessary personal beliefs: 
"Elm adds far more value than redux such as a type system"
"Elm has been around for about 5 years which is far more stable than the JS 
libraries you would use to replace it"
"People want to work in Elm and would probably would attract more rather 
than less."
"breaking changes to the language they have been pretty minimal and have 
always been large improvements"
"It has basically no cruft."
"I feel the pros far outweigh the cons"
"you'll have less leaving because the front end makes them happy than sob 
into their pillow."   <--- is there something else going on here?

I personally wouldn't go ahead with your second pitch and would strongly 
suggest thinking along the lines of what Charlie said about creating a 
demo/prototype to show these strong points rather than repeating them in 
words.
In fact, that's what I'm doing right now with a work project and with a 
hobby project ( https://github.com/mordrax/cotwelm ). It's to both showcase 
Elm and my skills as a hireable Elm developer. :)


On Thursday, 12 January 2017 04:56:16 UTC+11, Gage Peterson wrote:
>
> I've been wanting to pitch (again) Elm as an alternative to Angular / 
> React + Redux. These are my arguments, please leave some comments:
>
>
> https://gist.github.com/justgage/7de5a2f9e639aec9436aad882fc90446 
>

-- 
You received this message because you are subscribed to the Google Groups "Elm 
Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to