News for hackers. Stuff that matters.
Re:Porting the Go compiler from C to Go by gizmo686 on Saturday April 26, 2014 @12:55AM (#7650489)
The general way that self hosting influences language design is that the compiler is often one of the first major projects to be built using a language. This does not give it more influence then other major projects, but if your goal is to have a language designed for use case X, it is generally best to have your early projects with it be for X. Additionally, self hosting may encourage a language design that makes bootstrapping easier (such as a stricter divide between the state-1 language and the general language).
Re:Porting the Go compiler from C to Go by pohl on Saturday April 26, 2014 @10:44AM (#7651513)
I sort of had the general sense of that already. I guess I was hoping for something more specific about what language features are so useful when writing a compiler but get in the way for general problems.

The part I quoted above almost sounds like wiping sweat from one's brow after having dodged a bullet: "phew, the language is safe from influence by those gull-durn compiler-writers..."

Re:Porting the Go compiler from C to Go by steveklabnik on Saturday April 26, 2014 @02:30AM (#7650625)
To expand a bit on your last point, self-hosting helps answer the question "can I build Real Software (tm) with this language, or is it really difficult?" earlier in the lifetime of the language.