Go compiler moving from C to Go

[Paulo Pinto]

On Thursday, 19 December 2013 at 11:31:10 UTC, Russel Winder
wrote:
> On Thu, 2013-12-19 at 12:23 +0100, bearophile wrote:
> […]
>> Moving their Go compiler from C to Go seems a good idea, for 
>> the reasons they have listed. But moving all their other tools 
>> from C to Go seems a little too much.
>
> I think not. The whole point of Go is to replace C, so it is 
> right to
> replace all use of C with Go for the Go toolchain.

Fully agree. Only when the public at large starts to see GC
enabled languages used in contexts where C is known for, are they
convinced that C can be replaced.

What I advocate since I got in touch with Oberon.

Having the full toolchain done in Go already takes out of the
equation the typical "my compiler compiles yours" statement.


--
Paulo