Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is all explained very nicely in <a href="http://wiki.ecmascript.org/lib/exe/fetch.php?id=es3.1%3Aes3.1_proposal_working_draft&amp;cache=cache&amp;media=es3.1%3arationale_for_es3_1_static_object_methodsaug26.pdf">"Proposed ECMAScript 3.1 Static Object Functions: Use Cases and Rationale" document</a> (pdf) by Allen Wirfs-Brock himself (editor of ES5 spec, and a member of TC39).</p> <p>I would suggest to read all of it. It's pretty short, easily digestible, and gives a nice glimpse of the thought process behind these ES5 additions.</p> <p>But to quote relevant section (emphasis mine):</p> <blockquote> <p>A number of <strong>alternatives API designs were considered</strong> before the proposed API was chosen. In the course of considering alternatives we developed a set of informal guidelines that we applied when considering the alternatives. These guidelines are:</p> <ul> <li>Cleanly <strong>separate the meta and application layers</strong>.</li> <li>Try to minimize the API surface area (i.e., the number of methods and the complexity of their arguments).</li> <li>Focus on usability in naming and parameter design.</li> <li>Try to repeatedly apply basic elements of a design.</li> <li>If possible, enable programmers or implementations to statically optimize uses of the API.</li> </ul> <p>[...]</p> <p>Here are some of the alternatives that were considered that lead to the selected design.</p> <p>The obvious initial idea, following the example of the already existing standard method Object.prototype.propertyIsEnumerable, was to add additional “propertyIs...” query methods on Object.prototype for the other attributes and a parallel set of attribute changing methods.</p> <p>[...]</p> <p>As we considered this approach there were a number of things about it that we didn’t like and that seemed contrary to the above API design guidelines:</p> <ul> <li>It <strong>merges rather than separates the meta and application layers</strong>. As methods on Object.prototype the <strong>methods would be part of the public interface of every application object</strong> in a program. As such, they need to be understood by every developer, not just library designers.</li> </ul> <p>[...]</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POWhy were ES5 Object methods not added to Object.prototype?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USkangax
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy were ES5 Object methods not added to Object.prototype?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COInteresting... do you know how this lined up with `Object.create`? Did Crockford propose it as `Object.create` after these decisions had been made, or before that?
      singulars
      1. PO
      1. USDagg Nabbit
    2. COGood question. I have no idea :) I think Crockford renamed his `Object.beget` to `Object.create` at about the same time when these API were discussed. FWIW, the doc says: _'Note that Object.create without its optional second argument is essentially the same operation as the beget function that was been widely promoted. We (perhaps not surprisingly) agree with the utility of this function but felt that the word “beget” is probably confusing to many non-native English speakers.'_
      singulars
      1. PO
      1. USkangax
    3. COCrockford was directly involved in the ES5 design and originally proposed "beget". "create" emerged as the preferred name during the subsequent design discussions. He renamed "beget" in his book to reflect the ES design decision.
      singulars
      1. PO
      1. USAllen Wirfs-Brock
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload