Earlier quoted context omitted.
As both a developer and designer, this comment seems absurd to me. Art and information both play vital roles in the human experience.
A computer and any code that execute within one are tools, and tools must first and foremost serve to enable its user. This means when it comes to software design, function always trumps form. A tool should never be designed with form over function in mind, it must always be function over form. Any form (design) that impedes the function must be culled with extreme prejudice. When it comes to remote fonts, they slow…
Show example please.
> they violate privacy rules and laws,
Show more example please. Let's not forget when you access a webpage, the server already know what IP address you are connecting form. If the web font is loaded from the same host, the owner of the page does not violate any privacy rules than servicing you the page.
> they impede accessibility when fallbacks fail or do not exist
This is only when it failed.
> Most of us also know from experience that software designers by and large prioritize form over function, oftentimes with complete disregard for the function thereof.
You may have experienced designers who are bad at their job, but it does not mean a good design, including using or not using web font, help deliver the function better.
> So I second grandparent post's opinion: Screw designers. Removing them from the development process will bring about more net benefits than any benefits they might be bringing to the table.
I welcome your view, despite how myopic it is, and I hope you live by your value, which means code using vim/emac, not using any GUI tools, and browse the internet using lynx the text internet browser.