I agree. I'm superstitious about origins. When something spontaneously happens at location X it's good to let it continue to evolve there. I say we stay where the party started. We can post occasionally and nobody who's uninterested need look at it. I also confess to tasting sweet irony in the idea of turning HN to more productive use. I feel like I've finally got my enemy in a corner. (The internet has never stopped me from working, but man has it stopped me from learning. But I digress.)
There's a case to be made for the other Strang, but again - origins are magic, so unless there's a compelling negative I say we stick with tptacek's original inspiration.
I think old threads get locked (can't post new comments) relatively quickly on HN which would make it tough, it would involve making new posts and expecting everyone to find the new one. (Feel free to correct me on the locking thing)
Once in a blue moon I go back and find hanging replies to my comments, so I'm pretty sure these things stay alive for weeks, which is as long as we'd need them to.
One of my favourites is Hiroyuki Kojima's "Manga Guide to Calculus" (http://nostarch.com/mg_calculus.htm). It probably can't get much more informal and it's actually quite entertaining.
It somehow manages a decent balance of being fun without slipping into being trivial.
While we can complain and fuss about incidents like this one, I doubt there's much to gain. I don't expect there'll be a significant change in public opinion till there is a sufficient number of positive stories to counterbalance the negativity.
Less than a decade ago, when most people thought about "China", the first thought that popped into their heads was probably "cheap counterfeit goods". It's clear that things have changed since then.
Until we have a balance of positive stories, I fear we're stuck with this. Time to get moving and add to the positive stories about Nigerians.
I remember the Haskell community actually sat down and had a community discussion about laying down design guidelines for the entire Haskell ecosystem (all packages should use so and so a color scheme, this is our logo, this is our font, etc.). I find Haskell sites almost always aesthetically pleasing, and it was probably due to conscious decision by the community to establish design standards.
I think OSS in general could benefit from giving a designer such broad-brush authority over an entire ecosystem.
I actually do programming in Scala and I'd have to disagree. While there's the freedom to build a "type castle", you don't have to. For the most part Scala gets things right.
When you do need/want to get fancy with types, you get some of the best tools out there to do it.