00:55
<SimonSapin>
hsivonen: Are you in Portland this week?
01:08
<jgraham>
SimonSapin: I'm pretty sure he isn't
01:44
<smaug____>
SimonSapin: he is not
02:19
<SimonSapin>
thanks
07:56
<hsivonen>
SimonSapin: I'm not in Portland. :-(
07:59
<SimonSapin>
hsivonen: Ok. We have a meeting tomorrow with the Servo and JS teams, one of the topics is string representation. I thought you might be interested.
08:11
<hsivonen>
SimonSapin: I'd be interested, yeah, but can't attend since I'm not there.
08:11
<hsivonen>
SimonSapin: thanks
13:05
<Ms2ger>
zcorpan, ta
13:06
<zcorpan>
Ms2ger: welcome
14:09
<MikeSmith>
botie: inform tantek I updated the Web Notification WG charter http://www.w3.org/2010/web-notifications/ The group isn't closed. The current chair is Jon Lee from Apple.
14:09
<botie>
will do
14:09
<zcorpan>
botie: sup
14:09
<botie>
zcorpan: what?
17:03
<botie>
tantek, at 2014-12-05 14:09 UTC, MikeSmith said: I updated the Web Notification WG charter http://www.w3.org/2010/web-notifications/ The group isn't closed. The current chair is Jon Lee from Apple.
17:04
<tantek>
the W3C's bot is in this channel? whoa.
17:04
<tantek>
what
17:06
<gsnedders>
pretty sure it's more MikeSmith's than the W3C's.
17:10
<encryptd_fractl>
Domenic: I was wondering is this 'reverse destructoring' is a part of es6, or a traceur-only thing? Thanks https://github.com/whatwg/streams/blob/b8edaac6391c49fbfa7b57123ba5786df6d0d77d/reference-implementation/lib/experimental/readable-byte-stream.js#L176
17:12
<arv>
encryptd_fractl: That is property short hand. part of es6: http://people.mozilla.org/~jorendorff/es6-draft.html#sec-object-initializer
17:13
<encryptd_fractl>
Ah thanks, easier to find docs when you know what its called :)
17:14
<encryptd_fractl>
yea I liked that feature in coffeescript. Must not be implemented in the version of esnext I'm using
17:31
<WesleyCrushed>
guys, can someone give a proper/canonical answer to this http://stackoverflow.com/questions/26292408 ? i know this is not the best place where to ask, but maybe there's someone here [really] involved with CSS. ty :P
20:19
<terinjokes>
can we get `text-justify` standardized?
20:21
<terinjokes>
`text-align: justify` just looks terrible
20:51
<astearns_>
terinjokes: is your justified text not hyphenated? that's usually the culprit
21:00
<Domenic>
encryptd_fractl: esnext is not very complete; I trust Traceur much more :)
21:33
<terinjokes>
astearns_: i'm used to the TeX algorithm
21:34
<astearns_>
terinjokes: multi-line breaking algos are much better. but most people
21:34
<astearns_>
's complaints about web justification go away once text is hyphenated
21:35
<astearns_>
we certainly can do better. But first Chrome has to hyphenate :)
22:12
<Domenic>
There's still no way to independently apply multiple CSS transforms right?
22:52
<WesleyCrushed>
Domenic: details?
22:53
<Domenic>
WesleyCrushed: e.g. apply scale from CSS and translate from script or similar
22:55
<WesleyCrushed>
someone (and also me) suggested "slots" as in, for example: background-image(3):url('foo.png'); which is the same of writing background-image:none, none, none, url('foo.png')
22:55
<WesleyCrushed>
from dom would be say, element.style.backgroundImage[3] = "url('foo.png')";
22:56
<WesleyCrushed>
the same would apply also to transforms, transitions and all similar properties
22:57
<Domenic>
i'm really asking as to whether any such ideas have been implemented yet, not proposed :P
22:57
<WesleyCrushed>
Domenic read http://fremycompany.com/TR/2012/ED-css-list-properties/ and http://www.xanthir.com/blog/b4KZ0/
22:57
<WesleyCrushed>
me too :P
22:57
<Domenic>
yeah, seen 'em
22:59
<WesleyCrushed>
that's definitely a thing to discuss asap
23:19
<astearns_>
Domenic: there are "simple" transforms proposed (AFAIK not implemented) that would let you set separate translate, rotate and scale along with the current transform property
23:19
<Domenic>
astearns_: yeah, saw those too... would be pretty sweet.
23:47
<iamstef>
Domenic: esnext is also pretty slow
23:47
<iamstef>
because recast is slow
23:47
<Domenic>
yepyep
23:47
<iamstef>
esnext es6-module-transpiler bundle format is whats keeping me around atm
23:48
<iamstef>
as is eventualbuddha being a solid guy
23:48
<iamstef>
but i am concerned about recast
23:48
<terinjokes>
does the common-interop export stuff in 6to5 not work?
23:48
<terinjokes>
not work for you*
23:48
<iamstef>
re: perf and the lack of movement on that front
23:49
<iamstef>
terinjokes: ?
23:49
<terinjokes>
https://github.com/6to5/6to5/blob/v1.14.6/doc/modules.md#common-interop
23:50
<iamstef>
im unsure what the context of your question is
23:50
<terinjokes>
i might be misunderstanding the convo though, if so ignore me
23:50
<iamstef>
the bundle format essentially aggressively re-writes and re-orders content to remove the need for a costly loader
23:50
<iamstef>
i dont think this is related to the interopt story
23:52
<iamstef>
lets see what happens but if in the next while no movement happens on the perf front i may re-consider a different solution
23:53
<iamstef>
i dont have the bandwidth to work on that
23:54
<iamstef>
Domenic: any ideas of the traceur guys would consider something like the bundle format?
23:54
<Domenic>
iamstef: yeah it's been on the to-do list for a while
23:54
<Domenic>
arv ^
23:55
<iamstef>
ya we all need to actually grab beer or something soon
23:55
<iamstef>
we keep trying to do something but noone is in town at the same time
23:55
<iamstef>
the ny chrome team that is