Re: [elm-discuss] Re: elm first impressions (and frustrations)

That would be amazing. I would settle for having a way to export all the ajax calls from a program (and ports) with what kind of data they expect. So you could say that there can be a post to /path/to/resource with a json of this shape. That alone would let me write a test on the server side (or

Re: [elm-discuss] Re: elm first impressions (and frustrations)

> Just imagine a workflow where you change one model working in the front end and the compiler throws and error that the back-end does not implement what you need. +1 On Mon, 1 Aug 2016 at 09:57 Peter Damoc wrote: > Zach, > > Of course being backend agnostic is an amazing

Re: [elm-discuss] Re: elm first impressions (and frustrations)

Zach, Of course being backend agnostic is an amazing thing. That being said, I would love to have a backend that could be implemented in Elm and one full-stack solution that has perfect impedance match. This way, the data models can be shared between the backend and the front-end and with a

Re: [elm-discuss] Re: elm first impressions (and frustrations)

I think that being backend agnostic was / is a good choice. When I started SquareTarget http://squaretarget.rocks I was able to reach for Erlang/OTP and WebMachine on the backend, which is a stack that I know well and I know how it performs under stress etc. Others have used Ruby, Elixir or

Re: [elm-discuss] Re: elm first impressions (and frustrations)

Hi Neil, Few comments on the issues you've raised: 1. Elm plans to go to the server side too. There are already proof-of-concept that allows one to use Elm server-side and with the advent of 0.18 (next version) we might see official support for that. Also, one could use something like Horizon

Re: [elm-discuss] Re: elm first impressions (and frustrations)

thanks dude. i read a considerable amount more before going sleep last night... checked out the compiler repo (which has a much more clear description of elm - "Elm is a type inferred, functional reactive language that compiles to HTML, CSS, and JavaScript.") and played around with trying to

Re: [elm-discuss] Re: elm first impressions (and frustrations)

it seems like a language combined with a client-side framework... something you might use in place of React and Redux (or Angular or what-have-you). i'm checking it out because i've had some companies i advise ask what i think of it and if they should look into using it. i'm detailing the

Re: [elm-discuss] Re: elm first impressions (and frustrations)

Elm is a programming language. Currently it is for client-side (browser) use only. So there is no server or db persistence layer. "elm-make --output elm.js" compiles your elm program to JavaScript, so that it can be embedded in a web page. You can learn how to use Elm by following this guide

[elm-discuss] Re: elm first impressions (and frustrations)

ok, npm install worked. cloned the todo example, cd into the directory and ran `elm reactor`. opened up http://localhost:8000, see the list of files. clicked on `Todo.eml` and got a blank page. ok, get out of reactor, run `elm-make Todo.elm --output elm.js` and open `index.html`. todo