4 ms·
It's still there, albeit not for long. There were ample reasons in the past whereby going down this path made architectural sense. The primary one being multi-
by gniting 2y ago
It's still there, albeit not for long.
There were ample reasons in the past whereby going down this path made architectural sense. The primary one being multi-language support. Since then, TS and JS have found their way to the top of "the programming langs of choice" charts and so we're digging into removing the Rust based components and making them optional.
We'll share more on this in the coming weeks.
- maxloh 2y agoHow would that affect the now unofficial Go client?
- gniting 2y agoGreat point! We'll be taking all of that into account. The idea is not to make this a breaking change as a lot of community work went into the various lang support modules that are available. Partly this is what makes this a fun and interesting challenge that goes beyond just the tech and the team is eager to get their hands dirty to solve this. For now, lots of ideas on the board. Once we have a plan, we will start to share in order to get community feedback.
- mind-blight 2y agoThat's great news. The rust client has eaten a few days of my and my co-workers' life by causing deployment issues