I also want to add a note of agreement with Asen. If the OP hasn't replied
with any JavaScript in a few days then I think the post should be deleted.

On Sat, May 21, 2011 at 6:45 AM, Nathan Sweet <[email protected]>wrote:

> I completely agree with the sentiment against the OP here. If someone links
> to a blog post here, even if it's their own, to talk about JavaScript I'm
> fine with it; plus I might want to subscribe to their blog. I would have
> been much more interested in what the OP, Garrett,  had to say if he (I'm
> assuming you're a man) had talked about the issue he had tried to correct.
> Otherwise it feels like sour grapes to me -- be brave and tell us about your
> issue with his blog.
>
> On a side note, Zakas is the lead front-end guy for one of the Alexa 5
> websites, and, in particular, one of the 5 that displays a lot of
> information, I'm sure that the amount of emails he receives in a day would
> boggle most of our minds (at least my mind), even by dev standards. I'm sure
> he's insanely busy, and not posting your comment on his own blog is
> completely warranted. I have to admit, it would have been nice if he had
> dropped you a quick line explaining why. Also accusing Zakas of career
> building is a little funny since he's probably one of the few people in the
> world making over 200k to mess around with JavaScript.
>
> On Sat, May 21, 2011 at 4:54 AM, keif <[email protected]> wrote:
>
>> I'd suggest if you feel his blog post is incorrect, you write a blog
>> post that corrects it (and explain why what you have written is "more
>> correct"
>>
>> -keif
>>
>> On May 21, 2:27 am, dhtml <[email protected]> wrote:
>> > Hey all,
>> >
>> > Just wanted to throw out a friendly bit of advice to the newbies.
>> >
>> > Blog author and JSMentor "Nicholas Zakas" censors his blog comments
>> > and doesn't take any feedback or criticism.
>> >
>> > I sometimes try and correct wrong advice when I see it. But it sure is
>> > frustrating when the author hides/disproves comments that I took time
>> > to write out.
>> >
>> > I can understand promoting one's career but the author's act of
>> > censoring a purely technical comments should give a clue that maybe
>> > there's something something wrong with what was written (or why would
>> > he have to censor it, when he could just rebut).
>> >
>> > If it was an accident, then I apologize, however, I don't even bother
>> > emailing him anymore because it never worked out in the past. This has
>> > happened before and went through the emails/messages on Twitter but
>> > didn't get responses that way.
>> >
>> > Just a notice for the community here about Zakas' blog.
>> >
>> > Garrett
>>
>> --
>> To view archived discussions from the original JSMentors Mailman list:
>> http://www.mail-archive.com/[email protected]/
>>
>> To search via a non-Google archive, visit here:
>> http://www.mail-archive.com/[email protected]/
>>
>> To unsubscribe from this group, send email to
>> [email protected]
>>
>
>

-- 
To view archived discussions from the original JSMentors Mailman list: 
http://www.mail-archive.com/[email protected]/

To search via a non-Google archive, visit here: 
http://www.mail-archive.com/[email protected]/

To unsubscribe from this group, send email to
[email protected]

Reply via email to