This is especially true when you look at costs spread out over an extended period. For example, the entertainment concern I described above shelled out a substantial amount of coin to build a significantly-complex Token Ring network that went to every desktop in the organization. However, they only had to build this network once. I use Ethernet here and wouldn't dream of trying to rely exclusively on Token Ring, but that's because my network is relatively new and small, and I'm not in need of certain elements that Token Ring offers. Indeed, there's lots of places where these advanced characteristics just aren't needed.
Nobody needs prioritization and Jumbo frames on their inkjet print server.
And to tell the truth, Ethernet has had lots of advantages over Token Ring. We do need better networking infrastructures than Ethernet. In this regard, there is very little advantage in using one or the other when you're trying to bring a robust infrastructure all the way down to the desktop. Maybe the best approach from here on out is to examine the true costs of building a network that can handle the load, and then choosing the technically-superior solution that can get you there in the long run. Rather than thinking about this quarter's budget, think about the cost benefits over the next few years, and get it right the first time.