End of Javascript?
As we know, since 1995 when Brendon developed JavaScript in just 10 days he revolutionized the web technology by which we discovered interactive web pages. However, the web pages at that time was not so advanced like we have in 2018. It was not very dynamic, single page react type app. At that time it was more of static web pages with very few and minimal user interactions.
Since then other languages like Java Applets, ActiveX etc. have come along and that is pretty much the history of web. We are now in 2018 and still the only possible language we think of to create a web page is JavaScript. JavaScript is the only language officially supported by the web. But is it really so? Is JavaScript the only possible language to build web pages? Is a technology which was built way back in 1995 still is reliant and feasible enough in terms of performance with such dynamic web pages build daily? We will figure it out in a while.
Comparing the differences in modern era
We need to understand that javascript has changed a lot in 2018 by the time it was originally invented. Today we use javascript not only for web interactivity but also for other many purposes that it serves for eg: build tools, server, mobile devices and so on.

Previously when JavaScript is build there wasnot much processing behind the scenes and we used to write plain simple JavaScript and used to render in page. But in today's world no no no no no. We write JavaScript code it goes through a lot of processing called as transpiling, minification, bundling and many of such advanced transformations and by the time it lands on our browser it is something like above picture.
We have started using JavaScript as in Assembly language. But the fact is JavaScript is not a very good assembly language. To no surprise because to refer to to context to which it was built for. It was never designed to be an assembly language.
Why Javascript is not a good Assembly language?
We need to understand how JavaScript is served in the browser. We write a code, it gets transpiled into a Abstract syntax tree(AST), then it is converted into byte code and then it is run into an interpreter. That was it. These days, along with the above tasks performed we have worked on a lot in optimizing JavaScript. In run time it will start making assumptions and optimization of the code happens so that the code is executed faster. Now this is getting complicated. JavaScript will first parse, compile, optimize, probably re-optimize if the code is not efficient enough then execute and at last garbage collection. Just one thing developers want is the performance of the code to be executed quick and application becomes interactive. But do you thing so much added task in the poor soul of JavaScript will perform better? Definitely not.
So what can be the alternative? In my next article I will be focusing on WebAssembly which can indeed be a killer of JavaScript.
