On Thursday, January 26, 2017 at 8:00:57 PM UTC, Peter Damoc wrote: > > > > On Thu, Jan 26, 2017 at 6:40 PM, 'Rupert Smith' via Elm Discuss < > [email protected] <javascript:>> 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? >
I think what is missing is DB access. I'm doing static Html with Elm server side, but have not gone as far as business logic. Actually you have shown me something very interesting here, because I can see a way that I could very easily start writing business logic in Elm, which would be a nice language to write it in. I can't see myself wanting to do DB access in Elm any time soon though. Partly because I have already solved that very nicely in Java. Java may not be nice but it does have one thing going for it: lots of mature libraries to interface just about anything. I can map my Java data object into Elm (already doing that for the static Elm programs), all I would need to do is add ports for all the data layer operations (CRUD + finder + custom operations) and I could start doing business logic in Elm too. I would need it to run faster though. Its ok for static page generation to be really slow, as I can add a caching layer. I might be better to look at something like Frege (Haskell for the JVM) if I wanted to start writing business logic in a statically typed functional language. -- 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.
