Fonts are still a Helvetica of a Problem
Fonts emerge here as both a major security surface and a surprisingly complex piece of infrastructure, with past exploits in font renderers and tools like FreeType and FontForge illustrating how malformed font files can lead to remote code execution. Commenters weigh the trade-offs between downloadable custom fonts and system fonts, balancing design control, branding and typography quality against user tracking, accessibility, and the risk of buggy or vulnerable rendering pipelines in browsers and operating systems. The thread also touches on vector vs raster formats (SVG vs PNG) for text-heavy graphics and points out inaccuracies and gaps in popular histories of digital typography.
Font security and attack surface
- Multiple comments stress that font parsers are a serious attack surface, with historic exploits in TrueType, FreeType and OS font stacks.
- Browsers often hand downloaded fonts to OS renderers not designed for hostile input, increasing risk.
- Suggested mitigations: sandbox anything processing fonts, avoid
system()-style calls around font tools, and prefer trusted/local fonts. - Some users disable downloadable web fonts entirely due to security and tracking concerns.
System fonts vs custom fonts
- One camp prefers system fonts for safety, privacy, consistency, and respecting user preferences (size, weight, accessibility).
- Others argue designers need strict typographic control; system fonts vary across platforms and can break layout, especially in commercial work.
- There’s a call for a small, cross-platform, open set of “universal” system fonts, but skepticism that designers or companies would stick to it.
Design vs “styling”
- Strong distinction made between functional design and purely stylistic “dribbble-style” aesthetics.
- Some argue that designing without understanding users’ devices and context is poor design, even if visually polished.
- Others note that variable screen sizes and fonts already make digital design hard; removing font control increases complexity.
SVG vs PNG and vector vs raster
- Debate on why text-heavy diagrams are often shipped as PNGs despite good SVG support.
- Pros for SVG: sharp at any DPI, smaller for many diagrams, more future-proof; cons: tooling is harder, SVG rendering and text layout differ between viewers, many bugs and inconsistencies.
- Common workaround: convert text to paths in SVG for visual fidelity, at the cost of filesize and accessibility.
- Raster images are simpler, more predictable, and historically more performant, but scale poorly on high-DPI displays.
Historical and technical corrections
- Several comments correct the article’s font history, noting earlier outline font systems and disputing claims that Adobe “introduced” outline fonts.
- Clarifications that TrueType itself was freely licensable, while some advanced Apple typography tech was not.
Miscellaneous
- Discussion of bitmap vs vector terminal fonts, readability, and DPI preferences.
- Lighthearted puns on font names and the article title.