 Hi, my name is Rudraksh. I gave this talk last year at this other JavaScript conference, essentially back in those days I used to do a lot of scientific computing, doing some defense work with the army, doing couple of other projects with other people and this was basically about figuring out how you could use a language like JavaScript for something as, you know, compute heavy as scientific computing and at the end, you know, what we realized was that it's not really such a bad idea after all. Sure, there are some cave-eats, there are some quirks and there are some major problems but at the end of the day it does work out. So, I'm just going to quickly run you through what we did. You know, when you say scientific computing, what really comes to mind? It's stuff like astrophysics, biostatistics, cheminformatics and, you know, it just doesn't stop there. So, you also have some things that are more closer to us than we realize, like computational finance, the stock market, there are some great companies in the U.S. that actually use scientific computing to make better money off the stock market and currently languages that are used heavily in this regard are Python, there's Julia as well that's upcoming, some of you may have attended Shashi's talk yesterday, so that's coming up really well. Now, the thing is that why JavaScript? I mean, what's wrong with Python and R? So, theoretically there's nothing really wrong with them. They're great languages and people have been using them for a while. R's been around for at least 20 years now. Python for about six or seven. But the thing is from what I realize is that they don't have the same advantages that JavaScript does and those are async and that runs everywhere. So, Python, for instance, does have asynchronous extensions. There's tornado that allows asynchronous computing, but it's not something that Guido won't really thought about when he was designing the language. And JavaScript, unlike other languages, runs everywhere. I mean, it runs on cameras, it runs on drones, it runs on the server, it runs inside a browser. Inside the browser, it runs in different contexts. It runs everywhere, unlike Python or R. So, the thing is, it feels like JavaScript's the phone gap for scientific computing. Now, a lot of us hate phone gap. A lot of us really think that phone gap didn't work. But what a lot of us don't realize is that phone gap changed the way people thought about mobile development. I mean, you just know HTML and CSS and JavaScript. And now, lo and behold, suddenly you can write mobile apps. You don't need to learn Objective-C. If you don't know Java, that's cool. You just need to know JavaScript. In the same way, JavaScript has that thing going for it. It can change the way scientific computing is done today. It gives us a powerful experience.