[elm-discuss] Re: Convincing my team that Elm isn't just going to die like CoffeeScript

I'd say that Elm is such an easy thing to learn that I wouldn't worry about hiring Elm devs. If people know React and Redux then they already know the principle of how Elm works, and so learning syntax and how functional programming works is quite easy. I also think No Red Ink hires people new

[elm-discuss] using a compile-to-js workflow with elm-webpack-starter

I have my project set up with elm-webpack-starter, which installs a boilerplate index.html and index.js https://github.com/moarwick/elm-webpack-starter/tree/master/src/static I'm now trying to follow the ports guide http://guide.elm-lang.org/interop/javascript.html which says to compile elm to

[elm-discuss] Convincing my team that Elm isn't just going to die like CoffeeScript

Hey Elmos, I've finally gotten an opportunity to pitch Elm to my fairly large dev team. I feel like I'm prepared to make the case for it against a lot of objections: i.e. how will we learn yet another programming language, do we really need something that never throws exceptions, etc. etc.

Re: [elm-discuss] Re: Support for binary data

Seconding this one - I need to be able to pass a binary file to my backend, which requires the ability to both load the file and attach binary data to a POST request. martin On Wed, Oct 19, 2016 at 2:53 AM, Simon wrote: > My need is to upload PDFs directly to S3. That

[elm-discuss] Re: Embracing out messages

The part that is "more awkward" is in having to write the functions to apply — or even just translate — the out messages from one layer to the next. But, of course, the opportunity to do that work is where the pattern gets its strength, so it's a tradeoff. Other than that, it could probably

[elm-discuss] Re: Embracing out messages

Thanks for writing this up Mark, it seems very clear. It seems like it would be especially good for cases where results of effects need to be applied further up the state tree from where the effect is triggered. Or for cases where you want to examine (and possibly modify) requested effects

[elm-discuss] Re: Interactive maps with Elm 0.17 : recommendation?

You won't find a library because you need access to native code. But I wrote a blog using Ports for 0.16 http://simonh1000.github.io/2015/10/elm-architecture-ports/ On Thursday, 3 November 2016 17:16:08 UTC+1, dedo wrote: > > Relatively simple interactive usage to show markers on a map. > >

Re: [elm-discuss] Send a file via an ajax POST request

(but I don't think that will work until we get binary support as Simon says) On Sat, Nov 5, 2016 at 11:30 AM, Marcus Roberts wrote: > You can pass a string to a POST request, by setting the body: > > body = Http.string someStringValue > > So if you could convert the

Re: [elm-discuss] Send a file via an ajax POST request

You can pass a string to a POST request, by setting the body: body = Http.string someStringValue So if you could convert the binary data into a base64 encoded string you could then pass it as the body of the request. On Sat, Nov 5, 2016 at 9:27 AM, Martin DeMello

Re: [elm-discuss] Send a file via an ajax POST request

Hi guys, I'm the author for FileReader and the shortcoming you note is well known and currently unavoidable. Please add you needs to this thread https://groups.google.com/forum/#!searchin/elm-discuss/blob|sort:relevance/elm-discuss/spr621OlUeo/UQq0rk0dBQAJ as we need to get WebApi

Re: [elm-discuss] Send a file via an ajax POST request

Thanks, I took a look at that, but it loads the file data into elm, where we still have the problem that we cannot attach a binary blob to a POST request. I'm not fully sure, but I think the flow needs to be: 1. Get filename from the input button, in elm. 2. Pass filename to javascript 3. Upload

Re: [elm-discuss] Send a file via an ajax POST request

I've not used it yet, but there's a module for doing that here: https://github.com/simonh1000/file-reader Note you have to enable native modules in your config, and you can't just install it as a package as Elm packages don't allow native code. On Sat, Nov 5, 2016 at 8:27 AM, Martin DeMello