All well and good, but overlooks one very important point. Ethernet never killed token-ring, IBM did that for them.
The chipset problem was alluded to in the article. The problem here was that if you wanted to use any of the IBM software (e.g. the PC terminal emulators) you had to use cards with the honest-to-god, gen-u-ine IBM TROPIC chipset (that's the big, square metal thing on an IBM card). Nothing else would do. For all other purposes, third-party cards would do just fine.
IBM, in their infinite wisdom, only ever produced "real" IBM cards as 8 bit ISA cards which, from the price, seemed to be assembled from Unicorn vellum laid on an Unobtanium substrate. Eventually they decided to license TROPIC and the result was the excellent (and sensibly priced) 3com Tokenlink III. As usual with IBM, it was too little too late and Ethernet had its feet firmly under the table by then.
I'm afraid that all the alleged FUD was actually, er, true. You only needed four PCs running DOOM and chaingunning the fuck out of each other to prove that 4meg token-ring shat all over Ethernet for throughput under load. TR gave you a usable (if slow) network with that going on, Ethernet cacked itself on the spot. One of TRs best features was that it degraded gracefully under heavy load. 16meg (that's 16, not 12!!) TR just flew in comparison to Ethernet.
Token-ring had diagnostics and redundancy built in, which is why the cards were pricier than their Ethernet counterparts. Yes, it was entirely possible to have the thing give up without your having a clue what had gone wrong, but if you weren't running something with the capability to diagnose and act on beacon frames and you hadn't made that the designated ring controller, it was entirely your fault! The concept of the token "falling out" is actually an old joke. If you do manage to axe the machine that has the token at the time, it's NAUN (Nearest Active Upstream Neighbour) spots the problem and generates a new token containing a beacon frame to advise the ring controller of the change. This happens in milliseconds, not minutes.
There certainly is a load of FUD around all this, but he's the one pushing it!