loading...
Cover image for January of JavaScript

January of JavaScript

lautarolobo profile image Lautaro Lobo Originally published at lautarolobo.xyz on ・3 min read

It’s January. Time to talk about JavaScript. How was it born? Why is it called like that? Is it really that popular? Let’s find out!

A Little Bit Of History

JavaScript was born in December of 1995 when Netscape announced it’s rollout. The guy behind the work? Brendan Eich, a Computer Scientist working at that time in Netscape. He’s known as the father of JavaScript, because of his titanic work on the language before it’s rollout.

Fun fact: JavaScript was named Mocha, then LiveScript, and finally they changed it once and for all to the name that we all know now.

And why is it called ‘Java’-‘Script’? Well, quoting Brendan:

[…] It was all within six months from May till December (1995) that it was Mocha and then LiveScript. And then in early December, Netscape and Sun did a license agreement and it became JavaScript. And the idea was to make it a complementary scripting language to go with Java, with the compiled language.

A co-marketing deal between Netscape and Sun.

In fact, Oracle acquired Sun Microsystems in 2009, so “JAVASCRIPT” is a trademark of Oracle. How crazy is that?

In 1997, ECMAScript was born. But what is ECMAScript? It’s a standard, a specification of a programming language, published by ECMA (European Computer Manufacturers Association) International. So JavaScript is a dialect of the ECMAScript standard.

That’s right, ECMAScript defines a programming language, and JavaScript is the programming language.

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.

Are you confused yet? To make it simpler, ECMAScript is like the version, and JavaScript is the language itself.

For a more-of-a-timeline of the history of JavaScript, check:

The Weird History of JavaScript

Weird Stuff

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:

Do you know these weird parts of JavaScript?

What’s Next?

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?

So yeah, it’s a smart move to learn JavaScript. It’s used all around the web and even in non-web environments, for good or bad. In fact, from the Stack Overflow Developer Survey of 2019 we can say that it’s the most commonly used programming language. And the top Libraries and Frameworks are also JS-based.

It seems like JS is staying with us for a while.


Hey, thanks for reading until this far! If you are starting your journey on JavaScript, or just want to train yourself a bit, check my #7DaysJS Challenge!

See ya!

Posted on Jan 22 by:

lautarolobo profile

Lautaro Lobo

@lautarolobo

While you read this I'm learning something new. CS ♥️

Discussion

markdown guide