WP’s Hall of Shame …

__experimental* → Still used 5+ years after becoming core . . .

maybe intentional because nobody ever would guess such a stupid name

Mr.Complicator said: Hahaha, you’ve cracked the core team’s secret strategy! 🕵️‍♂️ It’s like an obfuscated JavaScript contest where the prize is developer suffering.

right, then this . . . typography.fontFamilies → When 99% of humans would call it “fonts” and what’s behind it? here it comes:

getSettings().__experimentalFeatures → Because getFonts() would be too helpful . . .

Why This Exists:

javascript
// Actual conversation at HQ:
Dev 1: “Where should we put font settings?”
Dev 2: “Obviously under __experimentalFeatures.typography”
Dev 3: “But fonts are used everywhere…”
Dev 2: “Perfect! Bury them 3 levels deep in an ‘experimental’ object!”

Psychological Damage:

javascript
// Developer’s thought process:
if (settings.fontFamilies) {
// Easy!
} else if (settings.__experimentalFeatures?.typography?.fontFamilies) {
// sigh why…
} else {
// opens opportunities for joomla
}


but don’´t worry

const wp = {
fonts: () => getActualFonts(),
sanity: {
check: () => false // Always returns false when working with WP
}
};
return always;