02:06
<MikeSmith>
didn't know yet about SlimerJS http://slimerjs.org/
02:06
<MikeSmith>
SlimerJS is similar to PhantomJs, except that it runs on top of Gecko, the browser engine of Mozilla Firefox (specifically, version 31), instead of Webkit, and is not yet truly headless.
02:07
<MikeSmith>
Hixie_: Happy New Year
05:54
<hemanth>
Came here looking for a decent use-case/example of Reflect API...
05:59
<hemanth>
Wonder if the Streams API implementation has begun...
06:05
<hemanth>
dbaron: meow
06:09
<caitp>
hemanth, it looks like a way to invoke internal methods ([[....]] methods), but a lot of it should be more or less equivalent to static methods of Object
06:09
<caitp>
not sure what the use-case is though
06:17
<hemanth_>
caitp: interesting, bumped into Reflect.defineProperty(obj, name, desc)
06:20
<hemanth_>
they gel well with proxies
06:23
<terinjokes>
anyone have any ideas why SSE isn't more popular?
06:25
<caitp>
i'm guessing you don't mean intel's SIMD stuff
06:25
<caitp>
and therefore don't know what you mean
06:37
<terinjokes>
sorry, Server Sent Events / EventSource
06:38
<caitp>
IE11 not supporting it likely has something to do with it
07:46
<MikeSmith>
terinjokes: sse predates web sockets and webrtc datachannel and for most use cases those supersede it
07:47
<terinjokes>
MikeSmith: that seems like it's true only for bi-directional communication, no?
07:49
<MikeSmith>
terinjokes: well cleraly there's nothing that requires you do bi-directional communication over a web sockets connection. You can use it to push stuff if you wan
07:49
<terinjokes>
true, but I would say they solve a different use case, rather than supersede
07:49
<terinjokes>
both are a different language than HTTP, no?
07:50
<MikeSmith>
SSE isn't
07:51
<MikeSmith>
and as far as the UA implementors POV and can understand them not wanting to implement SSE if they already support web sockets
07:51
<MikeSmith>
and web sockets are supported basically everywhere now, in all UAs afaik
07:51
<MikeSmith>
as far as browser engines
07:51
<MikeSmith>
well not Presto
07:52
<MikeSmith>
but I'll sure they'll get there too eventually
07:52
<MikeSmith>
ah I mean Servo
07:52
<MikeSmith>
Jon-gian slip there
08:20
<terinjokes>
MikeSmith: i mean websockets and webrtc being not HTTP
08:21
<terinjokes>
whereas SSE is
08:21
<terinjokes>
and SSE is supported everywhere but IE
08:28
<MikeSmith>
ah
08:28
<MikeSmith>
yeah fair enough
08:29
<MikeSmith>
and I didn't know SSE was now supported everywhere but IE
08:30
<MikeSmith>
that's a pretty good argument for IE to add support for it I guess
10:04
<annevk>
wanderview: it's not entirely clear to me what the scenario is; we shouldn't collect the response just because the page has not inspected it yet though
11:37
<smaug____>
hmm, what should happen when there is an attribute type Window, but that Window isn't the current Window of the WindowProxy?
11:40
<smaug____>
Hixie: ^
11:40
<annevk>
smaug____: elaborate?
11:40
<smaug____>
I mean in the scripts
11:40
<smaug____>
accessing such attribute
11:43
<smaug____>
need to ask bz
11:45
smaug____
was just reading https://www.w3.org/Bugs/Public/show_bug.cgi?id=27128
12:39
<Domenic>
caitp: hemanth: one major benefit of Reflect.* is many of those functions return false instead of throwing.
12:44
<hemanth>
Domenic, no more try catches ;) instead of Function.prototype.apply.call(f, obj, args); we could say Reflect.apply(f, obj, args)
12:45
<Domenic>
Well, that one will still throw if the function throws
12:46
<hemanth>
heh heh yeah, at least in case of 'defineProperty'
12:46
<Domenic>
More like Reflect.deleteProperty vs. delete operator or Reflect.preventExtensions or, indeed, defineProperty
12:47
<hemanth>
cool
12:47
<hemanth>
Reflect.has(obj, key); feels more Javaish
12:51
<hemanth>
Sadly IE Technical Preview is the only browser that has implemented this API..
15:06
<annevk>
Domenic: do you know why the lifecycle callbacks are tranfered?
16:10
<hemanth>
mewo...
16:11
<caitp>
=)
16:15
<hemanth>
caitp, what's new?
16:16
<caitp>
well v8 folks are back from vacation so maybe more exciting syntax sugar features can get reviewed and worked on more
16:17
<hemanth>
^_^
16:17
hemanth
makes an attempt on FP joke -> https://twitter.com/GNUmanth/status/552688274632761344
16:26
<wanderview>
annevk: remind me where fetch spec issues go?
16:26
<wanderview>
not on github, right?
16:28
<hemanth>
caitp, how about influencing v8 folks to implement http:crbugs.com/346690 or may be even http://crbugs.com/316153 ? :)
16:29
<hemanth>
wanderview, https://github.com/whatwg/fetch/issues right?
16:31
<caitp>
my influence is pretty limited
16:32
<wanderview>
hemanth: actually, I think he prefers here: https://www.w3.org/Bugs/Public/enter_bug.cgi?product=WHATWG
16:32
<caitp>
I think 316153 is more an issue for the devtools team
16:32
<caitp>
less v8-specific
16:32
<hemanth>
yup
16:33
<hemanth>
wanderview, must be
16:36
<wanderview>
annevk: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27781
16:36
<annevk>
ta
16:38
<caitp>
hemanth, in that first bug are you saying "template literals don't work correctly" or "template literals aren't implemented, please implement them"?
16:38
<caitp>
(because we did this through october-november, try in canary),
16:43
<hemanth>
caitp, implement temaplate strings, this was reported in Feb, will check on canary
16:43
<caitp>
yeah, there were a bunch of bugs like that, it's too hard to go through them all and switch their status on code.google.com
16:44
<hemanth>
caitp, what about arrow functions? is it on it's way? kangax won't help here
16:44
<caitp>
mm, andy did most of arrow functions, i'm not sure what's left
16:45
<caitp>
probably some minor things that make them unshippable for now
16:46
<hemanth>
oh, heard that class implementation is speeding yup
16:46
<caitp>
they should work if you use --js-flags="--harmony-arrow-functions" or whatever it's called
16:46
<hemanth>
not there in experimental flags?
16:46
<caitp>
i think only staged features get switched on with experimental mode
16:46
<caitp>
and i'm not sure they're staged yet, could be wrong
16:48
<hemanth>
hmm
16:48
<caitp>
https://github.com/v8/v8-git-mirror/blob/master/src/flag-definitions.h#L175-L183 <<< those all need flags manually passed in, the shipping ones don't need a flag at all, and the staged ones are enabled if you turn on that experimental flag
17:01
<hemanth>
caitp, nice, thanks.
17:02
hemanth
wonders what sloppy mode is...
17:06
<zcorpan>
sounds like not "use strict"
17:58
<terinjokes>
MikeSmith: for things I'm working on, real time data updates, I'd prefer SSE to WebSockets. Seems to be created for this use case.
19:12
<Hixie>
smaug____: there should never be an attribute of type Window
19:20
<smaug____>
ah, yeah
19:43
<Ms2ger>
Hixie, is that written down somewhere? :)
22:00
<Domenic>
annevk: 7 months later https://github.com/w3c/webrtc-pc/issues/172