Simon Willison’s Weblog


14 items tagged “douglas-crockford”


JavaScript: The Good Parts. Douglas Crockford’s soon-to-be-published book on the subset of JavaScript that he recommends. Promises to be “short, but dense”—if it’s half as good as his JavaScript lectures this is going to be a must-have.

# 19th April 2008, 4:38 pm / books, douglas-crockford, javascript

hash. Douglas Crockford: “Any HTML tag that accepts a src= or href= attribute should also be allowed to take a hash= attribute”—to protect against file tampering and (more importantly) provide a truly robust caching mechanism.

# 30th March 2008, 6:34 pm / caching, douglas-crockford, hash, html, sha1


In the long term, I want to replace JavaScript and the DOM with a smarter, safer design. In the medium term, I want to use something like Google Gears to give us vats with which we can have safe mashups. But in the short term, I recommend that you be using Firefox with No Script. Until we get things right, it seems to be the best we can do.

Douglas Crockford

# 7th November 2007, 3:36 pm / javascript, noscript, firefox, google-gears, dom, security, mashups, douglas-crockford

The Elements of JavaScript Style. Douglas Crockford illustrates better coding practises through refactoring of old code.

# 13th September 2007, 8:22 am / douglas-crockford, javascript, refactoring, yahoo

Base32 encoding (via) I was on the verge of inventing this when I discovered that Douglas Crockford had invented it for me.

# 17th August 2007, 11:25 pm / base32, douglas-crockford, encoding

JavaScript Minifier that doesn’t break code (via) Perl re-implementation of Douglas Crockford’s classic JSMin that doesn’t clobber IE’s conditional comments, by Peter Michaux.

# 4th June 2007, 5:44 pm / conditionalcomments, douglas-crockford, ie, internet-explorer, james-bennett, javascript, jsmin, perl, pete-michaux

JSON and Browser Security. Douglas Crockford suggests using secret tokens to protect JSON content, and avoiding wrapper hacks to protect unauthorised JSON delivery as they may fall foul of undiscovered browser bugs in the future.

# 11th April 2007, 12:52 am / douglas-crockford, json, security

Browser Wars. Doug Crockford is hosting a panel discussion with Chris Wilson from IE, Mike Shaver from Mozilla and Håkon Wium Lie from Opera on February 28th in Sunnyvale.

# 22nd February 2007, 7:53 am / chris-wilson, douglas-crockford, hakonwiumlee, mike-shaver

With this much storage, you can imagine filesystems in which files are never deleted and files are never rewritten. The filesystem never forgets. Such systems could be much more reliable than the systems we use today which are based on the assumption that storage is a constrained resource.

Douglas Crockford

# 8th January 2007, 7:04 pm / storage, douglas-crockford


The good thing about reinventing the wheel is that you can get a round one.

Douglas Crockford

# 21st December 2006, 10:14 am / douglas-crockford, json

I read on Niall Kennedy that has come up with an API that returns a JSON structure, and I figured, sheez it can't be that hard to parse, so let's see what it looks like, and damn, IT'S NOT EVEN XML! [...] Who did this travesty? Let's find a tree and string them up. Now.

Dave Winer

# 20th December 2006, 7:21 pm / douglas-crockford, dave-winer, json, xml

XHTML is not going to replace HTML as the web's official markup language because it turns out that resilience is more useful than brittleness.

Douglas Crockford

# 14th December 2006, 5:40 pm / douglas-crockford, xhtml

Proposed RFC for application/json (via) Douglas Crockford is putting JSON through the IETF.

# 1st August 2006, 9:29 pm / douglas-crockford, ietf, json, rfc


JSON and Yahoo!’s JavaScript APIs

I had the pleasure yesterday of seeing Douglas Crockford speak about JSON, the ultra-simple data interchange format he has been promoting as an alternative to XML. JSON is a subset of JavaScript, based around that language’s array, string and object literal syntax.

[... 240 words]