Garrett, Thanks for your follow up post. I think your criticisms are merited and I appreciate your insights into the discussed code. I think you're right to challenge the status quo, and some one like Zakas has a lot of sway over what a lot of developers do, so I think you're right in wanting to correct the code/idea. I have to say it might be splitting hairs a bit, as he was more generally promoting a fix to the current animation problems in the browser, but your point still stands.
However, I think that your original post may have gotten away from you a little bit, and I think your second post should have been your first. Your first post definitely upset me, because you were attempting to influence others' in their decision whether to engage with another developer in the JavaScript community or not. The web is an open place because of a lot of good people and when we start to let personal spats and invective infect the community as a whole, then lines of communication between people start to break down, the community starts to second guess good decisions about standards, practices, and innovation, and we are less united against a world that generally doesn't like the fact that the web is slowly, but surely, chipping away at the information asymmetry that separates the common man from the corporate fat cat. Progress isn't inevitable and only moves forward when good people work together; when that stops happening, even a little, then the good guys lose. I know that was a little preachy, so let me step off my soap box to say that I would have been just as frustrated as you were had the same thing happened to me. I don't want to make it sound like I would have done any better, but I think *we* can do better as a community. Thanks for your insights into the code, have a good one. -Nate On Sun, May 22, 2011 at 3:11 PM, Rey Bango <[email protected]> wrote: > You can review it and bring technical merits to the forum but issues > regarding censorship or your personal life are outside of the scope of > what's acceptable here. > > Rey.. > > > On Sun, May 22, 2011 at 2:16 PM, Michael Haufe (TNO) < > [email protected]> wrote: > >> So a person is not allowed to review other people's code/library/book/ >> article? Only their own? >> >> On May 21, 3:09 am, Asen Bozhilov <[email protected]> wrote: >> > "Via the JSMentors mailing list you can: >> > >> > Discuss ECMA-262 standard >> > Discuss different implementations of ECMA-262 >> > Discuss different host environments of JavaScript >> > Discuss implementation of algorithms in JavaScript >> > Discuss your library design >> > Review your code >> > Review your book on JavaScript topic >> > Review your article on JavaScript topic >> > Via the JSMentors mailing list you must not: >> > >> > Insulting other subscribers >> > Post racism >> > Spam publications" >> > >> > According the rules of JSMentors, your post is irrelevant and it's >> > contradiction of rules. >> > >> > Nicholas Zakas is free to post or NOT comments in *his* blog. This >> > topic is not related with JSMentors. >> > >> > Regards, >> > Asen >> > >> > 2011/5/21, dhtml <[email protected]>: >> > >> > >> > >> > >> > >> > >> > >> > > 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] >> > > -- > 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]
