Bram Cohen: Comments on Go

On topic: I find it funny that someone of Bram Cohens' standing would miss the point of fast compilation.<p>If you're working in plenty of other languages compile time does not go up linear with code size, but much faster.<p>When you start out it zips right along, but as soon as you cross that 10,000 line mark the first bits of irritation set it in, and not much later than that you can go and get a cup of coffee and drink it while your code rebuilds. For really large projects an hour isn't much at all!<p>Fast compile time = I won't lose my train of thought while waiting for the compiler to finish. It's a 'tool' thing, and I think that such details make for much better tools.

I really wish people wouldn't include the name of the author in the title.<p>I think this should be banned and cleaned up by the moderators in the same way using numbers in the titles of submissions is, and the same way that moderators removed "Ohhhh snapppp" from the Go post about the author of Go!<p>Invariably, Paul Bucheit, Paul Graham, Bram Cohen, Guido van Rossum, Joel Spolsky, and other famous hackers get voted to the very top of the list. If these guys are great writers and great thinkers, then their articles will speak for themselves, and they usually do (but not always).<p>For the few people who have never heard of Bram Cohen or Joe Hewitt (currently 1 and 2 on HN), then their names are just noise. For those who have heard of them, it just biases their judgment in both clicking and voting.<p>In this case, Bram's blog even carries his name... so why make his name the first two words in the headline? Do we really need to make to use this kind of name-dropping to highlight content? That sounds like the opposite of content democratization to me.