It is tricky: Japanese chat logs don't have all that much context to go on, and you have to make a judgment call as to what sort of "voice" they'd be speaking with. I gave them fairly informal young American programmer personalities but with just as much reason I could rewrite this to loko like it was two frat boys.
Disclaimer: I don't exactly go all-out for accuracy when translating to procrastinate about going to sleep.
I always enjoy (from an intellectual perspective) seeing two translations of the same thing...
When I compare your rewrite to mine, I notice that I semi-unconsciously had Matz and Keiju writing some lines as full sentences with correct English capitalization, and others as fragments starting with lowercase letters. That's often how English chatlogs look, after all. I have a Skype chatlog in my other window, talking with my product manager, that has a similar feel - I don't capitalize when I'm continuing the thought from a previous chat message.
And of course, I missed a few things you didn't - I'm not as conversant with tech-related Japanese.
It's tricky to come up with an idiomatic way to show two people discussing in Japanese an English play on words. Not to mention the Japanese "how is that spelled?" question that doesn't make sense in written English.
The one linked in the headline was the result of a professional programmer and OSS enthusiast spending probably an hour of their time doing something very difficult for the benefit of the community. The only reason they were able to spend that hour was because they had previously spent probably 10+ years studying English. Had they not spent that hour, the odds of me independently deciding to translate that email were zero. So, I would suggest upgrading that comment to "The one linked in the headline was a generous contribution to the community of the type which we should enthusiastically encourage."
Almost all professional translators strongly suggest that one translate exclusively from one's non-native language into one's native language. I think that is kind of a silly rule in the real world, but there is a reason it is so popular: idiomatically phrasing things in one's non-native language is really freaking hard. I've almost certainly produced Japanese much worse than that when paid money to do so.
More broadly, I'm reminded of a comment I heard from bilingualism debates when I was six: always remember, prior to criticizing someone for their accent, that it means they speak one language more than you do.
May I suggest that if you (by "you" I mean the parent and siblings of my comment) are going to speculate, you might consider reading the Wikipedia article before going off in all directions. It's even got sources for some of the claims (although not all).
Supposedly, perl was originally pearl. Practical Extraction and Report Language. The 'a' got dropped because Larry wanted the name to be a four-letter word.
Wow, So Ruby was almost named Coral. Imagine programming in Coral on curtails.
Incidentally, there is actually a language named Coral ( a general purpose programming language based on ALGOL-60 http://en.wikipedia.org/wiki/Coral_66 )
keiju> ruby
keiju> a jewelry name after all
matz> put it alongside kanji?
Just FYI, this refers to the simpler hiragana characters sometimes put next to kanji characters (for people who don't read kanji very well). This is also often a source of confusion for people who see the <ruby> HTML5 tag and think that it's for the Ruby language.
[Pedantic note] They're not just for people who can't read kanji well: they're also used to provide a phonetic gloss for proper names (where the pronunciation is ambiguous or unique), or in literary contexts to indicate the intended pronunciation where unorthodox kanji are used for nuance.
I might try my hand at a translation with better flow... although, remember, the original is a chat log. Chat logs read in retrospect usually don't flow as well as natural conversation!
Certainly if one is fluent, that's a perfectly reasonable desire - I'm not, but I'm sure there's a significant amount lost in that translation process.
http://pastebin.com/tHDPJsUt
It is tricky: Japanese chat logs don't have all that much context to go on, and you have to make a judgment call as to what sort of "voice" they'd be speaking with. I gave them fairly informal young American programmer personalities but with just as much reason I could rewrite this to loko like it was two frat boys.
Disclaimer: I don't exactly go all-out for accuracy when translating to procrastinate about going to sleep.