To keep this thread from getting off-track: I am talking about
patterns as a common ground between ES.next spec writers
and JS.current coders. Focusing on patterns now would help
to get JS coders involved in checking current proposals for
consistency/edge cases, instead of leaving that burden
On Nov 9, 2011, at 10:55 , Claus Reinke wrote:
Both the committee and JS coders could profit from examples.
Amen to that. JavaScript seems worse than any other language when it comes to
finding correct information on the web. For example, I trust StackOverflow for
many topics, but for
Rauschmayer a...@rauschma.de
Subject: Re: supporting ES upgrading with a programming pattern repo?
Date: November 10, 2011 1:34:36 GMT+01:00
To: Claus Reinke claus.rei...@talk21.com
Cc: es-discuss@mozilla.org
On Nov 9, 2011, at 10:55 , Claus Reinke wrote:
Both the committee and JS coders
Amen to that. JavaScript seems worse than any other language when it comes
to finding correct information on the web. For example, I trust
StackOverflow for many topics, but for JavaScript, it’s often shockingly
wrong. Half-truths are even worse than information that is completely wrong.
4 matches
Mail list logo