Re: Prototype - Good/Bad/Why?
David Mark wrote:
<snip>
<snip>
Martin Honnen? For experience and technical knowledge Martin is pretty had
to beat.
As worded that has the implication that I may be bigger authority on
javascript than Douglas Crockford. I am not very comfortable with that idea.
Partly because I am not very comfortable with the idea of authority at all;
nobody's ideas are worth any more, or any less, than the reasoning behind
them. But mostly because Douglas Crockford was genuinely an expert when I
was a complete novice and making all the amateurish mistakes that are
expected of novices.
I learnt a huge amount from Douglas Crockford as a result of our exchanges
on this group, and even more as a direct result of reading his articles and
code. It is the case, for example, that I maybe would never have pursued
closures were it not for Douglas Crockford's method for creating private
members of javascript object instances (because that more OO employment of
closures had more concrete appeal at the time for a former Java programmer
than Yann-Erwan Perio's fascinating functional programming examples).
It is difficult to understate the significance of JSON. Javascript's object
notation sat under our noses for years but it took a genius to notice that a
subset of it could be directly interchangeable with XML but more efficient,
and that genius was Douglas Crockford. JSON is here to stay, and if
inventing it were his only legacy that alone would be a significant
accolade. But if you look at every significant change in the way javascript
is coded that has happened over the last half decade or so a line of
influences traced back might branch and spider along the way but sooner or
later it would link to Douglas Crockford.
Richard.
David Mark wrote:
<snip>
Crockford is one of the leading experts on JavaScript.
Other than Richard Cornford, I am not familiar with
any bigger authorities on the language.
Other than Richard Cornford, I am not familiar with
any bigger authorities on the language.
Martin Honnen? For experience and technical knowledge Martin is pretty had
to beat.
As worded that has the implication that I may be bigger authority on
javascript than Douglas Crockford. I am not very comfortable with that idea.
Partly because I am not very comfortable with the idea of authority at all;
nobody's ideas are worth any more, or any less, than the reasoning behind
them. But mostly because Douglas Crockford was genuinely an expert when I
was a complete novice and making all the amateurish mistakes that are
expected of novices.
I learnt a huge amount from Douglas Crockford as a result of our exchanges
on this group, and even more as a direct result of reading his articles and
code. It is the case, for example, that I maybe would never have pursued
closures were it not for Douglas Crockford's method for creating private
members of javascript object instances (because that more OO employment of
closures had more concrete appeal at the time for a former Java programmer
than Yann-Erwan Perio's fascinating functional programming examples).
It is difficult to understate the significance of JSON. Javascript's object
notation sat under our noses for years but it took a genius to notice that a
subset of it could be directly interchangeable with XML but more efficient,
and that genius was Douglas Crockford. JSON is here to stay, and if
inventing it were his only legacy that alone would be a significant
accolade. But if you look at every significant change in the way javascript
is coded that has happened over the last half decade or so a line of
influences traced back might branch and spider along the way but sooner or
later it would link to Douglas Crockford.
Richard.
Comment