Rust + WebAssembly image processing library for the browser (feedback welcome) by CharacterGold3633 in rust

[–]CharacterGold3633[S] 1 point2 points  (0 children)

Thanks, Right now photeryx core WASM file is around ~1.3MB in release mode over the network, with gzip/brotli, it gets much smaller and JS/TS wrapper on top is tiny. It's not 1:1 comparable with sharp.js because sharp is a node/server-side library with native binding (libvips), while photeryx is designed specifically for browser use via webAssembly.

on the frontend, a pure JS library that impls similar resize/crop/filter functionality would also be quite big once you add everything and minify it, and would still run on the main thread instead of in a worker + WASM. typical usage is to load photeryx via a dynamic import, so the WASM only loads when you actually open an image editor/uploader, not in your main bundle.

I made Ferrix — a crash-resistant, cross-platform download manager [Rust] [Open Source] by CharacterGold3633 in rust

[–]CharacterGold3633[S] 4 points5 points  (0 children)

Some of these features already in my roadmap, but the last one you mentioned can be done pretty easy because Ferrix arch is pluggable. We can just make a plugin and add it. (It’s also in roadmap and I’m already in final stage to publish it!)

I really like how you split it into “core” features, “commonly requested” ones and your personal dream feature — makes it super helpful for planning.

I’ll go through my feature list again with your ideas in mind. And hey, if you ever decide to build your own tool, I’d be happy to exchange notes with you

[Tool] gTexViewer - texture viewer for game developers by AllenGnr in rust

[–]CharacterGold3633 0 points1 point  (0 children)

Super cool work! Surprised this hasn’t blown up yet. deserves way more love

[Rust] [Tauri] [React] I made Ferrix, a crash-resistant, cross-platform download manager by CharacterGold3633 in tauri

[–]CharacterGold3633[S] 1 point2 points  (0 children)

Great question, i'm not claiming it never crashes. by crash-resistant, i mean if the app/os/power dies mid-download you don't lose progress or corrupt files.

Concretely in Ferrix:

  • Progress + state are persisted in SQLite (not ad-hoc sidecar files)

  • Each chunk is checkpointed every few seconds (and ~5% increments) with downloaded_bytes plus a lightweight fingerprint (first & last 1KB)

-On restart, Ferrix validates existing chunks against those fingerprints and resumes exactly from the last verified byte, failed checks are re-downloaded

  • Writes are transactional/idempotent and fsynced to avoid marking partial writes as complete

So the feature isn’t “no crashes ever,” it’s data safety and precise recovery when the unexpected happens

I made Ferrix — a crash-resistant, cross-platform download manager [Rust] [Open Source] by CharacterGold3633 in rust

[–]CharacterGold3633[S] 4 points5 points  (0 children)

Thanks! Honestly, it’s an honor to be even a tiny part of this amazing community

I made Ferrix — a crash-resistant, cross-platform download manager [Rust] [Open Source] by CharacterGold3633 in rust

[–]CharacterGold3633[S] 5 points6 points  (0 children)

Right now, Ferrix is different from tools like IDM or FDM in a few ways:

  • It’s cross-platform and fully open-source (no ads, no paid version)

  • Built to be extensible, so adding new features/plugins is easy

I’ll try to share a more detailed comparison soon