A few days ago, I posted about this project on Hacker News and got (rightly) chewed out because I said I used WASM in the title, but the repository only had Vanilla JS at the time (I had pushed the wrong branch). I took the feedback seriously. I didn't argue, because facts are facts and they can't be changed. I spent a weekend completing the WASM core and merged it.
Now, v0.4.1 has been officially pushed: Pure Rust: no wasm-bindgen, no image crate. Only std and manual pointer arithmetic. Small: the binary is about 20.0KB. Smart: automatically enabled only for images larger than 20MP to bypass V8 GC stutter. Auditable: see SECURITY.md for proof of an empty dependency tree.
I hope I can regain everyone's trust. Thank you to every person who has given a Star. Your support is the biggest motivation for me to keep going.
After all, as the old saying goes: "Talk is cheap, show me the code!"
I've merged it into the main branch. It's live now. No longer hidden in a development branch. You can see the src/wasm-resize folder on the repository homepage. This time, I'm not joking.
Many thanks to everyone who has starred this project.
zayoka•2h ago
This update fixes and improves numerous issues, including more complete WASM support and enhanced logic, boosting performance and efficiency. We've fixed a memory leak in the worker callback and improved error handling during worker initialisation. We've updated the cache key generation to use the FNV-1a hash algorithm, including handling parameters to avoid collisions. Additionally, we've optimised the image processing strategy based on pixel count and WASM availability to ensure better quality and performance. We've also adjusted the content security policy to comply with new inline script handling.
Plus, we've added a little Easter egg: In the settings' "About" tab, click "GenresFox" three times in a row to trigger a Christmas-limited Easter egg!
Wishing you all a Merry Christmas! Here's to moving forward together in the new year!