Front-end is Elm. No opinionated framework to learn. 95% of Elm apps are code that I write for my features and their UI. It is an adjustment... learning to model as types and functions instead of components. We had some false starts there, but Elm does not overly penalize you for early mistakes.
Back-end is F#. We already had experience with .NET. But frankly, I can't think of a more balanced/practical FP language with a decent supporting ecosystem. Especially now with .NET Core. I looked for something else (b/c of Microsoft's data-collection-by-default), and I would have been game if I found something I liked better.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Front-end is Elm. No opinionated framework to learn. 95% of Elm apps are code that I write for my features and their UI. It is an adjustment... learning to model as types and functions instead of components. We had some false starts there, but Elm does not overly penalize you for early mistakes.
Back-end is F#. We already had experience with .NET. But frankly, I can't think of a more balanced/practical FP language with a decent supporting ecosystem. Especially now with .NET Core. I looked for something else (b/c of Microsoft's data-collection-by-default), and I would have been game if I found something I liked better.