What was the most surprising thing you saw or learned in this rewrite process?
The move from Electron helped us remove "native libraries" in Node. Previously we were using Xenova transformers to instantiate the models. This forced us to use multiple package.jsons and added a lot of cognitive overhead to our development. The move to rust freed us up to focus more on feature development than configs and setup. It was surprising because I thought learning rust would set us back much longer, but th…
Show HN: I rewrote my Mac Electron app in Rust
461–465 of 465 posts
Re: Show HN: I rewrote my Mac Electron app in Rust
#462Earlier quoted context omitted.
Would have loved to use sqlite if I could get good results. Maybe I botched the implementation.
Creator of sqlite-vec here, happy to help debug anything if you do attempt to try out SQLite vector search again. You mentioned "VSS" in another comment, which if that was my sqlite-vss extension, I more-or-less abandoned that extension for sqlite-vec last year. The VSS extension was more unstable and bloated (based on Faiss), but the new VEC extension is much more lightweight and easy to use (custom C vector functio…
Re: Show HN: I rewrote my Mac Electron app in Rust
#463I'm curious how you're implementing the image similarity matching. I recently reverse engineered the Apple Neural Hash model and wrote an API to use it in my app for doing image similarity calculations. I found it to be extremely quick compared to some of the other more computationally intensive methods that I was trying to use before.
We're using redis vector modules for cosine similarity. I'm sure there's more to optimize there. Your project sounds cool. How'd you reverse engineer apple's model?
Re: Show HN: I rewrote my Mac Electron app in Rust
#464Re: Show HN: I rewrote my Mac Electron app in Rust
#465Earlier quoted context omitted.
> Please just let us bundle a modern chrome with our apps. please, no. I wish software companies had to pay the hardware they require for their users, then we would have devs using Rust instead of JS and optimizing using ASM just to save parts of cents per instance. And we wouldn't see companies like MS kill well designed and performed native apps for a electron app
Why are you against the idea of an optional feature that lets them keep using Tauri while maintaining browser parity? You don't have to use it.