I generally like #rustlang but I think every project developer should be forced to use it on a Raspberry Pi with 4GB RAM... had to build Vaultwarden (https://github.com/dani-garcia/vaultwarden) on one, and man,,, after 15 minutes compilation is no longer running because the device went OOM and now is so hot the fan is louder that a datacenter server...
Just to be clear, I think this is a Rust problem, not a project problem.
@danielsreichenbach It is neither a Rust problem nor a project problem in my opinion. You shouldn't compile on a potato xD
Don't get me wrong, I love such boards, I even have one. But you can just cross compile and transfer the binary.
@mo8it But that is the thing, it is not a potato. I can compile a full server for World of Warcaft on it, the machine will not go OOM and also not die of heat. It is a Rust problem, not a problem of resources on that device. And if Rust is to be an alternative to C/C++ it should also be able to run in the same places IMHO. Don't get me wrong, I do not want to bash Rust, I would rather see a discussion happening on how to make Rust work properly here.
@danielsreichenbach @mo8it how many threads is it using to build? I’m guessing the default isn’t one.
@ambihelical @mo8it nope, it's basically spawning about 20 threads.
@danielsreichenbach @mo8it so -j N will make it work for some N. Probably cargo should be a little smarter when system memory is limited and pick a smaller N and this doesn’t sound very difficult to fix.
