ES Discuss - Message History

Benjamin (Inglor) Gruenbaum (2015-02-02T17:07:02.000Z)

Go to Source

> Follow-up thought: people still link to the (completely outdated)
proposals on the wiki, because they are often very readable.

I think people mostly link to them because they are rank pretty well in
search results and are confined to a single problem in a readable way.

I think the way PHP manages RFCs (https://wiki.php.net/rfc/) - while not
nearly as accurate (IMO) as ES proposals has some really interesting things
in its template and encouraging community feedback on proposals while
they're worked on is very valuable.

For example - I don't need to know or understand what `[[ReferenceGet]]` is
to understand something written in this sort of style:
https://wiki.php.net/rfc/combined-comparison-operator
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20150202/2602f14a/attachment.html>

d at domenic.me (2015-02-17T17:52:59.148Z)

> Follow-up thought: people still link to the (completely outdated) proposals on the wiki, because they are often very readable.

I think people mostly link to them because they are rank pretty well in
search results and are confined to a single problem in a readable way.

I think the way PHP manages RFCs (https://wiki.php.net/rfc/) - while not
nearly as accurate (IMO) as ES proposals has some really interesting things
in its template and encouraging community feedback on proposals while
they're worked on is very valuable.

For example - I don't need to know or understand what `[[ReferenceGet]]` is
to understand something written in this sort of style:
https://wiki.php.net/rfc/combined-comparison-operator

d at domenic.me (2015-02-17T17:52:50.205Z)

> Follow-up thought: people still link to the (completely outdated) proposals on the wiki, because they are often very readable.

I think people mostly link to them because they are rank pretty well in
search results and are confined to a single problem in a readable way.

I think the way PHP manages RFCs (https://wiki.php.net/rfc/) - while not
nearly as accurate (IMO) as ES proposals has some really interesting things
in its template and encouraging community feedback on proposals while
they're worked on is very valuable.

For example - I don't need to know or understand what `[[ReferenceGet]]` is
to understand something written in this sort of style:
https://wiki.php.net/rfc/combined

Edit