jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

Update article.md

Browse source 
Wording changes to 2012 prototype history. "allowed to" without a "who" is not very grammatical. Could replace with "allowed us to" or "allowed the user to". I went with a different verb, but either of the others would be OK too.

Also a little punctuation change to 2015 history.
This commit is contained in:
paroche 2019-09-27 20:31:44 -06:00 • committed by GitHub
parent f44cba85ec
commit df7f6d3fd6
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
1-js/08-prototypes/04-prototype-methods/article.md
View file

@ -72,8 +72,8 @@ Why so?
That's for historical reasons. That's for historical reasons.
- The `"prototype"` property of a constructor function works since very ancient times. - The `"prototype"` property of a constructor function works since very ancient times.
- Later, in the year 2012: `Object.create` appeared in the standard. It allowed to create objects with the given prototype, but did not allow to get/set it. So browsers implemented non-standard `__proto__` accessor that allowed to get/set a prototype at any time. - Later, in the year 2012: `Object.create` appeared in the standard. It gave the ability to create objects with a given prototype, but did not provide the ability to get/set it. So browsers implemented the non-standard `__proto__` accessor that allowed the user to get/set a prototype at any time.
- Later, in the year 2015: `Object.setPrototypeOf` and `Object.getPrototypeOf` were added to the standard, to perform the same functionality as `__proto__`. As `__proto__` was de-facto implemented everywhere, it was kind-of deprecated and made its way to the Annex B of the standard, that is optional for non-browser environments. - Later, in the year 2015: `Object.setPrototypeOf` and `Object.getPrototypeOf` were added to the standard, to perform the same functionality as `__proto__`. As `__proto__` was de-facto implemented everywhere, it was kind-of deprecated and made its way to the Annex B of the standard, that is: optional for non-browser environments.
As of now we have all these ways at our disposal. As of now we have all these ways at our disposal.