Self-host your compiler, you cowards!
Several times this year, I’ve read about new systems programming languages, usually created with robotic help. That’s great! New languages expand how we think about programming. I’ve noticed their compilers are almost always written in Rust.
Rust is a fine systems programming language in its own right, but a systems programming language, the kind of language meant for writing things like compilers, ought to be used for its own compiler before it’s used for any other serious work.
I’m kidding about the cowards part of course. I’m sure all language designers are brave and kind, even if some look like serial killers.
Apparently there are thousands of code modules and Soong keeps literally everything in memory while calculating dependencies? Which makes me wonder what the hell the blueprint files actually do if it’s still so absurdly heavy.
Considering how the requirements went from four gigs to over thirty over the years, it wouldn’t shock me if RAM use grows exponentially with the number of modules and they just put up with it because the Google devs use cloud machines with practically infinite resources for building and therefore don’t have any impetus to fix it.