Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #28558 > unrolled thread

FAQ: Update of FAQ Notes

Back to article view | Back to comp.lang.javascript

Contents

  FAQ: Update of FAQ Notes RobG <rgqld@iinet.net.au> - 2015-08-23 16:11 -0700
    Re: FAQ: Update of FAQ Notes Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2015-08-24 00:18 -0300
      Re: FAQ: Update of FAQ Notes Tim Streater <timstreater@greenbee.net> - 2015-08-24 10:06 +0100
        Re: FAQ: Update of FAQ Notes "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2015-08-24 13:27 +0200
    Re: FAQ: Update of FAQ Notes Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2015-08-24 20:19 +0200

#28558 — FAQ: Update of FAQ Notes

The FAQ Notes have some excellent articles, however they're becoming dated. ES5 was introduced in June 2011 and now ECMAScript 2015 is the current standard. The articles and FAQ don't seem to have been updated to reflect his.

For example, the closures article[1] makes many references to ECMA-262 ed 3 and uses language from that specification. Terms like "host object" are replaced with "exotic object" and the statement "[the prototype] property is not directly accessible with scripts" is no longer true given *Object.getPrototypeOf".

There are many other examples. Is there an FAQ maintainer? Is there a plan to update the FAQ to reflect the current standard?


1. http://www.jibbering.com/faq/notes/closures/#clResO

[toc] | [next] | [standalone]

#28560

On 23/08/2015 20:11, RobG wrote:
> The FAQ Notes have some excellent articles, however they're becoming
> dated.
> [snip]
> Is there an FAQ maintainer?

Yes, Thomas 'PointedEars' Lahn.

> Is there a
> plan to update the FAQ to reflect the current standard?
>

None that I am aware of.

>
> 1. http://www.jibbering.com/faq/notes/closures/#clResO
>

See the newer URL:
<http://pointedears.de/scripts/faq/cljs/>

-- 
Joao Rodrigues

[toc] | [prev] | [next] | [standalone]

#28561

In article <mre2en$9fk$1@speranza.aioe.org>, Joao Rodrigues
<groups_jr-1@yahoo.com.br> wrote:

>On 23/08/2015 20:11, RobG wrote:
>> The FAQ Notes have some excellent articles, however they're becoming
>> dated.
>> [snip]
>> Is there an FAQ maintainer?
>
>Yes, Thomas 'PointedEars' Lahn.

No, he's just a loudmouth.

-- 
HAL 9000:    Dave.  Put down those Windows disks.  Dave.  DAVE!

[toc] | [prev] | [next] | [standalone]

#28562

Tim Streater <timstreater@greenbee.net> wrote on 24 Aug 2015 in 
comp.lang.javascript:

>>> Is there an FAQ maintainer?
>>
>>Yes, Thomas 'PointedEars' Lahn.
> 
> No, he's just a loudmouth.

In practice, he is, 
as nobody else, including Tim,
wants to do it.

Tim's personal animosity is not much better 
than the way Thomas sometimes acts, 
Thomas also does good things for the group.

-- 
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)

[toc] | [prev] | [next] | [standalone]

#28563

RobG wrote:

> The FAQ Notes have some excellent articles, however they're becoming
> dated. ES5 was introduced in June 2011 and now ECMAScript 2015 is the
> current standard. The articles and FAQ don't seem to have been updated to
> reflect his.

ACK.  However, note that the implementation of the 6th Edition is still 
incomplete at best.  For example, “Proxy” is not implemented by Google V8 
JavaScript in Chromium “44.0.2403.89 Built on Debian stretch/sid, running on 
Debian stretch/sid (64-bit)”, but by Mozilla JavaScript in Iceweasel 38.1.0 
for the same OS/platform.
 
> For example, the closures article[1] makes many references to ECMA-262 ed
> 3 and uses language from that specification.

It also makes at least one reference to the 5.1 Edition and uses its 
terminology, although probably not consistently as it was created before.

> Terms like "host object" are replaced with "exotic object"

In the 6th Edition/2015, not before.  Whether that was a smart move remains 
to be seen.  I find the term “host object” to be more descriptive, but that 
is not the reason why it is also used in the “FAQ for comp.lang.javascript”.

> and the statement "[the prototype] property is not directly accessible
> with scripts" is no longer true given *Object.getPrototypeOf".
 
This method has been introduced with Edition 5 already:

<http://PointedEars.de/es-matrix/?filter=getPrototypeOf>

Also, the “__proto__” property was supported before:

<http://PointedEars.de/es-matrix/?filter=__proto__>

> There are many other examples. Is there an FAQ maintainer?

Yes.

> Is there a plan to update the FAQ to reflect the current standard?

There is a plan to update the “FAQ for comp.lang.javascript”.  But as I have 
a day job, I am relying on your contributions to make that happen.  (I have 
announced it here and on Twitter at this FAQ’s inception, several years 
ago.)  This year I am implementing a plan to make contributions easier in 
the future.  But you can contribute to the content right now; several people 
have done it already, for which I am thankful.

> 1. http://www.jibbering.com/faq/notes/closures/#clResO

See below.

-- 
PointedEars, ed.
FAQ: <http://PointedEars.de/faq> | SVN: <http://PointedEars.de/wsvn/>
Twitter: @PointedEars2 | ES Matrix: <http://PointedEars.de/es-matrix>
Please do not cc me. / Bitte keine Kopien per E-Mail.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.javascript

csiph-web