03:48
<Michael Ficarra>
slight issue: https://github.com/google/fonts/issues/6506
04:34
<bakkot>
can we just host it? it's like 200kb zipped for regular+bold+italic
14:16
<jmdyck>
NotEscapeSequence (NES) is disallowed in untagged TemplateLiterals,
but allowed in tagged TemplateLiterals.
So consider a tagged TemplateLiteral that contains a NES.
The TRV of that NES is a String, and the TV of it is undefined.
So in GetTemplateObject, the relevant element of _rawStrings_ is a String,
and of _cookedStrings_ is undefined.
Is that all correct?
14:30
<Chris de Almeida>
whatever font is used, we should serve it directly and not rely on CDNs
14:56
<jmdyck>
If so, the return-types of TemplateString + TemplateStrings need to be fixed, to allow for undefined.
15:37
<bakkot>
yup, sounds right
16:07
<ljharb>
can we just host it? it's like 200kb zipped for regular+bold+italic
seems like we need to just host it, based on their response to michael's issue
16:09
<Michael Ficarra>
I will try swapping the glyph out and subsetting to get even smaller than what Google Fonts hosts.
16:12
<ljharb>
it'd be good if any modification you do to google's downloads is repeatable tho
17:58
<Michael Ficarra>
unbelievably, it actually worked 😀
17:58
<Michael Ficarra>
I now know way too much about opentype features and glyph substitution
17:59
<Michael Ficarra>
also, they're like 15kb each, so 60kb total, about the same as Google Fonts
17:59
<Michael Ficarra>
since I added a documentation comment
18:00
<Michael Ficarra>

Latin subset from Google Fonts with support for slashed zero substitution added back in by Michael Ficarra.

18:00
<bakkot>
huh, the ttf versions are 160kb each (uncompressed)
18:01
<bakkot>
I guess woff2 is a lot more efficient?
18:01
<Michael Ficarra>
it's a huge subsetting
18:02
<Michael Ficarra>
most of the non-latin glyphs and tons of opentype features are dropped
18:02
<Michael Ficarra>
just latin, a couple ligatures and diacritics, and now slashed zero
18:02
<bakkot>
ah, makes sense
18:03
<bakkot>
... I wonder if someone has done the work to take an HTML document and automatically derive the subset of glyphs you actually need for that document, so you can ship only those
18:22
<Michael Ficarra>
any preference whether we serve separate woff2 font files or embed them as a base64 data URL in the ecmarkup CSS file?
18:28
<bakkot>
I would do separate files
18:28
<Chris de Almeida>
I must be missing some context from the editor call yesterday... has a font been blessed by the editors?
18:28
<bakkot>
at least when the CSS is not already inlined
19:06
<Michael Ficarra>
Chris de Almeida: yes, we decided yesterday to go with IBM Plex Serif
19:25
<Michael Ficarra>
ugh ecmarkup has an option to inline the CSS
19:26
<Michael Ficarra>
which means I guess I have to inline the font as a base64 data URL when that is used
20:01
<Chris de Almeida>
related: if it's not already on the radar, the code {} font-family should be updated to use IBM Plex Mono, as it is designed to comingle with the other Plex fonts. (and no hard feelings against Consolas, which is ackchyually my preferred font for code editors)
20:04
<bakkot>
not Comic Code?
20:05
<bakkot>
I do feel a bit weird about using a font which is described as "It's global, it's versatile, and it's distinctly IBM"
20:05
<bakkot>
but like
20:05
<bakkot>
whatever I guess
20:13
<Chris de Almeida>
every day we all use things that are distinctly IBM, one more font won't kill us 😄
20:29
<shu>
i would like comic code
20:32
<shu>
every day we all use things that are distinctly IBM, one more font won't kill us 😄
leave that kind of content for Threads, this channel is Good vibes only
20:38
<Chris de Almeida>
lol. the worst part about Threads is not being able to get your usual username because they're all taken via instagram already
21:06
<shu>
i knew i shuoldn't have mutadis mutandised the resizable buffer spec draft
21:06
<shu>
this is taking forever
21:16
<ljharb>
have what now?
21:41
<shu>
https://en.wikipedia.org/wiki/Mutatis_mutandis
21:41
<shu>
i had a section that was like "just change the uses of these fields, omitted for brevity"
23:15
<shu>
why the hell do we call typed arrays Integer-Indexed exotic objects
23:15
<shu>
why didn't we just call them TypedArray exotic objects
23:46
<bakkot>
we could fix it
23:46
<bakkot>
90% of the answers to "why" questions about TAs are "khronos"
23:47
<shu>
it's like some star trek lore
23:47
<shu>
the strife started with the Khronos Accord
23:54
<jmdyck>
See https://github.com/tc39/ecma262/issues/1617
23:56
<jmdyck>
(from 4 years ago)
23:56
<shu>
i have no memory of this, but i agree with my past self still
23:58
<shu>
time gets away from us