00:35
<Krinkle>
Domenic: btw, fully on-board with linking to living standards; one thing I do find though, is that I'm often drawn to the field stating which version fo a spec the thing was introduced in (I don't click the link though). I suppose it's an old habit that is perhaps a bad one, given that even for ecma script specs (which still have a version), implementors cherry-pick out of order, so the support tables is where I should look!
00:35
<Domenic>
Agreed, support tables are the best.
02:20
<TabAtkins>
annevk: No, most languages allow both quotes. ^_^ I find escapes much more confusing and prefer to avoid them if possible.
06:26
<Krinkle>
Is there a draft spec for MemoryInfo? After googling for a few minutes, surprised to be empty handed for anything relating to performance.memory, MemoryInfo and/or totalJSHeapSize etc.
06:27
<Krinkle>
It's in chrome and no longer behind a flag.
06:27
<Krinkle>
was or is in Safari behind a flag.
06:32
<Krinkle>
Ah, found it. https://github.com/WICG/performance-memory/blob/master/explainer.md#-appendix-a---chromes-current-implementation-of-performancememory
06:32
<Krinkle>
https://github.com/WICG/performance-memory/issues/19
06:32
<Krinkle>
https://github.com/w3c/strategy/issues/144
06:32
<Krinkle>
Too bad.
10:17
<zcorpan>
Hello whatwg
10:24
<MikeSmith>
howdy zcorpan
11:08
<nox>
TabAtkins: Most languages allow both quotes? Citation needed.
11:12
<jgraham>
Most seems impossible to quantify. "Most weighed by usage" seems much more plausible to to compute and also to be true
11:12
<jgraham>
Although I wouldn't want to bet one way or another
11:13
<gsnedders>
most higher level languages allow either; most lower level don't?
11:13
<jgraham>
"most 'dynamically typed scripting languages, weighed by usage'" seems clearly true since just JS + Python
11:14
<jgraham>
Yeah, I think usually langauges that differentiate between char and str use different quotes for each and languages that don't don't
11:31
<nox>
Plot twist: TabAtkins was talking about human languages. :p
11:48
<MikeSmith>
hehe
12:30
<hsivonen>
annevk: :-( Is there some characterization of the overall vendor buy-in status for Web NFC?
12:43
<gsnedders>
hsivonen: nothing from MS or Apple; given Apple don't allow any third party access to NFC in iOS it seems unlikely they'll allow Web NFC
12:53
<annevk>
gsnedders: I think Apple now has some NFC APIs (perhaps readonly), but yeah, I wouldn't expect Web NFC to follow fast
12:53
<annevk>
https://developer.apple.com/documentation/corenfc
13:00
<gsnedders>
oh, somehow I'd missed that; that's big news for many things!
13:00
<gsnedders>
as long ago as iOS 11, seemingly