What new ports are you working on? (I'm just curious.)
Go is already very good at cross-compiling. That can be used to do a new port (as a trivial example, the fact that the compiler doesn't run on NaCl didn't hurt the NaCl port at all). There is a section in the doc explicitly about this. We are doing new ports too (like power64), and I don't anticipate the bootstrapping change slowing them down appreciably.
But Go only cross-compiles well for platforms and architectures it currently supports ;-)
This is an odd thing to say. Go cross-compiles exactly as well as it compiles. If you write a go_YOUROS_YOURARCH_exec script that copies the binary over to your target system and runs it, you can sit at any working system (for concreteness, any x86 system running Linux, OS X, or Windows) and work in a full Go environment. That's actually better than sitting on an unsupported system editing C files and unable to run any program written in Go.
Comments
What new ports are you working on? (I'm just curious.)
Go is already very good at cross-compiling. That can be used to do a new port (as a trivial example, the fact that the compiler doesn't run on NaCl didn't hurt the NaCl port at all). There is a section in the doc explicitly about this. We are doing new ports too (like power64), and I don't anticipate the bootstrapping change slowing them down appreciably.
[deleted]
This is an odd thing to say. Go cross-compiles exactly as well as it compiles. If you write a go_YOUROS_YOURARCH_exec script that copies the binary over to your target system and runs it, you can sit at any working system (for concreteness, any x86 system running Linux, OS X, or Windows) and work in a full Go environment. That's actually better than sitting on an unsupported system editing C files and unable to run any program written in Go.