Re: Showing APIs to the ECMAScript world

On Thursday, May 9, 2013 at 5:56 PM, Micheil Smith wrote:

> Hmm, that's an alright point, however, if developers are copying and pasting 
> code, then they probably aren't really understanding or caring about what it 
> does.
> I think it'd make sense to use a sensible default, and then communicate that.
I tend to agree (I made exactly the same comment previously). I have a feeling this one is going to keep coming up.   
> If you mean something as a boolean, it probably makes more sense to be a 
> boolean, even if developers may occasionally copy and paste code from 
> some examples on the web.

>From a self documenting code POV, it would be nice to have it in the options dictionary: 

var options = {respectTimezones: true} 

And have it default to false (or the other way around depending on which one is going to be used the most). 
> Also, as a user of this API, do you really want to always be explicit in setting 
> whether you want to respect timezones or not? I have a small feeling that 
> developers would actually use the Data attribute more-so over change the 
> respecting of timezones.

FWIW, I also agree. 

Marcos Caceres

Received on Thursday, 9 May 2013 17:14:30 UTC