Or, the context of your use, for a site that covers many thousands, is different than mine, leading to a different experience. The most-being-wrong applies ver

Or, the context of your use, for a site that covers many thousands, is different than mine, leading to a different experience. The most-being-wrong applies very reliably for any API, library, or language that isn't stable through time. You probably work C, or similar, where backwards breaking changes, or shifts in "the correct way", are rare. I'm jealous! The answer being wrong at any point in time is probably < 10%, in my experience.