I disagree that eMunie's is "vapourware".
1. It is function in the client now
2. Anyone can test the client out
3. The database of the client can be queried for the consensus components.
4. More documentation going up this coming week
5. Finally, I can provide source code relating to the consensus should anyone be willing to be legally bound not to leak it.
That to me isn't "vapourware".
Without getting into a semantics argument, let's just say for the purposes of this thread, the term vaporware applies to anything not being traded on exchanges or being actively, natively accepted in commerce.
Your statement is correct depending on the context, as is mine.
Most people however that read vaporware will consider the position of "it doesn't exist", as opposed to the truth in this case of "it isn't ready for general release"
Emunie can't be evaluated until released into the wild because of Realsolid's half correct, half i-don't-know analysis below:
[20:57] <@Realsolid> no one is going to understand emunie to ever work on it besides the dev
[20:57] <@Realsolid> bitcoin struggled and it was much simpler
[20:57] <@Realsolid> bitcoin , for what it needs to do, is a rube goldberg machine
[20:57] <@Realsolid> emunie is like rube goldberg to the square
[20:58] <@Realsolid> it means it will be vulnerable, overly complex systems always are, bitcoin was very vulnerable early on
[20:58] <@Realsolid> im one of the best coders in the world and even i sometimes make mistakes, even when developing ultra efficient killing machines
[20:58] <@Realsolid> let alone a rube goldberg ^ 2
[21:01] <@Realsolid> im one of the best coding, best debugging, best looking motherfuckers you ever seen
Another egomanic, whose comments I'm not going to acknowledge.
There is a saying "The loudest in the room is the weakest" and its never more true than it is when applied to loud developers (of which there is no shortage around here)