The database is not released onto the main net after three weeks of dev work. At what point does it become vaporware?
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
The QoS system is only need to deal with the huge blockchain.
No the QoS system is needed to deal with any size blockchain if people are using residential or other limited-bandwitch connections they don't want oversaturated, even temporarily.
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.