I don't really know what vaporware means in the context of an open process where the coding work is transparent.
Certainly when a vendor claims something to be delivered "later" and the work is entirely opaque (meaning it is impossible to independently assess when if ever the delivery will occur) that can be described as vaporware.
It is not a delivered feature, on that much we agree.
Agree
Most cryptocurrency users probably fall into the "using residential or other limited-bandwitch" category, but I cannot think of any other cryptocurrency that needs QoS. I am not well read on this topic so I may be wrong.
They all do. Some implement implicitly. There are merits to both implict and explicit implementation of i/o scheduling. (QoS is a bit of a misnomer, AFAICT.)
Let me rephrase, "I cannot think of any other cryptocurrency that
As I am not a developer at all, you are mistaken,