nishantmendiratta

Single Threaded

• One command at a time (under the hood of browser maybe not)

Synchronous

• One at a time and in order.

Invocation

• Calling a function in js by using parentheses ()

nishantmendiratta

If you are looking for a resource where you can learn Javascript in-depth. JavaScript: Understanding the Weird Parts Udemy course is highly recommended.

BUT

If you have a limited amount of time and want to Understand the Weird Parts of Javascript in 35ish minutes. Then tag along and read this post.

In 2015, I gathered all the learnings from the above mentioned Udemy course and created a document out of it. This document includes all the learnings which are the most important parts of Javascript. This document is quite handy and help me revise the complex Javascript concepts. I just want to give back something to the community. So, I will be sharing this document in the form of 6 posts.

---

nishantmendiratta

`#!/usr/bin/env python`

```
print "Hello World"
```

nishantmendiratta

The Problem

Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)

The temptingly easy but ultimately wrong solution:

Alter the port the script talks to from 8000 to 80:

}).listen(80);