When are Javascript datatypes supposed to be declared as object? They slow down execution speed, and produce nasty side effects, so Why is this possible?

According to W3Schools:.asp Also from .asp

When are Javascript datatypes supposed to be declared as object? They slow down execution speed, and produce nasty side effects, so Why is this possible?

According to W3Schools:http://www.w3schools./js/js_numbers.asp Also from http://www.w3schools./js/js_datatypes.asp

• javascript

• 5 What are these nasty side effects of which you speak? – Bucket Commented Jul 7, 2014 at 22:04
• Never heard about any nasty side effects .. care to explain? – Monideep Commented Jul 7, 2014 at 22:06
• 1 Unsubstantiated claim is unsubstantiated.... Also everything in javascript is technically an object... – Ryan Commented Jul 7, 2014 at 22:07
• 1 What would it even look like to declare String, Number and Boolean as Objects? – Pointy Commented Jul 7, 2014 at 22:09
• 1 var x = 123; var y = new Number(123); (x === y) // is false because x is a number and y is an object. I though this was known but as bits said I think this is a legit question I don't think I should be getting minus points for it. Check here w3schools./js/tryit.asp?filename=tryjs_object_number – Dave Commented Jul 7, 2014 at 22:47

2 Answers 2

Numbers, strings and booleans can be both primitives and objects. For example you can create a string which is a primitive, and you can create an other which is an object:

var name = 'John Doe';
var email = new String('[email protected]');

The difference is that objects (in this case email) have a lot of useful string manipulation methods. Because of that objects require more memory than primitives. So it's advised to create only primitive values and make the object conversion only when needed. JavaScript does this automatically. For example:

var name = 'John Doe'; // This is a primitive.
var email = '[email protected]'; // This is an other primitive.

The concatenation of the two is an other primitive:

var to = name + ' <' + email + '>';

However when a method is invoked on the primitive, temporarily email bees an object:

var index = email.indexOf('@');

Because the conversion to object is happening automatically, you don't need to worry about that. Declare your variables as primitives and JavaScript will convert it to an object when needed.

Declaring String, Number and Boolean as object results in:

1. Slow Performance: creating an object via new keyword is always costly and results in slow execution because it sets a lot of properties and performs underlying activities before returning the object instance. For more detail check below link for details on each operation performed by new keyword. https://zeekat.nl/articles/constructors-considered-mildly-confusing.html

2. Nasty side effects: when you declare string, number and boolean as object you can face real issues when trying to pare. eg:

   var x = "Hello";
   var y = new String("Hello");
   console.log (x===y) // false because x is String n y is object 
   
   var x = new String("Hello");
   var y = new String("Hello");
   console.log(x==y); // false because objects can't be pared