 How many of you here are JavaScript programmers? Most of you. How many of you here are actually good at JavaScript? Or do you do this for jQuery? So how many of you are only jQuery programmers? So that's not that many. That means the rest of you actually think of JavaScript as a full-blown programming language that you actively use. Is that right? You guys write serious code in JavaScript. Your lead is even there. You already know everything. So my way of introduction, actually for that, how many of you came to JS in January? There was a JavaScript conference here in Pune in January. So some of you came for that. I see a bunch of hands over there. Most of you have not heard of JSHOO. Have you ever heard of JSHOO? You don't know what it is. So JSHOO is a JavaScript programming conference. It had three editions over the last year. The first edition was in October last year in Bangalore. The second one was in Pune this January. And the third one was Chennai in February. And now we're coming up to the second edition in Bangalore, which is two weeks from now. So it's October 19th in Virginia. And mainly because it turns out that a lot of people are actually really interested in JavaScript, which was something you couldn't say even a couple of years ago. A couple of years ago it was all about jQuery and making small animations on web pages. It suddenly become more than that. And there's a principle reason for that. Something about JavaScript suddenly became really popular. Who wants to guess? Node.js. Node.js introduced people to an unknown undiscovered potential with JavaScript. And it's made a lot of people sit up and take this language, give the language a second glance and say, what the heck is this? This toy language that is really frustrating to work with because it has so many defects, so many unexpected corners, it suddenly become such a fact of language. And what the heck just happened. And if you keep seeing new streams, like as of yesterday, LinkedIn made an announcement saying they moved from Rails to Node.js. Not everything, but a bunch of the servers. And they say that everything got faster when they did this. And so what the heck just happened. JavaScript has always been known to be a really bad performing language. So this sort of is an interesting time to be looking at JavaScript because the problems in language haven't gone away. They're all there. They're problems that are there to be there forever. Because once you put out a specification and there are people writing code against a specification, you can't say the spec is wrong, you change it. Because code that's been written against a spec must continue to work forever. So it's a question that I'm saying, how do you now deal with this, the fact that you got a language that has a very troubled past but is suddenly considered as being a very, very important language going forward? How do you deal with the fact of this change? This is not how normally languages develop. Normally languages sit in the sidelines until they're mature and then they come out in the foreground. And this is true for most languages. Most languages that you hear of, a lot of people got excited about trains around 2004 onwards. And that was because of Ruby. But Ruby was not known in 2004. Ruby had been invented several years before and it took a long time developing. The same thing with Python. Most people discovered Python programming somewhere around 1998. Now, I'm sure most of you did not know this. But 1998 was the year in which Python became famous as a web development language. And afterwards it was Django that created the arrival of Python. But when was Python itself created? The first version of Python was when? In the case? Somewhere around that, it was 1991. 1991 to 1998 was Python's development cycle before it came up into the language. With JavaScript, there was no such chance. In 1995, it was public in the limelight despite being an unfinished language. And now in 2011 and 2012, we're suddenly discovering the fact that this language is a lot more important than we thought it was. Mainly because it's everywhere. Everybody has a browser that runs JavaScript. And it's a language that you simply cannot ignore. There is nothing else you can do to do programming on the browser. Despite everybody's attempts to kill it or replace it, there's coffee script, there's type script, there's dark... There's BB script, yes. Microsoft's infected with killing JavaScript. None of these have managed or so far managed to replace JavaScript. So it's a language that simply doesn't want to go away. It's just too deeply embedded in the modern day ecosystem. So given this, the interesting question now is what do you do with this? How do you understand JavaScript in the context of where it came from and why it's important? On the one side, there's so much hyperboated. On the other side, there's a whole bunch of flaws with it. So what the heck is going on around here? And that's really what I'm hoping Nanaji will explore. Comparing JavaScript with other languages and putting it in context, so it can make sense about the language of the world. So to also introduce ourselves, I'm with a firm named Haskeek. Zalab and I are from Bangalore. We just came in here for this event. We also did the JS4 event back in January. And in 2010, we did all the conferences here for Docker, HTML5 that looked at HTML5 as an emerging market language. Back then it was not important enough. Now it is obviously commonplace. Everybody uses it. So what we do is organize events like this. Right now we do it every week in a different city. But we do a bunch of conferences for JS4 which is two weeks from now. It's a two-day conference which is entirely about JavaScript. Then two weeks later there's an online and Android call. Which is again going to be two days with the interaction speakers coming in talking about the state of the art with Android.