Open gedw99 opened 2 years ago
I do have concerns that outside Go programmers, maybe not enough language diversity is making programmers in .NET/JAVA/Python/Rust/JS landscape hesitant to jump on board?
For example, I am a Python shop and use betterproto
to transpile the .proto
definition to Python3 stub - but that requires an additional glue code to let me run async
Python with the sync Python3 stub (for which I use trio
) - all in all a few months of 2 programmers working on it on and off went into this.
In retrospect, knowing what I know now, it's ~2-3hours worth of work to:
betterproto
to transpile the .proto
definition to Python3 stubtrio
as the additional glue code to let me run async
Python with the sync Python3 stubTo date, Liftbridge has been primarily focused on providing a "Kafka-lite" type solution for the Go ecosystem. This is why the Go client is the "canonical" client implementation. The lack of mature client support is definitely going to be a blocker for other languages I imagine. Unfortunately, I just haven't been able to dedicate the time and resources towards supporting other languages.
Is there concern that LiftBridge is not being used enough and so not having the advantage of the Network effect ?