thrift

lready has many language bindings, for example: - Protocol Buffer Third-party language bindings: https://github.com/protocolbuffers/protobuf/blob/master/docs... - Apache Thrift language support: https://github.com/apache/thrift/blob/master/LANGUAGES.md - Cap'N'Proto in other languages: https://capnproto.org/otherlang.html

/wang.yuxuan.org/blog/item/2020/09/typed-nil-in-go). In most cases, typed nils are more useful than being a footgun. See https://pkg.go.dev/github.com/reddit/baseplate.go/log#Wrappe... and https://pkg.go.dev/github.com/apache/thrift/lib/go/thrift#TC... for a few examples of typed nils are being useful and providing useful zero values.

pen: Niche web framework. They seem to be working on Python 3 support [4]. newrelic_plugin_agent: see supervisord python-cjson: Unmaintained drop-in JSON library that can be replaced with something else with no effort [5]. python-openid: There's a Python 3 fork which looks nicer than the original [6]. m2crypto: Porting effort underway, but mostly an issue for existing cde - there's no reason to use it for new projects since python-cryptography is better in all regards python-ldap: Issue for many enterprise Django projects (this is the one library in the list that I personally use), but there's a Python 3 fork so it's fine [7]. INITools: Abandoned, it used to be pip dependency so that's probably why it's in this list (?). marionette: see supervisord pathtools: moved to stdlib in Python 3. So, nothing major left in the top 360. All of the huge blockers like Twisted and Paramiko are now green and I migrated all my stuff over. The Fedora porting project has some great insight into how it's going in the real world: https://portingdb-encukou.rhcloud.com/ OpenStack is interesting, too: https://wiki.openstack.org/wiki/Python3 In general, no major libraries left, but lots of grunt work that needs to be done. Some stuff not on the list, that I encountered: python-dajax: Turns out it's a bad idea to put frontend logic in your backend code, but that doesn't make the dependency go away (great opportunity to finally undo that mistake in my code) wxPython: They decided to do a full rewrite instead of a port so it takes some time. Qt, I guess? [1]: https://github.com/apache/thrift/pull/213 [2]: https://docs.ansible.com/ansible/dev_guide/developing_module... [3]: https://packages.debian.org/sid/python/python3-google-apputi... [4]: https://github.com/whit537/mongs/issues/17 [5]: http://artem.krylysov.com/blog/2015/09/29/benchmark-python-j... [6]: https://github.com/necaris/python3-openid [7]: https://github.com/pyldap/pyldap/

still using the thrift protocols (uber/thriftrw) with our rpc library (uber/tchannel), but could have built on top of another IDL format like protobufs (v3). For those curious about the RPC interface, just check out: https://tchannel.readthedocs.org/en/latest/ The interface supports all sorts of things This is all over TCP right now and designed for performance and service to service communication, but there is nothing preventing the addition of HTTP (via XHR or WebSockets) as a transport for allowing web apps to speak with tchannel services. I contributed to the Apache Thrift implementation that allows this (https://github.com/apache/thrift/blob/master/lib/nodejs/lib/...). The implementation for tchannel would be similar, but rely on XHR/WS in the browser and the `http` module instead of the `net` module in NodeJS on the server. It's trivial to write a proxy frontend that relays TJSONProtocol on the frontend to a Thrift binary protocol like TBinaryProtocol or TCompactProtocol. https://github.com/uber/hyperbahn https://github.com/uber/tchannel https://github.com/uber/ringpop-node https://github.com/uber/ringpop-go https://github.com/uber/idl https://github.com/uber/tcurl https://github.com/uber/tcap etc.