And why is it called ‘Java’-‘Script’? Well, quoting Brendan:
A co-marketing deal between Netscape and Sun.
There were different versions of the standard since it first came out. Today, every modern web browser supports ECMAScript 5.1, and almost everyone supports the latest version, ECMAScript 6. Newer versions are still in the early stages of development.
When using JS, you may find some weird stuff going one, like that NaN (which stands for Not a Number) it’s a… number:
console.log(typeof(NaN)) // number
And NaN it’s not NaN ¿?
console.log(NaN === NaN) // false
And that NaN is an infinite number. Wait… what?
console.log(isFinite(NaN)) // false
And you know what’s the weirdest part? You should expect JS to behave like this! I mean, this is all on the specs.
You can take a look at more weird stuff here:
As I said before, there are some newer versions of the ECMAScript standard on development. But in so early stages that we shouldn’t expect JS to change much anytime soon.
After all, you can already use JS on almost anything: Videogames, AI, Back-End, Front-End, Art, Data Analytics…
And many frameworks and libraries are popping up every day. Svelte has changed the paradigm of website rendering. There’s this thing called CSS-in-JS. You can even write Artificial Neural Networks with Tensorflow.js, develop videogames with Babylon.js, make art using p5.js, automate stuff with NodeJS, even make charts based on .csv files!
Dang that’s broad, right?
It seems like JS is staying with us for a while.