Google Fonts

Yeah.

And yeah, with Google, that was a good time for Google, Google Fonts in particular.

And eBooks were newish, iPads were newish, and they tried to have an alternative to Kindle.

And they realized that the typeface they were using is just not working.

It's even for somebody that licenses the typefaces on a regular basis.

You know, I must be in, we must be in a teeny tiny percentage of people that understand where typefaces come from.

And they are more easily available now through Google Fonts in particular.

It tends to be where the vast majority of people will head.

Yeah

... was, uh, it was already created in Google using Google Fonts.

So it was a, uh, fairly easy path transition for Google Slides to unpack and then repurpose.

Yes.

Give you your cheese.

Mine wasn't.

So my, my main font and my heading fonts and my body and my heading font are not Google Fonts, and it, and it flagged it for me and it said, um, "This will be substituted unless you give me the font," basically.

And I did, and then it added it.

And the loss wasn't felt as hard.

But not like Google Fonts.

That seems like the biggie.

That feels like maybe the biggest because you don't bundle your fonts.

anything that gets embedded.

Like if you think, well, obviously CodePen, but also like YouTube Player, these kind of things.

It's pretty expensive, and then of course we have web fonts, we have Google Fonts.

Well, a lot of

but it used to be even hotter.

I feel like, or it used to be part of the discourse was like, Hey, if you're going to load fonts, load them from Google fonts because, because they're crawl.

Like if you use whatever proxy maneuvers, I don't even know something very popular.

Perfect.

No, I, yeah.

I mean, I bet it's something like that.

Like, or actually he didn't actually look like as we're talking, just posted or reposted somebody's article, you know, um, which is actually pretty good, but, um, who called out like Google fonts would be like a big one.

Right.