What in God's name is thrift and why the fuck does every fucking library that supports it have no actual documentation. DOES EVERYONE COME PREINSTALLED WITH THIS MAGICAL THRIFT KNOWLEDGE??????

@chatgpt what is thrift (speaking about programming and libraries)? Be elaborate. What it's used for and do I need it?

@netikras
Thrift is a lightweight, efficient, and cross-language remote procedure call (RPC) framework developed by the Apache Software Foundation. It enables efficient and seamless communication between services written in various programming languages by generating code for serialization and deserialization of data structures. Originally developed at Facebook, Thrift has gained popularity in the software development community for its ability to streamline and optimize communication between different services and systems.

Thrift essentially allows you to define data types and service interfaces in a simple definition language, which is then used to generate code for multiple languages. This makes it easy to create APIs that can be used across different programming languages without having to manually write the serialization and deserialization code for each language. By using Thrift, developers can focus on the functionality of their applications rather than spending time on the intr

icacies of data serialization and communication protocols.

Thrift is commonly used in scenarios where you have microservices communicating with each other, as it provides a standardized way to define data structures and service interfaces. It is also widely used in distributed systems where different components need to communicate efficiently over a network.

Whether you need to use Thrift depends on your specific use case. If you are building a system with multiple components written in different programming languages that need to communicate with each other, using Thrift can simplify the process and improve efficiency. However, if you are working on a small project that does not require communication between different services or components, you may not necessarily need to use Thrift. Ultimately, the decision to use Thrift depends on the specific requirements of your project and the complexity of your communication needs.

Sounds interesting. I use xmlrpc for that since it's native in python. I made it async in backend while client can use stdlib (xmlrpc.client.ServerProxy). I don't like grpc, what the fuck is it even. Will check thrift. Thanks!

I investigated it and a huge nope for me. That project will take over your whole project. It doesn't understand it's just a tool, not the software itself. I see no benefits in using this over some other rpc. The xmlrpc from python works like this: 7 == client.my_math_stuff.add(3,4). It's on top of http. No install client side required. Backend is just server.register_instance(obj) and it will contain all methods of the class and it will be callable as shown before. In this case the math my_math has a subclass or variable named my_math_stuff. I don't know why it's not more popular. Because xml is a bit broad? Supervisorctl uses it for example.