[00:02] <wgrant> lifeless: Doesn't work even unconfined as a proper package installed (in a VM) :/
[00:02] <wgrant> Can you Skype?
[00:02] <lifeless> sure
[00:03] <lifeless> though I can't alt-tab to it under precise. NO idea why
[00:54] <rick_h> lifeless: what's up?
[00:55]  * rick_h looks to make sure I haven't broken anything 
[00:56] <lifeless> rick_h: no, I wanted to sanity check my brain w/js
[00:56] <lifeless> rick_h: I nabbed wgrant as another js-head for that :>
[00:56] <rick_h> ah, okie then
[00:56] <wgrant> Unfortunately I just made the problem worse :)
[00:56] <lifeless> rick_h: getting my head around handlebars, and it has some really uhm crazy stuff
[00:57] <rick_h> heh, any example? I'm curious
[00:57] <lifeless> block helpers are called with a function which has had attributes on it - so options.fn [00:57] <rick_h> yea
[00:57] <wgrant> options.fn [00:58] <lifeless> 'tasteless' is one way to describe that
[01:02] <lifeless> also two typos in two answers, so I'm clearly not awake enough yet to be programming.
[01:02] <lifeless> I'm going to go fly some spaceships
[01:02] <wgrant> Heh
[01:10] <rick_h> hmm, looking at handlebars, but not seeing it. In base.js I see it registering helpers, which have a second arg options and it can have a fn in it
[01:10] <rick_h> if you guys have a link/line # handy be curious about the 'tasteless' bits
[01:11] <rick_h> hmm, fly spaceships. I should get started on the book club book tonight. Hope they didn't pick a dud
[01:12] <wgrant> rick_h: populateParams in compiler.js
[01:12] <rick_h> ah, thanks
[01:13] <wgrant> It sets tmp1 to the function, then conditionally adds various unrelated bits of data to it.
[01:14] <rick_h> geeze, could they leave out any more comments
[01:14] <wgrant> Basically it looks like they initially specified block helpers to take a function, but then realised they needed more so they decided to add unrelated attributes to the function.
[01:14] <wgrant> Yeah
[01:14] <wgrant> Does that file have even a single comment line?
[01:14] <rick_h> wgrant: yea, makes sense
[01:14] <wgrant> Oh, it does have a couple.
[01:14] <rick_h> yea, // HELPERS
[01:14] <rick_h> woot, I feel aided by the comment
[01:17] <rick_h> ah, interesting. Makes sense I guess. Means they don't have to maintain/change code elsewhere. Normally you'd just move that data up in scope.
[01:18] <rick_h> or deal with various arguments length checking stuff
[01:24] <lifeless> rick_h: doing it one way or the other would be fine
[01:24] <lifeless> rick_h: they do *both*
[01:24] <lifeless> rick_h: -> fugly
[03:47] <StevenK> lifeless: I didn't want the convoy tests module installed in the deb package, and I didn't want to wield rm in the build step.
[08:03] <lifeless> StevenK: I'd do what bzr does then, generate two packages
[10:01] <StevenK> lifeless: I'll make a note to have a quick look on Monday
[22:34] <lifeless> ok, so after all the fuss about 'classic twitter/new twitter' they go and change it (roughly) back. grah
[22:40] <wgrant> Oh?
[22:42] <lifeless> you don't have a new layout ?
[22:43] <wgrant> Doesn't look radically different from before, AFAICT.
[22:43] <lifeless> click on a tweet
[22:44] <wgrant> Ahh
[22:44] <wgrant> indeed
[22:44] <lifeless> and click on the tweeters name
[22:55] <nigelb> some changes are good.
[22:55] <nigelb> like, now its easiser to find if someone follows you.
[22:56] <nigelb> also, conversations are win!
[22:56] <wgrant> Are they as good as identi.ca's yet?
[22:58] <nigelb> Nope!
[23:02] <lifeless> sure
[23:02] <lifeless> I wasn't saying good/bad
[23:02] <lifeless> just that they spent /how long/ socialising the other change, letting folk opt in then opt out before finally forcing it
[23:02] <lifeless> and this, they just do.
[23:02] <lifeless> it is interesting
[23:10] <nigelb> You mean the first new twtter?