Js Basics Readme

JavaScript is the de facto language of the internet. It's a tool that, once mastered, will allow you to interact with your users via your app in fun and interesting ways. It is a dynamically typed, prototypical, functional programming language. What that exactly means will become more apparent in lessons and through exposure to the language. But here are the basics.


  • Print JavaScript to the console
  • Explain proper use of semicolons and other syntax basics
  • Explain truthy and falsely values

Syntax Basics

Variable Declaration

To make a variable called greeting and set it equal to the string "hello world" in Ruby, we could just write:

greeting = "hello world"

In JavaScript, to declare a local variable (which is almost always what you want to do), you add the keyword var before the variable name, like so:

var greeting = "hello world";

Notice that semicolons are used after variable declaration and after printing information to the console.


As with Ruby, JavaScript gives whitespace no meaning outside of quotation marks.

var greeting =         "hello world";

greeting == "hello world" // Returns true

As in Ruby, tabs enhance readability, but have no special meaning.

var tvShows = {
    "ABC": [
        "The Bachelorette",
        "Grey's Anatomy"
    "FOX": [


Semicolons must be used in some cases, should be used in others, and other times not at all.


Semicolons must be used when two statements are on the same line (this is called statement chaining). In Ruby, you probably didn't see too much statement chaining so here's an example:

fox.reverse!; fox.downcase!
# => "the quick brown fox"

Notice how that semicolon separates the reversal from the down-casing? JavaScript, like Ruby, also requires semicolons when executing two statements on the same line:

var fox = "XOF NWORB KCIUQ EHT";
fox = fox.split("").reverse().join(""); fox = fox.toLowerCase();
// => "the quick brown fox"

Of course, there are exceptions. For instance, when we cover loops, you may notice that the for loop abides by this rule for the first two statements in its argument but not for the last. Not to worry, its syntax will get covered more fully later in the curriculum.


From Codecademy's blog on semicolons:

As we saw above, the semicolon in JavaScript is used to separate statements. However, it can be omitted if the statement is followed by a line break (or there’s only one statement in a {block}). A statement is a piece of code that tells the computer to do something. Here are the most common types of statements:

var i;                        // variable declaration
i = 5;                        // value assignment
i = i + 1;                    // value assignment
i++;                          // same as above
var x = 9;                    // declaration & assignment
console.log("hi");            // function call

All of these statements can end with a ; but none of them must. However, it is a good habit to terminate each statement with a ;.


Semicolons don't follow the closing curly brackets of if, for, while, and switch blocks. For instance, this if statement has no ending semicolon:

var lunchtime = true;

if (lunchtime) {
  console.log("Go get lunch!");

The above-mentioned cases are pretty easy to remember. It's a bit trickier to remember that semicolons follow function expressions but not function declarations.

// function declaration (no semicolon)
function foo() {
    return 'foo';

// function expression (semicolon)
var bar = function() {
    return 'bar';

Also avoid putting semicolons between an ending parenthesis and a beginning curly bracket. In other words, you shouldn't write ) ; {.


Should you get stuck with your semicolon usage (and don't worry, even professional JavaScript developers occasionally forget what goes where), paste your code into a JSLinter, such as JSLint or even JSFiddle. If you click Lint, you'll see a line-by-line evaluation of your semicolon usage and other syntax mistakes.

A slightly more heretical take on semicolons

Semicolons don't really matter in JavaScript. If we're working on a large JavaScript application, chances are we're at least using a minifier that will insert semicolons as appropriate when it processes our code. And lately, it's becoming more popular to compile ECMAScript 6 to ES5 (the JavaScript that most browsers work in) using a tool like Babel. TypeScript is also growing in popularity.

All of this is to say that the long-running semicolon debate in JavaScript is largely overblown at this point. Remember to use semicolons to separate statements that occur on a single line; otherwise, follow the conventions of the team.

Truthy and Falsey Values

We make a lot of assumptions when we write computer programs. In order to make the right assumptions, we need to understand what values in our program evaluate to truthy values and which evaluate to falsey values.

Truthy values:

'all non-empty strings';

'all number strings'; // for example '0', '5', '0.2', '-3.14'

[]; // an empty array

{}; // an empty object

1; // any non-zero number

Falsey values:

0; // the number zero

'';  // an empty string




Printing to the Console

One of the first methods you probably learned in Ruby was puts. JavaScript has an equivalent function called console.log(). Let's take the Ruby code below and turn it into JavaScript code:

puts "JavaScript is also known as ECMAScript"

Well let's change that puts into a console.log:

console.log "JavaScript is also known as ECMAScript"

Now we'll wrap the string in parentheses:

console.log("JavaScript is also known as ECMAScript")

And the icing on the top of this printing-string cake (yum!) is to add a semicolon at the end:

console.log("JavaScript is also known as ECMAScript");

Will the code execute and work without the semicolon? Yes. Is the semicolon best practice? Yes. Should you use semicolons? Also yes.

Well, this code is all fine and dandy but how do you run it? The best, possibly most powerful thing about JavaScript is that all modern browsers know how to run it. All you need to do is make sure you're reading this on either Chrome or Firefox (trust us, the developer tools of these browsers are way better than on Safari). Then open up your browser's console. That's right, just like your computer knows about running a Ruby sandbox when you type irb, your browser runs a JavaScript sandbox when you open up the console.

To open up your browser's console from Chrome, type command + option + J; in Windows, that's ctrl + shift + J. From Firefox, type command + option + K. (If you love writing directly into your terminal, go ahead and install Node. Then type node in your terminal and you'll be in a JavaScript sandbox.)

From your console (or Node terminal), simply type the code above into the prompt and hit return. There, you've run your first JavaScript code!

Open up Chrome and on any tab (even a blank one) right click and select Inspect from the dropdown. From there, select the console tab:


The white space below is your console, a sandbox where you can enter and execute any JavaScript code you want.

Executing JavaScript in Console

View Javascript Basics on Learn.co and start learning to code for free.

Unlock your future in tech
Learn to code.

Learn about Flatiron School's Mission

With a new take on education that falls somewhere between self-taught prodigy and four-year computer science degree, the Flatiron School promises to turn students with little programming experience into developers.

In the six months since the Manhattan coding school was acquired by WeWork, it has spawned locations in Washington, D.C., Brooklyn, and London. Now, WeWork is opening a fourth Flatiron School location, this time in Houston.

Adam Enbar, Flatiron School's cofounder, believes now is the time to grow. "How the world is changing has impacted working and learning in very similar ways. We think education fundamentally is about one thing: enabling people to pursue a better life."

Learn. Love. Code.
Students come to Flatiron School to change their lives. Join our driven community of career-changers and master the skills you need to become a software engineer or a data scientist.
Find Us