3 ms·

This is very good, though this thread is a bit old and deep. Your italicized part ("Again, I think this can be attributed to you taking a more abstract approac

This is very good, though this thread is a bit old and deep. Your italicized part ("Again, I think this can be attributed to you taking a more abstract approach to what you are saying, but choosing to use concrete names, such as Perl, and doing so in the comments of an article about a new Perl release.") made me laugh :) You are possibly right, though I was just making an off-hand remark and only just clarified when prompted explicitly. I think the 90 words / 4 lines I wrote originally were fine, and if someone asks for clarification no reason not to include it. In general I don't think an article on a new version of Perl is a bad place for such thoughts. I like your comments, especially, on domain specific languages, though as mentioned the thread is a bit old and deep to continue here. I couldn't find an email but if you reply with one I'm happy to discuss. Your tenhundredwordsofscience is a really good example of how it gets awkward not to use specialist vocabulary. I like your analogy with chemists, physicists, lawyers, engineers, and architects. The former two especially use specialist symbols that are impenetrable to total laypersons. anyway if you have an email I'll respond to your good points.

kbenson 12y ago
I updated my about with a slightly encoded version of my email, if you want to continue.
- logicallee 12y ago
  Hi, tried to email you. You'd written "k e n t r a k # google's mail" but kentrak@google.com (the only way I could think of interpreting that) bounced. (I don't mind including it here as Google's server says that mailbox doesn't exist). Kind of ironic given our conversation :-) Could you bit a bit more explicit ;-)
  - kbenson 12y ago
    @google.com is for people who work at google, @gmail.com is what I meant, as "google's email service". I agree, it wasn't very clear, but I don't particularly want harvesters having an easy time.
    - logicallee 12y ago
      wow, how bizarre. I could have sworn I sent it to a gmail address, I thought that it was obvious you meant gmail, and even after your reply I thought "well yeah of course I sent it to gmail, that part was obvoius" and thought I must have just mistyped it here, but sent correctly in my sent mail. It's weird that I actually did send it to @google. The thing is that I must have just carefully been doing character transliteration, changing your #, removing spaces, etc, to deobfuscate and @google didn't end up looking wrong enough! Sorry. Sent to the correct (and obvious) email. BTW the fact this happened is just too good, given the subject! I forgot to dereference a literal in a string. :) Anyway I've re-sent the email.

kbenson 12y ago

I updated my about with a slightly encoded version of my email, if you want to continue.

logicallee 12y ago
Hi, tried to email you. You'd written "k e n t r a k # google's mail" but kentrak@google.com (the only way I could think of interpreting that) bounced. (I don't mind including it here as Google's server says that mailbox doesn't exist). Kind of ironic given our conversation :-) Could you bit a bit more explicit ;-)
- kbenson 12y ago
  @google.com is for people who work at google, @gmail.com is what I meant, as "google's email service". I agree, it wasn't very clear, but I don't particularly want harvesters having an easy time.
  - logicallee 12y ago
    wow, how bizarre. I could have sworn I sent it to a gmail address, I thought that it was obvious you meant gmail, and even after your reply I thought "well yeah of course I sent it to gmail, that part was obvoius" and thought I must have just mistyped it here, but sent correctly in my sent mail. It's weird that I actually did send it to @google. The thing is that I must have just carefully been doing character transliteration, changing your #, removing spaces, etc, to deobfuscate and @google didn't end up looking wrong enough! Sorry. Sent to the correct (and obvious) email. BTW the fact this happened is just too good, given the subject! I forgot to dereference a literal in a string. :) Anyway I've re-sent the email.