On Wednesday, January 11, 2017 at 11:56:16 AM UTC-6, 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:
>
I think a smaller, more-focused pitch might go over better, but I think you
Looking back I can totally see that this is the wrong approach. I'll be
thinking about what project or presentation I can use in lieu of this write
up.
On Fri, Jan 13, 2017, 5:51 AM 'Rupert Smith' via Elm Discuss <
elm-discuss@googlegroups.com> wrote:
> On Friday, January 13, 2017 at 12:49:57 PM
On Friday, January 13, 2017 at 12:49:57 PM UTC, Rupert Smith wrote:
>
> On Thursday, January 12, 2017 at 10:54:12 PM UTC, joseph ni wrote:
>>
>> arrived into the face of anyone who will listen. This revolution needs
>> your emations as much as your cleverness. :-P
>>
>
s/emations/emotions/ - if
On Thursday, January 12, 2017 at 10:54:12 PM UTC, joseph ni wrote:
>
> 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.
>
Yeah, just shove anyone out of the way who disagrees that
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
I've successfully made this pitch. Here were the key points for me:
- no run-time exceptions
- much quicker with much smaller file size
- demo debugger
- simple to add a little elm to existing code wo/ changing workflow/ci
process
That got a trial run which sold all our developers, who in turn
I'll recommend a different approach based on my personal experience with
trying to sell Elm.
Rather than showing a laundry list of technical points, start off with
something that really grabs their attention and gives them a "holy crap"
moment.
Two examples: I gave a meetup talk early last
Nice!
A few notes if you want them:)
Tests are VASTLY easier to write in elm because we have a guarantee of
same-arguments-same-result, which means each piece can be tested
independently. And, like you said, you'll need fewer tests because of the
type system.
You can have higher confidence
On Wednesday, January 11, 2017 at 8:28:01 PM UTC, Ossi Hanhinen wrote:
>
> Nice write-up! As it happens, I recently wrote a collection of thoughts in
> the same vein, and just published it as a blog post:
> http://ohanhi.github.io/why-and-when-of-choosing-elm.html
"What is Elm a poor fit for
On Wednesday, January 11, 2017 at 5:56:16 PM UTC, 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
>
"a lot
Nice write-up! As it happens, I recently wrote a collection of thoughts in the
same vein, and just published it as a blog post:
http://ohanhi.github.io/why-and-when-of-choosing-elm.html
--
You received this message because you are subscribed to the Google Groups "Elm
Discuss" group.
To
Good questions. The target audience would basically be some lead developers
(although I would like to write one for product people too).
I think the last time they figured that adding a whole new language was too
extreme and you could "get the same thing" or at least get close with React
+
Who is your target audience? Are you pitching to a CTO? A Scrum Master? A
Project Manager? A handful of Developers?
Why did the last pitch get turned down.
Those are two important pieces of information to have if you want this one
to be successful.
--
You received this message because you
13 matches
Mail list logo
