Have a look at some of the historic photos of Sir Edmund Hillary and also some books from Royal Robins - you'll see the bowline featured as a prominent tie-in knot. These guys knew that #1010 in its original form needed to be 'secured' in some fashion to prevent it from working itself loose.
Although one must wonder ... , as RR in his book shows
the mere
overhand back-up, and my annotation there
decries that as putting a dubious knot to be secure.
Still, if that was the state of the practice, did it really
work? --perhaps better in the (stiff but) laid ropes of
the day, and not so well in kernmantle? (Hillary wasn't
doing so much of the technical-climbing, vertical stuff, methinks.)
You can die just as quickly with a poorly/incorrectly tied #1047.
But do you? If the usage splits say roughly 25/75% respectively
of
bowline vs.
fig.8 eyeknot,
and the accident occurrences come at the opposite proportion,
that is quite some indictment against the
bowline !!
(Where even 40/60% of accidents would show a bias.)
Thus, it is important (a) to understand the facts, and
(b) advocate
bowline back-up, and self-checking
("... give the knot a tug ...").
Make your own evidence-based assessment --don't just take some unknown persons word for it.
OTOH, one can question each person's ability to do this.
It's better that some
collective wisdom be heeded
--where "heeded" doesn't preclude further consideration.
(I had pretty good, I thought, reasoned assessment that
a #782 (? --converts to #1452 in capsizing) made a good
offset abseil-ropes joint, but that came a sudden rebuke
when in simple manual loading of such a knot shows that
it could capsize one side ahead of the other and just spill!!)
Your tie-in knot must be proven to work in all possible loading profiles associated with climbing and falling.
Hmmm, I'm losing the urge to see
ring-loading as some
likely possibility for tie-in knots, where the eye is kept
small and thus close to everything --hard to conceive
of how it could be thus loaded. (And there is a long
history of this being a non-issue here, yes?!)
You also need to have 100% flawless memory retention of how to tie the knot --error free.
Errr, hmmm, thinking of my own errors, which I recognize
in the process, I vote for a process that defends against
imperfection rather than one that bans it. Might be
that the knot limits "errors" to variations that still
result in security, given all of the tucks, et cetera.
--dl*
====