Earlier quoted context omitted.
> QoS does not stand for Quality of Service. It stands for Quantity of Service. Fuck you. You aren't even trying to have a reasonable conversation, are you? You're welcome to attempt to argue that there's an unavoidable equivalence between QoS as everybody defines it and the other concept you're trying to equate it to, but you have to actually make that argument, not just declare the definition of QoS to have changed…
> You're welcome to attempt to argue that there's an unavoidable equivalence between QoS as everybody defines it and the other concept you're trying to equate it to, but you have to actually make that argument, not just declare the definition of QoS to have changed because you don't like what it means. QoS still stands for Quality of Service. QoS being a quantity of service is a very well known term, pioneered and po…
So you're still trying to re-define the literal text of what the "QoS" initialism expands to, and now you're also trying to narrow the scope of QoS as defined by everybody else.
There's more to QoS than just deciding which packet to drop. You also have to decide when to drop a packet. This second aspect is what makes QoS not a zero-sum game when faced with real-world traffic.
> QOS might work OK on networks with microspikes but it completely breaks on networks that are > 20% oversubscribed.
What exactly do you mean by "microspikes"?
20% oversubscription is laughably small compared to the disparity between my 1GbE LAN and my 50Mbps WAN connection. QoS makes a world of difference for the users on my LAN. Oversubscription just means you'll actually get the opportunity to notice the difference between having QoS and having a dumb FIFO. Nobody's actually asking for a circuit-switched Internet, or anything that would require a circuit-switched Internet.