gurk-rs VS beancount-language-server

I have an old Nokia N900 phone that runs a custom alpine linux-based rom (postmarketOS). Given the limited hardware resources, small screen size, and sliding keyboard, you'll be mostly running terminal applications on this phone (some GUI apps works but the experience is mixed). There are some unofficial terminal clients for Signal [0], and iirc hacker news works with the lynx terminal browser. The N900 might work for this scenario as a feature-minimal phone, but depends on your use cases.

[0] https://github.com/boxdot/gurk-rs

I recently found gurk, a Signal client for linux command line.

gurk-rs

I switched to gurk-rs on my devices and it's amazing, uses zero CPU and have zero impact on battery life. Can be used on desktop, mobile, can be accessed via SSH and tmux.

I want to finish the store encryption implementation in my CLI Signal messenger: https://github.com/boxdot/gurk-rs The initial implementation is already there, but I could not get back to it for several weeks already. First step: switch to sled, second step: plug encryption in between.

It's all intended in service of writing an LSP implementation for an older data-only syntax that doesn't have any modern tooling. For extant projects this one is spiritually very similar to the assists I'd like to offer eventually.

Basically porting a Beancount language server written in JS to one in Rust. So far, this has been a piece of cake thanks to tree-sitter, trie-rs and tower-lsp.