compilation

M-Tron drives were horribly expensive, but my main compilation server still run on a bunch of these.

It also has strong support for separate compilation, because we want to make compile times fast.

After all, one of the motivations behind Go was a C-like language with far better compilation time than C++.

What people mean when they say Javascript is web assembly is that Javascript is a compilation target, which is completely true.

First of all the syntactic compile overhead isn't what makes compilation slow necessairly.

"Thankfully" the C++ of the game took so long to compile that we were already using Xoreax Incredibuild to distribute the compilation.

We adapted that setup to distribute shader compilation and brought the turn-around time down to 15 minutes by leaching cycles from several dozen of my co-workers' machines.

It implies that you can define a macro and immediately have the compiler incorporate it in the compilation of the next form, or evaluate some small section of an otherwise broken file.

Go compiles so fast that it changes the way you write and organize code; you would never consider compilation overhead in any decision you made in a Go source tree, where you might do that in a C codebase.

> and there's no compilation step or anything -- then it's almost a fundamental paradigm shift for what desktop software could be.\n> It already makes me dream of a word processor I could hack like that, or a music player.