What made you give up? As the article describes, self hosting fonts is as easy as making the static font files available and then adding a few lines of CSS. What solution would you want Google to offer?

I needed to figure out exactly which files need to be there, and I needed to understand what's happening in that CSS file. I vaguely remember seeing different content for the CSS file in different browsers.

At that time it would take me more than a few minutes (which was what I had), and seemed a rabbit hole. I decided not to pursue that.

LOL downvoted. The sentence "self hosting fonts is as easy as making the static font files available and then adding a few lines of CSS" is a complete lie and you could tell they have never gone through the process themselves and were just making things up.

If you don't believe me, you are welcome to try it out yourself FROM SCRATCH without any references whatsoever, and see how long it takes you to come up a solution that works on all 5 or 6 platforms, desktop or mobile.

Please educate me if I'm missing something!

From memory, what I would do is simply download the original ttfs or otfs, run them through woff2 (https://github.com/google/woff2), and then write the @font-face declarations for each weight/style variation. Variable fonts make this even easier, since you can get by with just the one declaration.

One could further optimise them for size with fonttools, to do stuff like subsetting by unicode ranges (https://github.com/fonttools/fonttools), but that's quite optional. Unless your font includes CJK, it's probably not that big to begin with.

> The sentence "self hosting fonts is as easy as making the static font files available and then adding a few lines of CSS" is a complete lie and you could tell they have never gone through the process themselves and were just making things up.

It's not a lie—I've been doing exactly that as long as Google fonts has been a thing.

I think people are confusing what was required in the back in the day when browsers were buggy and supported different font formats--15+ years ago.

The technique was called the "bullet proof" @font-face syntax because it "solved" getting web fonts to work across operating systems and devices in the 2010's [1]:

    @font-face {
      font-family: 'Graublau Web';
      src: url('GraublauWeb.eot');
      src: local(''),
        url("GraublauWeb.woff") format("woff"),
        url("GraublauWeb.otf") format("opentype"),
        url("GraublauWeb.svg#grablau") format("svg");
    }

If you weren't doing web development back then, you don't understand what a revelation this syntax was for supporting cross-browser web fonts. There were even websites that would generate the syntax for you. BTW, woff2 didn't exist then.

It seems that some developers, like the Japanese soldiers who didn't stop fighting WWII until the 1970's because they didn't know the war ended in 1945 [2], still believe dealing with fonts in 2025 is like it was 15 years ago.

It's never been easier to self-host fonts… why make an additional HTTPS request if you don't have to?

There are plenty of utilities to compress TrueType or OpenType fonts to WOFF2.

[1]: https://www.paulirish.com/2009/bulletproof-font-face-impleme...

[2]: https://en.wikipedia.org/wiki/Hiroo_Onoda

Saying that Chinese people are okay, and are not necessarily represented by the actions of the Chinese state, isn't about anything more than trying to prevent violence and hate from being targeted towards ethically East Asian-looking people. There is precedence for this kind of violence, and if we're angry at China for human rights abuses, we should not breed an environment in which the human rights of Chinese people are put at risk in other countries.

According to the article, "APU with a disabled or defective iGPU" and "the AMD 4700S lacks display outputs".

Built-in Windows controls, like buttons, scroll bars, etc. are updated with each system release. However, they are relatively inflexible, and no one uses WinApi anyway, so most frameworks and apps build their own components, with varying dedication to emulating the "native" style. Built-in controls also don't perform much in the way of layout (I believe the only way to position child HWNDs remains manual absolute positions?) so while your button might look native, your collection of two buttons won't.

My guess is MacOS's consistency comes from some combination of developer incentives, and UI toolkit design.

> I believe the only way to position child HWNDs remains manual absolute positions? so while your button might look native, your collection of two buttons won't.

I thought the native APIs provided some kinds of constraints, like ‘these go into corners, and this is next to that’? Such approach is sorta necessary when windows can be resized. And I thought that UI builders like Visual Basic depended on these constraints. However I didn't do much manual UI, so perhaps the programmer indeed has to recalculate everything in pixels when something moves or is resized—like we did back in the day before we knew better.

Which is the "native" API - win32, MFC/ATL, Form builder, WPF, or MAUI? If you're dealing with HWNDs directly, it's either win32 or MFC/ATL, but those haven't been touched in tens of years in favor of the current .NET APIs.

Win32 does not do automatic layout.

What is the use of wealth, if not to increase one's quality of life?

It displays for me, in place of the favicon (but I'm on nightly, so this might be a more recent change). Here's what it looks like for me: https://imgur.com/a/EwaKsNt

The difference is compact mode. In compact mode it replaces the favicon, in normal/touch mode it adds an extra line with the "PLAYING" text.

> an extra line with the "PLAYING" text.

If anyone knows how to turn this off, or prevent it moving the tab title up and down please let me know.

Pausing a video in one window then a second later having my attention drawn back to it by the movement is very annoying. I'm on xubuntu.

Interesting, here's what I see now on 89.0: https://imgur.com/a/bItmejF

I swear the "PLAYING" text wasn't there when I first updated. Seems like maybe they're still ironing out how to handle it.

FWIW, the playing text is longer in the localization I use, and when cut off (many tabs) it's not really readable. :)

Sure, but not all people who use computers are programmers, and programmers make up a small minority of computer users. Much of the value in computers come from augmenting other workloads. There are no shortage of people composing e-mails and documents, or consuming content, in non-English languages. Probably more than there are fluent English users.

I have an app installed that essentially draws over the entire view to darken the screen, while all interactions pass through transparently. It can't draw over certain areas, like some popups and the notification bar, but most of that wouldn't matter for malicious interactions.

Apple, maybe, but Google services don't operate in China.

> by the way, in contrast with the... Start Menu!

Well, good news! I don't know when this might've changed (I have animations enabled), but I just tested it on Windows 10 2004, and the start menu doesn't animate with animations off.