On Wed Feb 15 18:49:32 2023 +0000, Zebediah Figura wrote:
I'm not advocating to improve their whole API; only modifying the parts we care about seems reasonable to me. The point is that if we have to make a change, I don't see why we should do it here instead of there.
I generally don't think you're wrong, but the tradeoff isn't visible to me given how little programs use Vosk, and even if they use it, it isn't via the C-API. Say the lib becomes more popular over time and speech recognition a less niche thing on Linux, I'm inclined to upstream it. Just keep in mind, what if we want to change to some different lib in the future? Additionally, I don't want to clutter their API with just some "C-Compatible"/non-Json functions.