Introduction
Before moving further, let us look at the previous articles of the series,
- Voice of a Developer: JavaScript Data Types - Part One
- Voice of a Developer: JavaScript Objects - Part Two
- Voice of a Developer: JavaScript Engines - Part Three
- Voice of a Developer: JavaScript Common Mistakes - Part Four
- Voice of a Developer: Editors - Part Five
- Voice of a Developer: VSCode - Part Six
- Voice of a Developer: Debugging Capabilities of VSCode - Part Seven
- Voice of a Developer: JavaScript OOP - Part Eight
- Voice of a Developer: JavaScript Useful Reserved Keywords - Part Nine
- Voice of a Developer: JavaScript Functions - Part Ten
- Voice of a Developer: JavaScript Functions Invocations - Part Eleven
- Voice of a Developer: JavaScript Anonymous Functions - Part Twelve
- Voice of a Developer: JavaScript Pure And Impure Function - Part Thirteen
- Voice of a Developer: JavaScript Closures - Part Fourteen
- Voice of a Developer: JavaScript Currying - Part Fifteen
- Voice of a Developer: JavaScript Chaining - Part Sixteen
- Voice of a Developer: JavaScript Array Methods - Part Seventeen
- Voice of a Developer: JavaScript ECMAScript 6 - Part Eighteen
- Voice of a Developer: JavaScript ECMAScript 6 Features v1 - Part Nineteen
- Voice of a Developer: JavaScript ECMAScript 6 Features v2 - Part Twenty
- Voice of a Developer: JavaScript Web Workers - Part Twenty One
- Voice of a Developer: JavaScript JSLint v1 - Part Twenty-Two
- Voice of a Developer: JavaScript JSLint v2 - Part Twenty Three
- Voice of a Developer: XMLHttpRequest API - Part Twenty Four
- Voice of a Developer: Web Storage API - Part Twenty-Five
- Voice of a Developer: Application Cache API - Part Twenty-Six
- Voice of a Developer: Javascript WebSocket - Part Twenty-Seven
- Voice of a Developer: Parse JSON - Part Twenty-Eight
- Voice of a Developer: Save Coding Time With Lodash.js - Part Twenty Nine
- Voice of a Developer: ChakraCore JavaScript Engine by Microsoft - Part Thirty
- Voice of a Developer: JavaScript Web App Performance Best Practices - Part 31
- Voice of a Developer: ECMAScript Promises - Part Thirty-Two
- Voice of a Developer: Browser Runtime - Part Thirty-Three
- Voice of A Developer: JavaScript Unit Test - Part Thirty-Four
- Voice Of A Developer: Decoupling Your Application - Part Thirty-Five
- Voice Of A Developer: Adding WinJS To Your Web App - Part Thirty-Six
JavaScript
Javascript is the language of the Web. This series of articles will talk about my observations learned during my decade of software development experience with Javascript. What mistakes a developer generally makes and what differences they should be aware of.
In computer programming, there are two prominent terms, scalar and vector. I am sure these terms must have brought back memories of our computer science/engineering memories.
Computer science is new in comparison to other science streams like Physics or Chemistry. Many computer science concepts are driven by other streams of science. I find the roots of Vectors in Physics. Physics describes how any quantity is either a vector or a scalar. Let’s look at the differences
Flashback
Physics
| Scalar | Vector |
| Any quantity that can be defined by magnitude (or numerical value) is called a scalar. | Any quantity that can be described by the magnitude and a direction is called vector. |
| Example: Speed is scalar | Example: Velocity is a vector |
![]() |
![]() |
Computer Science
| Scalar | Vector |
| The term comes from linear algebra, where we differentiate between a single number OR value with a matrix. | A vector is a dynamic array, which can hold any object, and you can resize it. It has an index and can be accessed by the iterator |
| A single value | A one-dimensional array |
| Update the value | Add or remove elements |
| Ex- int a = 10; | Ex- var vector = [];
|











Santhakumar MunuswamyPosted Jun 25, 2016, 2:16 AM
Thank you for nice article
Vignesh ManiPosted Jun 20, 2016, 6:45 AM
Nice