One of the main reasons was separation of meta and application layers. Take a look at this doc for a thorough explanation of rationale behind new API.
http://wiki.ecmascript.org/lib/exe/fetch.php?id=es3.1%3Aes3.1_proposal_working_draft&cache=cache&media=es3.1:rationale_for_es3_1_static_object_methodsaug26.pdf -- kangax Sent from my iPhone On Feb 28, 2011, at 9:56 PM, Jason Persampieri <ja...@persampieri.net> wrote: > Just read Angus Croll's post on the new Object properties, 'keys' and > 'getOwnPropertyNames'. > > http://javascriptweblog.wordpress.com/2011/02/28/javascript-object-keys-finally > > It got me thinking... I hadn't noticed until now, but it looks like all of > the new properties (create/preventExtensions/etc) are implemented on Object, > as opposed to Object.prototype. Any insight as to why? It may be just a > personal preference, but I would *vastly* prefer obj.keys() over > Object.keys(obj). > > _jason > -- > To view archived discussions from the original JSMentors Mailman list: > http://www.mail-archive.com/jsmentors@jsmentors.com/ > > To search via a non-Google archive, visit here: > http://www.mail-archive.com/jsmentors@googlegroups.com/ > > To unsubscribe from this group, send email to > jsmentors+unsubscr...@googlegroups.com -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/jsmentors@jsmentors.com/ To search via a non-Google archive, visit here: http://www.mail-archive.com/jsmentors@googlegroups.com/ To unsubscribe from this group, send email to jsmentors+unsubscr...@googlegroups.com
