> Imagine having to download a shitty webfont with megabytes before being able to read the website

This is exactly what the article is arguing against, that the content is the most important and it should show immediately, no matter if the font is yet available or not.

> Why not use font-display: swap instead?

That's again exactly what the article is advising people to do. Another action that the article suggests, boils down to "choose a default font that is similar to your custom one, to minimize the effect of FOUT", how does that decrease the value for the users?

I'm not sure if you either read the article then decided to write your comment pretending you didn't, or if you're just rehashing what the article just said for some other purpose.