Is there any library you guys want but can't find?

<p>I&#39;m looking to contribute to the open source community by writing a Go library that you guys need but doesn&#39;t exist. Feel free to throw some ideas my way.</p> <hr/>**评论：**<br/><br/>Spirit_of_Stallman: <pre><p>Native crossplatform GUI. True bidirectional RPC. </p></pre>Aoreias: <pre><p>Tried grpc for bidirectional RPC? If so, what kind of limitations have you had with it?</p></pre>Spirit_of_Stallman: <pre><p>As far as I understand in &#34;grpc&#34; it is suggested to implement it through the bidirectional stream. And there is no way to call client methods on the server or at least pass a new session through some tricky method. Here is <a href="https://github.com/grpc/grpc-go/issues/484" rel="nofollow">issue</a> about it: &#34;I think you need to refactor your service model somehow to fit into the client-server model of rpc&#34;. In the world of &#34;grpc&#34; my desires are wrong by design. So I would like to find a world where my wishes are normal :)</p> <p>ps: I was implement this through the wrapper/manager around net/rpc: the client and the server are init two connections, in which they have implementations of both roles for each other. But at the moment it all looks pretty messy and cumbersome. Soon I will try to implement this through a multiplexer, which would cost a single tcp connection. And all this things needs to be coded. Bui I wish it had been &#34;import &#39;hogwarts.code/archmage/awesome-rpc&#39;&#34; and pew pew pew.</p></pre>Aoreias: <pre><p>This makes sense. I don&#39;t think there&#39;s a way to get around having a client and server at least for the initial connection - something has to listen for a connection provided by a client. Once that&#39;s established though then I don&#39;t see a reason why they can&#39;t pass that connection off to the same handlers to serve the RPC.</p></pre>sacrehubert: <pre><p>A pure-Go implementation of WebRTC.</p></pre>gopher2018: <pre><p>A WSDL library that really work, not just on simple use cases.</p></pre>Hactually: <pre><p>Yeah this would be good. Having to work with SOAP is painful from Golang</p></pre>pubgftw: <pre><p>XML Schema validation</p></pre>Zamicol: <pre><ol> <li><p>An idiomatic implementation of json5: <a href="http://json5.org/" rel="nofollow">http://json5.org/</a></p></li> <li><p>An idiomatic implementation of the JOSE suite which would be these:</p> <ul> <li>JSON Web Signature (JWS) (RFC 7515)</li> <li>JSON Web Encryption (JWE) (RFC 7516)</li> <li>JSON Web Key (JWK) (RFC 7517)</li> <li>JSON Web Algorithms (JWA) (RFC 7518)</li> <li>JSON Web Token (JWT )(RFC 7519)</li> <li>JSON Web Key (JWK) Thumbprint (RFC 7638)</li> <li>JSON Web Signature (JWS) Unencoded Payload Option (RFC 7797)</li> <li>Examples of Protecting Content Using JSON Object Signing and Encryption (JOSE) (RFC 7520)</li> <li>Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs) (RFC 7800)</li> <li>FRG Elliptic Curve Diffie-Hellman (ECDH) and Signatures in JSON Object Signing and Encryption (JOSE) (RFC 8037)</li> </ul></li> </ol></pre>artooro: <pre><p>I&#39;ve used <a href="https://github.com/square/go-jose" rel="nofollow">https://github.com/square/go-jose</a> which is actually pretty good.</p></pre>OdinSQL: <pre><p>implement the parse method for <a href="https://github.com/domainr/whois" rel="nofollow">https://github.com/domainr/whois</a> </p> <p>The fact that each domain registrar has decided to implement whois in a different and incompatible way is what makes it non trivial. </p></pre>Sequel_Police: <pre><p>A native library for mDNS+SD that&#39;s compatible with Avahi</p></pre>soapysops: <pre><p>A high quality, pluggable task queue library. There are a few out there that only work with a specific queue provider, and there are others that have many non-optional advanced features like task result storage. None of them are particularly robust or efficient, and they also usually don&#39;t fit in with Go&#39;s ethos of simplicity and composability. I just want something that lets me give it a function that returns messages to process, a function that marks processed messages as done, a function that processes messages, and it should handle the rest.</p></pre>KevBurnsJr: <pre><p>I have one I made for work but it&#39;s not open source (yet)</p></pre>fazalmajid: <pre><p>Not exactly a library, but GNU Parallel, rewritten from Perl to Go.</p> <p>A modern parallel vcheck, rewritten in Go: <a href="http://www.jasonc.com/code/vcheck/" rel="nofollow">http://www.jasonc.com/code/vcheck/</a></p></pre>artooro: <pre><p>A good MQTT server library. Existing ones have been abandoned or are incomplete.</p></pre>