nanomsg was an interesting successor to the bloated&#x2F;C++&#x2F;LGPL zmq, but it succumbed to old ways that don&#x27;t work anymore.<p>It&#x27;s 2016 and you can&#x27;t run an (intended) global-scale open source project by just being &quot;code nerd in chief.&quot;  If you can&#x27;t run an open feedback-driven community <i>and</i> if you can&#x27;t be chief architect (also means communicating plans constantly, not just &#x27;do whatever you want&#x27;) <i>and</i> if you don&#x27;t possess technical and professional excellence (also means being responsible with security issues and timely resolving of user issues), then you don&#x27;t actually have an &quot;open source project,&quot; you have a private uploaded code repository other people can see publicly.<p>Gone are the days of 1995 when you could live on an island and upload your new code once per year and everybody would leave you alone and praise you in computing magazines for being a genius.  Now you&#x27;ll have 1,000 issues on GitHub and requests for public appearances and proposals for changes and important security flaws to fix and requests for extensive communication about current designs and upcoming features.<p>The whole &quot;i&#x27;m going to do this all on my own, everybody else go away it&#x27;s my code&quot; doesn&#x27;t work anymore.  Those projects are now destined to fail on their own without open and scalable community leadership.  The good projects &quot;get it&quot; and the old guard are toppling as we speak.  In another two years, nobody will trust open source projects without a stated scalable community model and codified successorship plan.