Some limitations and caveats apply (this is only one data developer's experience, etc).
Why are they suggesting skipping straight to this hot mess instead of using a simple and well tested algorithm?
Nor sure I understand? The article explicitly argues for using this simple and well tested algorithm.
Some programming languages manage to absorb change, but withstand progress. -- Epigrams in Programming, ACM SIGPLAN Sept. 1982