Ben Lynn, a Google engineer, writes about programming languages, data structures, Unicode, and shell scripts.
Commenters note his affection for many languages, link his post arguing UTF-16 is bad, and cite his crit-bit tree and Android posts.
Judging by his blog (http://benlynn.blogspot.com/) it looks like he has considerable affection for many languages beyond C. And I think you may have misinterpreted his comparison with Fortran: rather than showing how handily C beats Fortran (fish in a barrel), he seems to be saying that even with some C99 improvements, there still are places where Fortran has the advantage (refreshingly heretical). It's definitely not a piece for beginners, but I think it may be a more balanced picture than you present.
Appears to be mostly good information, though I'm surprised he paints UTF-16 in such a positive light ("optimized for languages residing in the 2 byte character range."). UTF-16 should be considered harmful:
http://benlynn.blogspot.com/2011/02/utf-8-good-utf-16-bad.html
http://stackoverflow.com/questions/1049947/should-utf-16-be-considered-harmful/1855375#1855375
I think this is a cool project, but surely needs more of a preamble? Like what are crit-bit trees? [1,2,3,4]
[1] http://benlynn.blogspot.com/2007/04/trees-hash-tables-and-tries_11.html
[2] http://en.wikipedia.org/wiki/Radix_tree
[3] http://cr.yp.to/critbit.html
[4] http://www.imperialviolet.org/binary/critbit.pdf
And the obligatory "Without Eclipse":
http://benlynn.blogspot.com/2009/01/developing-android-without-eclipse-or.html
http://www.anddev.org/novice-tutorials-f8/developing-android-apps-without-eclipse-t13912.html
The author works for Google, and his most recent blog post is actually about the Go language:
http://benlynn.blogspot.com/2009/11/it-go-time_6644.html