4,625 karma · joined February 28, 2010
Mostly Swift, Rust nowadays.
Podcast: https://contravariance.rocks
Twitter: https://twitter.com/terhechte
Mastodon: https://mastodon.social/@terhechte
[ my public key: https://keybase.io/terhechte; my proof: https://keybase.io/terhechte/sigs/ETCgR5hPJ0vXdK9SGFqWuMxn_RglDOVJbeJbseoD-4s ]
One reason to use LLMs is to understand when and how to use them properly. They're like an instrument you have to learn. Once you do that, they're like a bicycle for your mind.
- https://crates.io/crates/lancedb - https://crates.io/crates/usearch - https://crates.io/crates/simsimd
search and simsimd are fast and lightweight, but I'd advise to use lancedb if you're a bit new to Rust as the other two are a bit trickier to handle due to the C dependency (e.g. usearch needs Vec::with_capacity and will otherwise crash, etc).
And then, you take the result of this query and can combine it with a sqlite `in` query.
Or you use SQLite with a vector search extension: https://crates.io/crates/rig-sqlite
> If the user doesn’t know the answer, the LLM can’t help. That’s not just a minor limitation—it’s foundational.
doesn't mean the LLM is not useful. My favorite use case for LLMs is them doing something I know 100% how to solve myself. However, they do it much faster and I can 100% understand their solution and give feedback in case it is wrong. No surprises. I much prefer this as it allows me to work on multiple tasks in parallel.
[0] https://github.com/Lightricks/LTX-Video/blob/main/configs/lt...
I'd venture to say there's more of these than there are UI Editors tbh.
If this is your main use case you can always try to fine tune a model. I maintain a small llm bench of different programming languages and the performance difference between say Python and Rust on some smaller models is up to 70%