Use nullary objects

[eivindfjeldstad]

Don't allow Object prototype to be modified. Test will fail in IE < 9

[wavded]

nullary objects also remove toString() and valueOf() which means you can't compare values with ==

var object = Object.create(null)
object == 'thingy'
TypeError: Cannot convert object to primitive value

=== will work but i imagine having no Object.prototype anymore is causing issues for others (like in the reference above)

/cc @visionmedia

[tj]

yarg :( silly javascript

[eivindfjeldstad]

An alternative could be to keep a blacklist of properties. Or even attatch the proto after the fact. Like

var obj = Object.create(null);
// parse querystring
obj.__proto__ = {}

Might be bad for performance though

[wavded]

if I may inquire, what was the rationale for using nullary objects?

Object.create(null) is significantly slower than {}, not sure how hot this code path is in this case though:

http://jsperf.com/object-create-proto-after

[tj]

__proto__ is plenty fast enough if we want to go that route, plus @wavded it's definitely much slower but at several million ops/s that doesn't matter

[wavded]

yeah fair enough, i'm cool with __proto__

[eivindfjeldstad]

I have a feeling this is going to come up again and again. As long as Object.prototype is safe, I'm happy.

[wavded]

Yeah I agree

[tj]

0.6.3 has the fix