 So we do financial services for startups. And so we have an application which does this financial analysis. We plug into accounting software like 0, and we get insights out of it. I will show you a bit how it works and what was the issue which brought us to want to use web workers. So I might be in a page where we want to do financial analysis of a company. I will pick a organization. So maybe a group of company which has two organizations. We have two loads. We analyze steps. And it will come through. And we'll see some insights for the company. We can change company. We do charts. So same, we get the data from the organization. And for one organization, we'll find analysis of income and expenses, profitability, cash, et cetera. And you can see that, yes, we have three analysis coming. I start taking a bit of time. But we have a second organization which we'll take again sometime. We have different periods. Sometimes other customers want to see a few months. Sometimes they want to see their full history. So I have a full three-year history of a business where we can very quickly analyze. We had only expenses. And until we built a product, then revenue started growing with profitability coming up. The point is to do financial analysis, we want to analyze many things. And so far, we have three on this page. And we started having some slowness with some customers. So we thought about a way to make it faster. And that's where Worker came. So we said we can get the data, calculate all this in the browser, and do many, many calculations. So to do that, we tested our Worker's works. And so I have a page. And the first solution would be to do plenty of calculation in the USUR JavaScript. So I would click, and we see what's happening. The browser is completely locked, which is why Worker's were invented. Because here we have maybe 10 dozen calculations. So these are random, but you get the point. So there are eight things going on, which takes around 10 seconds. In the meantime, the browser was completely locked. Well, if I do the same with Worker, I can select, and it's all going on. So we can imagine the speed and the experience we can provide if we do that for all the analysis we want to do. My base is clear with the rationale. And seeing that is very exciting to me, because I know that we'll be able to do all this super cool calculation very quickly. So to do it again, once it's loading, and it's all being calculated, I can really interact. My user interface is not blocked. And the calculations are going in the background. So if we want to see, here we go, and it works. So another beauty of Worker's is that they are super easy to implement in the font. And I want you to do it. Yes. So to launch a Web Worker, we just create a new Worker. And then we don't pass a function. We pass a URL of a file. Actually, there are two ways of launching Worker's. Either through a URL or through a blob to an aggregation. We went for the URL solution. So you call a Worker. You now have your Worker in your code. And you communicate with message, because it's so asynchronous. So you post a message. You can post an object. And then you listen to the Worker itself to receive a message what's happening and get your response. On the Worker side, you would listen to messages. And once you listen, you can do whatever you want. In our case, when you can see, we call it. So we have many calculations going on and many functions. We didn't want to create one individual file for every potential Worker. Because basically, we have a module, a library, with all the potential calculations. So we want to have always the same. And we call the proper function. So we use in the data that we send itself which function we want to call. And the listeners, so we have a Worker Manager, which will listen to that, execute, and communicate directly with that. So that's to show that it's super easy to implement. A few things which I find interesting also, and which you might like if you want to implement Worker. When, as you're passing a URL, you want to make sure you have data. You want to make sure you have your files available. So here, too. So when we minify and prepare our deployment script, we make sure the workers are separate. As we have a revision, we have a script which makes sure to have this version available for servers. But except that, it works. And another fun fact is that I'm sure when you do calculations, sometimes you love your browser because you do infinite loops. At least I'm guilty of that. I do that. And if you do that in normal, yeah, there is at least someone else. If you do that in your JavaScript, it kills your tab. And you are like, it's annoying to close. When you do an infinite loop in a Worker, you can still close the tab. So I find it quite cool. And I think I will stop here for a few minutes of presentation. Is there any question at this stage? Anyone now wants to use workers? Yeah, I convinced. I increased by 50% the number of people who want to do. Yeah, question. How is the support right now for developers? It's, I would say, all the modern browsers have it. We can check. I think it's pretty good. And in the back, the Worker is basically the exact same JavaScript. So the only thing that you need is the ability to create a Worker, to send a message, and receive a message. And so we see. Yeah, Chrome says that it's there since version 4, so for quite a long time. One more question? Yeah. I'm lucky our customers are using modern browsers, so they don't have counter issues so far. And again, looking at the table, I'm not too scared. And it's a bit to be up. So in a way, if there is, it's not like a consumer website where you need to cater to your customers. In this case, I can say we support this one. And you have to move if you want it. And they are quite up here with the service, so that's fine. Yeah, cool. Thank you very much.