Quote from: aminorex on July 23, 2014, 04:43:31 AM

Quote from: btc-mike on July 23, 2014, 04:36:26 AM

Quote from: smooth on July 23, 2014, 03:51:30 AM

Quote from: btc-mike on July 23, 2014, 03:46:25 AM

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

Quote from: smooth on July 23, 2014, 03:51:30 AM

Quote

The QoS system is only need to deal with the huge blockchain.

Quote from: smooth on July 23, 2014, 03:51:30 AM

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.

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 ~~needs~~ requires QoS.

Quote from: aminorex on July 23, 2014, 04:43:31 AM

If I am not mistaken, you are a development team member of one.

As I am not a developer at all, you are mistaken,