On Tue, Oct 25, 2016 at 11:27 AM, 'Rupert Smith' via Elm Discuss < [email protected]> wrote:
> If your 'persistence API' requires the application to behave correctly in > order to not store invalid or maliciously altered data, you cannot > guarantee that. > This actually sounds more like a challenge to be faced rather that a technical impossibility. Maybe some kind of declarative access control embedded in a shared schema could solve this. I do think that these server side responsibilities are not really within > the domain of Elm. Look at what happened with Javascript. Once it got useful in the client people wanted it on the server and then we got Node. We are nowhere near the popularity of javascript and yet, I already see frequent enough questions about using Elm on the server-side. There are two ways to address this: 1. allocating resources to making Elm viable on the server 2. making the server part as small and automatic as possible as to not require much coding. To me, option 2 is much more attractive. -- 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]. For more options, visit https://groups.google.com/d/optout.
