Nutthead StudiosIt's a shame that #Rust has an extraordinary runtime, but a compiler as slow as molasses,
Michał Fita@__nutthead__ normally Rust doesn't have runtime, it's compiled down statically to the target machine code. There's kind of runtime bit with async.
@michalfita A runtime "what"? It has an extraordinary runtime performance. And I assume you are referring to tokio for async/await?
PS: even a hello-world program written in Rust creates a binary about 4MB in size, unless you specifically ask the compiler not to include the quote and quote runtime in the target binary.
"Runtime" is an overloaded term.
@__nutthead__ What? 4MB? You meant debug build, right? One with all symbols for backtrace of the standard library included in the build.
W/o extra optimisations release build of hello world has 415kB on x86-64 Ubuntu.
@michalfita Even if you optimize with the -O flag, the binary is still 3.7MB. Only when you strip the symbols it becomes 360K on AMD64 Ubuntu.
I read Reddit too. Even though I am a newbie at Rust, I stumble upon the fight between Go and Rust fans enough to have seen all this...
And without symbols you lose function names in stack traces, debugging/profiling becomes nearly impossible, etc. unless you make .deug files.
Long story short: by runtime I was referring to runtime performance.
@michalfita And the main subject of my topic was not runtime: it was abysmally slow compiler of Rust.
@__nutthead__ Recently I find it faster than gcc for C++. I'm cheating, however, with `sccache` running for every Rust build.
@__nutthead__ I built mine with `cargo build --release`... I think we _kind of_ compare apples with peaches, or rather different methods of their collection.