The flexibility of FASM/G allows using it to create new compiling/assembling solutions that are effectively pre-processed such that concern about FASM/G build times is a fallacy, and one need only use FASM/G (Compiled Macros) to create their own tools that build faster, e.g. for a specific CPU?

For example, FASM2 uses FASM/G and it's not significantly slower than FASM?

I.e. Help people understand the true power that FASM/G offers? I.e. Need to understand the whole point of FASM/G and the power it provides?

A key point that I am seeking to have addressed is the idea that FASM/G build times relative to FASM may be seen as a reason to not use FASM/G for compiler development, yet the tools produced by FASM/G can be much faster than any Rust or even C compiler?

If build times were an issue, initial startup for a particular environment could be cached as part of the system support -- the same could be done for fasm, too. (Analogous to the pre-compiled headers, [s]ccache, modules of the high-level languages.) To my knowledge, no such effort has ever been made.