Comments on: Chrome Extension API; How we wish we have named parameters

By: SubtleGradient

SubtleGradient — Thu, 09 Apr 2009 08:39:06 +0000

Explain again why removing the { & } characters is a good idea. Just pretend you have a cute little pinchy crab hugging all your properties ^_^

By: savetheclocktower

savetheclocktower — Wed, 08 Apr 2009 23:50:37 +0000

Ruby has shown us that a bit of syntactic flexibility can go a long way. For instance, Ruby has “getters” and “setters” simply because parentheses are optional in method calls.

Likewise, one can leave off the braces when passing a hash into a method (except where it would cause ambiguity), thus approximating named parameters. If we could likewise leave off the braces in JavaScript, we’d be 90% there.

By: eyelidlessness

eyelidlessness — Tue, 07 Apr 2009 18:58:55 +0000

I would hope that the “selected” property was named “hasFocus” instead due to selected having multile meanings such as when you tab to an object.

“Focus” suffers from the same problem. “Selected” is more accurate, at the least, and really who cares? It’s not like developers are going to utterly confuse the tab system with a webpage checkbox.

By: slightlyoff

slightlyoff — Tue, 07 Apr 2009 18:30:00 +0000

+1 for named params, ala Python. In some sense we already have them, but not in the “optinal in any order property bag” syntax.

By: EliGrey

EliGrey — Tue, 07 Apr 2009 17:06:05 +0000

I would hope that the “selected” property was named “hasFocus” instead due to selected having multile meanings such as when you tab to an object.

By: mpcm

mpcm — Tue, 07 Apr 2009 16:08:40 +0000

It was something we found we needed in json-rpc to make life easier. It makes more sense if you think of api methods as properties that take an array or an object, especially when you go into doing work at language agnostic levels.

By: TNO

TNO — Tue, 07 Apr 2009 12:01:31 +0000

Named parameters have come up on es-discuss from time to time, I expect we’ll see them in the not so distant future.