This technique doesn’t even seem to work in Safari 4 (all the shadows blend together), so I’m probably going to hold off for now.

Although the current proposal has a requirement that only trailing formal parameters may have default values specified, this shouldn’t be necessary when named parameters are used:

The rationale here is that you can call a function that has named parameters with default values just like a function that doesn’t. So, a function:

function foo(x, y=2, z=3) {
 return [x, y, z];
}

could be called by: foo(1, 4) would return [1, 4, 3]

If a named parameter were in the first argument:

function foo(x=1, y, z) {
 return [x, y, z];
}

what would a call to foo(1,2) mean? (As far as I can tell, it would just effectively require all calls to treat all parameters using the named parameter syntax.) Python has the same restriction if you use the default value syntax (but not for the **kwargs syntax).

Uh, rename it? You’re already going to be jumping through hoops to make all this work anyway. I suppose you want to customize background-color to be backgroundColor or just bgc in CSS too? Frankly the background details end users never see aren’t much of a concern to me, and #! is a fair convention to use, if we’re going to be adopting this mess.

Granted, they could offer something more customizable, but in the end all it means more processor time on their servers just to stroke the egos of the 0.0001% of us who make the web sites. Anyway why would you, being Google want to give up branding/bragging rights?

I don’t think we’re there yet with this #! mess; but we can’t disguise theming it as improving it either…