Guillermo Rauch - The future of chat

hello everyone my name is Guillermo ouch I'm the creator of Sal KO NGO and the founder of a few companies in the past you can find me on Twitter on tutorial comment / Reggie and I occasionally log about the things that we've been learning at our different projects on Reggie calm my experience in the last five years has done a lot with no Jas

JavaScript and a bunch of open-source frameworks in particular what we focused on early on was making this idea of real-time collaboration and real-time communication namely chat applications very easy to write so our hello world application when we introduced salka do back in the day was basically the most minimal server that would allow you in mid events back and forth and with this event you would be able to create any

sort of application but particularly it was really easy to create a chat application so not only will you be able to emit events you would also be able to broadcast events and then we started adding functionality relating to rooms and subscriptions and things that come up always in the context of messaging systems but something that we noticed over time was a lot of what we enabled very easily also needed a lot of extra functionality a lot of extra patterns

and a lot of new ideas to evolve to become maintainable and scalable in particular when you're working with potentially larger code bases when you're working with larger teams when you're working with applications that are growing beyond the scope of what you had originally planned so this talk is going to be about the main ideas that have changed both in the JavaScript

ecosystem and in our own thinking about how to design this systems not only just chat applications but any sort of very um basically real-time alive application so the changes that we've noticed especially those things that we would do differently if we were starting over again are in basically three key aspects one of them is the definition when we started this project we said we

were going to solve the problem of creating real-time applications no one was quite sure what real time really referred I think everyone had a slightly different idea then the second big change especially over the last year or two has been the emergence of new language features the emergence of really sophisticated build systems that have shaped our code bases differently and then finally and perhaps more importantly the programming model that we use to basically create complex you I

that is constantly updating the way we think about dataflow the way we think about making local changes to the application that are synchronized later on have all changed and I'll discuss these three concepts for which I published 3 s's over 2015 so all of this concepts that I will be discussing today you can expand on by going to this

websites so in terms of the definition one of the most important things to me has been trying to really understand what makes a real-time application real-time or what doesn't make it so and I've come to the conclusion that there are two key aspects that make a real-time application remembering these two ideas throughout the development cycle or even throughout the process of you coming up with a product that you want to make real-time I really great indicators of whether your application will be as successful as fast as