I've already done this. Full stack elm is not a feasable option right now. You can use elm to drive your logic if you want but the amount of boilerplate and overhead from the runtime make it inefficent for a server. For full stack elm, with the server code in elm, youll find yoyrself fighting nodemore than anything else. See the readme of https://github.com/noredink/take-home
On Thursday, January 26, 2017, Peter Damoc <[email protected]> wrote: > > > On Thu, Jan 26, 2017 at 6:40 PM, 'Rupert Smith' via Elm Discuss < > [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Still, its a long way from there to a full stack... >> >> Every journey has to start somewhere. Can you share a set of requirements > for a full-stack? Like, how would a checklist for your must have and nice > to have features would be? > > > > -- > There is NO FATE, we are the creators. > blog: http://damoc.ro/ > > -- > 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] > <javascript:_e(%7B%7D,'cvml','elm-discuss%[email protected]');> > . > For more options, visit https://groups.google.com/d/optout. > -- 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.
