3 ms·
If considering all English translations, you would certainly get a wide variety of opinions about what should be the default for everyone, if default there be;
by chrismorgan 6y ago
If considering all English translations, you would certainly get a wide variety of opinions about what should be the default for everyone, if default there be; yet I suspect that the substantial majority of informed opinions would support the KJV, NIV and ESV, with all others trailing far behind. As regards user-facing systems, BibleGateway.com has long used the NIV as its default. I certainly wouldn’t; I’m not fond of what the NIV has become. All in all, for an API I would agree with you and recommend no default.
But for a site like this, you’re only considering public domain translations. Given that, I think that the WEB is a reasonable default, specifically because of the paucity of available options. And when you have fewer options, I think a default is more useful—“you don’t have the one I want, so what should I use instead?” will cause paralysis that a default resolves.
On the available public domain English BIbles: you’re generally limited to the KJV, a variety of more obscure translations older than the ASV, the ASV, and the WEB. (Fun fact: the old testament of the RSV and the first edition of the new testament are now public domain for most of the world, including Australia where I live. I grew up with the RSV and still use a second edition RSV as my primary Bible.) Out of these, I don’t think there’s much contest: the KJV is popular for historical reasons but a poor default for the aforediscussed reasons; of the obscure translations, most or all are either unconventional in some significant way, or would be widely acknowledged to be superseded by the ASV, by direct or indirect lineage; that leaves the ASV and the WEB which is mostly just a linguistic update of the ASV. That leaves the WEB as a sensible default public domain translation.