Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

fix: grammar, update times and references #360

Merged
MylesBorins merged 1 commit into from
Dec 20, 2019
Merged

fix: grammar, update times and references #360

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions src/documentation/0002-node-history/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,15 @@
---
title: A brief history of Node.js
description: 'A look back on the history of Node.js from 2009 to today'
authors: flaviocopes, onel0p3z, ollelauribostrom, MylesBorins, fhemberger, LaRuaNa, amiller-gh, ahmadawais, kevjin, keywordnew, karlhorky
authors: flaviocopes, onel0p3z, ollelauribostrom, MylesBorins, fhemberger, LaRuaNa, amiller-gh, ahmadawais, kevjin, keywordnew, karlhorky, bdharrington7
section: Quick Start
---

Believe it or not, Node.js is just 9 years old.
Believe it or not, Node.js is only ten years old.

In comparison, JavaScript is 23 years old and the Web, as we know it (after the introduction of Mosaic), is 25 years old.
In comparison, JavaScript is [24 years old](https://en.wikipedia.org/wiki/JavaScript#Beginnings_at_Netscape) and the Web is [30 years old](https://howoldistheinter.net/).

9 years isn't a very long time in tech, but Node.js seems to have been around forever.
Ten years isn't a very long time in tech, but Node.js seems to have been around forever.

I've had the pleasure to work with Node.js since the early days when it was only 2 years old, and despite the limited information in the wild, you could already feel that it was going to be a huge thing.

Expand All @@ -25,7 +25,7 @@ One key factor that led to the rise of Node.js was the timing. Just a few years

JavaScript engines also became considerably better as many browsers competed to offer users the best performance. Development teams behind major browsers worked hard to offer better support for JavaScript and find ways to make JavaScript run faster. The engine that Node.js uses under the hood, V8 (also known as Chrome V8 for being the open-source JavaScript engine of The Chromium Project), improved significantly due to this competition.

Node.js happened to be built in the right place and right time, but luck isn't the only reason why it is popular today. It introduces a lot of innovative thinking and approaches for JavaScript server-side development that has already helped so many developers.
Node.js happened to be built in the right place and right time, but luck isn't the only reason why it is popular today. It introduces a lot of innovative thinking and approaches for JavaScript server-side development that has already helped many developers.

## 2009

Expand Down