It takes ~30sec to prepare an xl cup of instant coffee for me. It takes a minute for a cup of "turkish" coffee, or two minutes if I wait for it to settle down before pouring.
It's not great coffee, but I'd say it's above average.
verstra
joined 2 years ago
Oh god, that changes so much.
I've built a caterium computer factory with 200+ machines total and I used 4 different blueprints for it. It was still a lot of work because each blueprint had like 3 connection points that needed to be connected manually. Very tedious, will not try again.
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.
From what I read, it could easily be a tauri app, without a backend: just index.html in your system's webview.
I did also forget to say it does look very nice, with animations and proper polish!
If you do delve into improving the performance, I suggest using Rust and no_std crates for dealing with images, such as https://docs.rs/zune-jpeg/latest/zune_jpeg/.
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've tried nextcloud, it felt too slow.
Why would you want that all in one container?
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.
Any language feature with such a long definition is a bad language feature.
The less such features, the better the language.
Thus, javascript is not a "good" language for expressing your programs.
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.
If you are interested (and can pull together a bit of funding) I can look into how we could do this optimization in WASM.
It's JavaScript.
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.
The secret: 7.5kW induction plate.