I thought it was stuck for a minute. It's an anemic computer, but there's no way the webserver was taking ALL DAY to compile rust. Then I looked closelier. Horrified, rocking in the fetal position, vomiting.
YOU HAVE TO COMPILE EACH PREVIOUS VERSION TO COMPILE THE NEXT ONE. IT'S BEEN COMPILING TEN DIFFERENT VERSIONS OF RUST ALL FUCKING DAY AND THERE'S NO END IN SIGHT.
WHO CAME UP WITH THIS FUCKING HORSESHIT? ARE RUSTACEANS ALL TOILETLICKING PASTE-EATING HELMET-WEARING SHORT-BUS-RIDING INBRED CLOWNS?

@idiot >WHO CAME UP WITH THIS FUCKING HORSESHIT?
People who need to compile everything from scratch (no, really)

Rust doesn't officially support compiling itself from scratch if you don't already have a rust compiler. And with how often the language changes, they only test that previous minor version can compile the next one, so unless you're feeling brave, that's what building from source does everywhere.

Anyways, next time you end up in the situation of needing to compile rust from scratch, just download a binary package for the one-before-current rust version and use it to compile the current one. Just like you'd bootstrap a C compiler. If you do gentoo just to get -march native for everything you're not gonna miss out on anything except heating by doing that.

@idiot ok compile a C compiler without using a binary version of a C compiler

@pi55d "No way to stop this" says developers of the only language where this happens.

@idiot Rustaceans mean it seriously when they say they want to replace C

@pi55d But that's the other thing: I already had a rustc. This isn't inventing the universe from scratch, this is just a failure to bootstrap nightly. And every dickhead rust dev targets nightly.
GCC doesn't take this long to bootstrap and that's at least four compilers.

@pi55d if the solution is the choice between thrashing your ssd to death bootstrapping eighty different versions of rust, versus, "bro just download this binary bro you can trust me I promise bro ;)" it might as well be proprietary software. No amount of whataboutism is changing my mind.

@idiot OpenJDK does it too but it’s not nearly as bad (t. have recompiled Java a million times for GC benchmarking)

@idiot Guix only had Java 18 so I had to build up to 24 manually.
It’s so much nicer when it only takes 10 minutes and releases are bi-yearly

@bronze @idiot go is simply better

@theorytoe @idiot i've never had a single bad experience with programs made in go despite it being a "woke" nu-lang

@bronze @idiot
>woke
im pretty sure rust is more woke than go, ive seen more unneccisary proselytizing for rust than go, because go has actually caught on in the industry, whereas rust still seems to be less prevalent

also (most) go devs seem to understand its intended uses and limitations, whereas the same cannot be said about rust devs

i find the biggest critics of go to be from the c++/rust side of programming, whereas many C devs I see enjoy it quite a bit.

@bronze @theorytoe @idiot didn't Uriel love go too?

@PurpCat @theorytoe @bronze @idiot
Yeah

@pi55d @idiot
That's stupid.

@sysrq @theorytoe @PurpCat @bronze @idiot >made go
KenThompson-3043448928.jpg

@idiot @sun Only binary package on my desktop. I even compile WebKit

@idiot why do you trust the original gentoo seed archive and not dev-lang/rust-bin?

@sysrq @idiot it is yeah

@idiot i have a special hatred of rust devs its not even funny
its because of shit like this
apparently the rust "people" seethed when they saw gcc-rs because apparently you cant have other compilers for their god's gift to man language

@theorytoe @bronze @idiot Literally the single single issue I have with go is the package manager brainrot.

Guy who makes a rust -> c transpiler so he doesn't have to deal with rust nonsense

@tyler @graf @idiot @sun go is great you don't need runtimes for your binary

@idiot
MEMORY SAFE™

@phnt @bronze @idiot
yeah... its not pip levels of awful.. but yeah it still sucks

@idiot MASK THAT SHIT YOU DO NOT WANT TO EMERGE RUST

@pi55d @idiot

@idiot get an m4 ultra

@bronze @theorytoe @idiot neither have i with rust either

@mischievoustomato @idiot those still cost all of the limbs in your body

@kirby @idiot it's not that expensive, let me check

@mischievoustomato @idiot nothing a few days of drug dealing couldn’t do

@mischievoustomato For a webserver?

@idiot yez.
in reality, for a server that does a lot of shit I'd get an intel chip.

@idiot @pi55d this is why i like nixos/nix

@idiot yes

@idiot you're bootstrapping it out of ocaml like,,, yeah

@idiot @pi55d

> only language where this happens

> While developing Pascal, Wirth employed a bootstrapping procedure in which each newer version of the Pascal compiler was written and compiled with its predecessor. Thus, the 'P2' compiler was written in the dialect compilable by 'P1', 'P3' in turn was written in 'P2' and so on, all the way till 'P5'. The 'P5' compiler implemented Pascal in its final state as defined by Wirth, and subsequently became standardised as 'ISO 7185 Pascal'.

@idiot SAFE AND SECURE !

@phnt @theorytoe @bronze @idiot they added "optional" (((telemetry))) on 1.23

@romin @theorytoe @phnt @bronze @idiot
> they fell for the g*ogle product again

@romin @theorytoe @bronze @idiot
I know about it and I wasn't surprised when they added it. At least they have it disabled by default unlike others that went in that route.

@idiot why are you compiling r*st in the first place

@romin I hadn't updated world in like six months.

@idiot never update

@phnt @theorytoe @bronze @idiot
>disabled by default
disingenuous, only the uploading of the telemetry is disabled, they still collect data by default. In the future there will be some oopsies when they enable uploads by "mistake"

@romin @theorytoe @bronze @idiot
Or they could have an oopsie and enable the remote part by "mistake". It's almost the same. The only difference being the length of collection. The level of cancer is still less compared to other languages and their toolchains. It's a trade-off.

@phnt @theorytoe @bronze @idiot how about 0 cancer?

@idiot noone can expect them to test if it is actually necessary....

like i wouldnt mind this shit if there is any technical reason i cannot compile 1.80 with 1.75.

since they go each single version in order i assume they just dont care about users.

i like rust. rust devs on the other hand..... they have systemd dev levels of issues

@idiot feature creep in action, it's multiple layers of rust

@idiot >ARE RUSTACEANS ALL TOILETLICKING PASTE-EATING HELMET-WEARING SHORT-BUS-RIDING INBRED CLOWNS
thats exactly what rust "people" are

@theorytoe @bronze @idiot yes, but they still haven't fixed this https://github.com/golang/go/issues/11100 so i'll keep doing C

@pi55d @idiot Easy; https://www.gnu.org/software/mes/

To add support for C on any new CPU architecture, it's simply a matter of writing a simple assembler in straight machine code and a better assembler in assembly and then a C compiler in assembly and then you use that to compile tcc and then gcc-4 and then the newest later gcc version.

@Suiseiseki @idiot mhm and that's what @idiot was doing, compiling a bootstrap compiler (mrustc) and then stepping upwards through the rustc versions

@pi55d @idiot You cannot build mrustc without a C++ compiler, so before you can think about compiling mrustc, you'll need to get gcc bootstrapped.

With mrustc, you need to compile EVERY SINGLE RUST VERSION from the last supported version, which takes days and HUNDREDS OF GIGABYTES of storage and has high chances of the compile failing.


What he was doing was installing rust-bin and then using it to compile each rust version until the newest nightly build was reached.

@Suiseiseki @idiot

> With mrustc, you need to compile EVERY SINGLE RUST VERSION from the last supported version, which takes days and HUNDREDS OF GIGABYTES of storage and has high chances of the compile failing.

Yeah because mrustc was designed to be able to compile just one compiler version, it's not even guaranteed to correctly compile anything else written in the rust language as of that version IIRC because it throws out a lot of safeguards.

> What he was doing was installing rust-bin and then using it to compile each rust version until the newest nightly build was reached.

Rust-bin has all the same versions available as rust, what is the point of installing rust-bin of 10 versions ago instead of 1 version, aside from heating.