In last 5 - 6 years I got chance to work with different client-side technology like JQuery, Knockout, Angular, React etc. Lately, I have been a big advocate of Elm style architecture. While ELM is very restricted, Fable along with ELMish have brought best of both worlds. In my recent project, I'm using Fable-Elmish to create a complex-big client-side application. In this talk, I like to share my experience about why I choose Fable - Elmish and things can be done to scale application.

In the first part of a talk, will explain why TEA (The Elm Architecture) is winning the world, not only for web but for mobile also. It is not a silver bullet but it works and it works for better. We will also look into the reason for choosing Fable-Elmish instead of Elm.

In the second part of a talk, will look into scaling part of a Fable-Elmish application. We will look into two main section readability and performance. Fable-Elmish is having three main components (model-update-view) and will go into details how to scale all three of them . Also, will touch few things that can be taken care while developing applications with Fable for better client-side output and performance.