Rust will take time - it has a few concept that I haven't seen in javascript/python/java/C++ family of languages. But it gives "zero-cost abstractions" i.e. a way to write high-level code without any performance penalty. And it has great tooling and WASM support, which is what you'd be after.
But as I said, it is all not worth it now, just for this application.
Sure, do recommend - I'd need a basic overview, but not too deep, as I don't have enough motivation for in-depth review of all socialist governments in the last two centuries.
It would probably take some time to get it working, but it would probably increase performance and support any format you can find a crate for. But it does not seem like it's worth it.
I'll add this to my list of "things I might to when I don't have a side project to waste my time on" :D
I don't want it, SeaFile provides only such conglomerate Dockerfile. And I didn't have much success with writing my own Dockerfile for it. It's terrible.
This is just what I need. A few months ago, SeaFile shat the bed and I just could be bothered to fix it. It's deployment is a mess - a server, then a frontend host, a reverse proxy, a database - all in one container!
So I will try this out. I was contemplating building a thing like this myself, so I can contribute fixes/features too.
And it is slow, but not as slow as I expected it to be. I've optimized a photo I've taken with my DSLR, 6.3MB, 24MP, JPEG. It has taken ~50sec on this phone, in Firefox.
I know, it's a phone, but also, my phone can and does save, optimize, and apply filters to such images in <1sec.
Wait, how does this work in-browser? Does it send the photos to the local server where image magick does the job, or is it using javascript to read/write images, or does it contain WASM to do that?
Or post to gemini instead