On Jan 24, 2018, at 12:44 AM, Mitar ***@***.***> wrote: the problem is that those checks and balances are, well, checking-and-balancing against old bugs that are no longer the case. Really? I think if you read Plato's Republic, you can see that most cases of issues with governance were already there. Things like corrupt institutions and individuals, concentrations of power, nepotism. Heh, even Ponzi schemes still happen. Time to throw out the obsolete code, and implement at least direct democracy (although I would recommend moving on to XXI century and implement online/realtime democracy). Voting is just a very small part of whole governance application. Even story I linked before <https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/> says: A second reason programmers think that their code is a mess is that it is inefficient. The rendering code in Netscape was rumored to be slow. But this only affects a small part of the project, which you can optimize or even rewrite. You don’t have to rewrite the whole thing. When optimizing for speed, 1% of the work gets you 99% of the bang. So ye, we can optimize/improve that 1% of the whole thing. But rewriting the whole application, this leads to failure. But a voting feature, there is definitely some improvement to be made. Collaboration in general. Real-time, massive, online. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOfhaz0nBgmwCXZV_npWro0HoKs45vWks5tNsM_gaJpZM4BFLPn>.