"Some people ARE making personal attacks against me."

Hmmmm ... I wonder why?

• "Yes, but if it was up to me, I'd eliminate sleep and make Perl smart enough to know when a loop does nothing but waste time so it will work as sleep and waste no resources."
• "I must of skipped or read that last sentence too quickly, but they should clarify what they mean by recognized."
• "Not that you're solution is worse than my proposed one, but I was suprised to learn that mine didn't work."
• "I'm considering getting help with a script that I'm working on ... Mainly, I'd like to work with a company that would pay me as I collaborate with them. In return, they would get a piece of the action when the script is finished."
• "Read the comments. Don't ask me to explain what the code does. I know what it used to do before I chiseled away at it in a failed attempt to isolate the bug"
• "But worse of all, I misread the documentation."
• "I'm barely a Perl programmer"
• "I don't intend to be a full time troll, and I don't take food from strangers."
• "The W3 validator is often wrong and not always helpful in finding problems"
• "As for flaming at newbies, I just gave someone a -- yesterday (yes, even I vote occationally) for being too hard on someone for asking a question without doing more research, but I don't know if the questioner was a newbie."
• "I continuously insult people???" (um, yes ... you do)
• "My posts have kept me busy longer than 60 minutes, but they and some of my responces have taught people something ..." (that you don't heed the advice given to you?)
• "There is a new O'Reilly book out called Spidering Hacks."
• "I guess I should start by saying that I'm not all that satisfied with any of the three popular computer books that I've bought. Learning Perl is one of those three."
• "Ahh.... I see Where do I post X now! I thought I'd seen it before. Those section descriptions should be under the section names when you go to the section. (Yes, I know that goes in PerlMonks Discussion.)"
• "I haven't even opened the book since I started this thread."
• "If the names of the sections here were designed more for usability than cuteness, I probably would have been able to find a more appropriate section."
• "I want to expose the fraudulent business practices of O'Reilly as well as help consumers."
• "I haven't even opened the book since I started this thread."
• ":) <--- proof of politeness Hummmmm <--- proof of meditation"
• "I don't know of another message board with a significant number of full length scripts."
• "Yeah, the server load issue (and security) is what's making me think twice about creating the web app myself. I don't think it would be a problem though."
• "I guess I have very specialized needs and I expect to have to customize the modules."
• "And I don't care about votes. I'm considering adding a signature that asks for downvotes."
• "It might be shareware, but not freeware and not open source."
• "I don't know nearly as much as you, but I could write a Perl program that does just about anything that any commercial software does."
• "And I prefer short, off comment posts over longer, repetitive criticism that's no doubt posted just to get ++. I give most of you a spiritual --, since I rarely vote. By the way, anyone know who holds the record for the worst # of posts/level ratio, or who has had the most total downvotes?"
• "I'd like to claim the title of worst monk"
• "Hmmm... I'm not bad enough to catch up to sickboy by being myself. I'll have to look for a different record."
• "As for reaping the node (and why can't everyone just say deleting the post?)"
• "No. I also come here to 'bitch and argue about everything that goes on with the site.'"
• "If I used a tiny subroutine for that ... Either way, it would take about as much code and be clearer if I duplicate the specific cut routine I need wherever I need it."
• "Wasser came from my HS math teacher, Mr. Wasserman, and I might have spliced it with "democrats" for the end...or maybe I thought up "crats" on my own. It just sounds right. I'm still waiting for the name to catch on. Please consider naming your baby Wassercrats."
• "Anyway, thanks for not telling me to use a module!"
• "I interpreted the third sentence to mean the opposite of what it meant."
• "...Yes, I know I left out some information."
• "Go eat an american cheese sandwich. That will bring you around."
• "Your argument sounds very philosophical. I hate philosophy. Applying a given set of beliefs to whatever problem comes your way simplifies things, but I prefer custom made problem solving."
• "Maybe there is too strong a bond between O'Reilly and Perl. I'll probably spread this information around to see how other groups respond."
• "That's how opinions work."
• "I will be taking whatever action I deem reasonable to hurt O'Reilly. I'm not limiting it to not buying their books."
• "I'm a busy monk."
• "Am I the only one who thinks it's dumb for there to be no built-in way to clear only user defined variables ..."
• "I don't like the limitations of scoping my variables. Aren't there pleantly of lower level language that don't even offer that feature? That never bothered me. It seems like it would just slow me down. It's too late for that now anyway."
• "I don't have all my variables memorized, and I'm not sure which ones need to be reset for my new implementation ..."
• "I might start coding the "right" way for future projects after I read up more and convince myself that it's better, but I have a marketable product as it is. It's essentially complete and I could deal with whatever issues come up ..."
• "Sorry, I don't remember the special ID linking rules here, and there's no reminder in site."
• "I decided to use my method ... because according to Programming Perl, 'Use of reset is vaguely deprecated.' If it won't be in Perl 6, I'm not using it." (what? Perl 6 or your "marketable" code?)
• "The voting system is a joke."
• "Proof that there are others like you. No reflection on me."
• "Sorry, I don't feel like reading all that ..."
• "If you can't determine that my script is broken, and if you don't know of a better way to accomplish what I want to accomplish, and if it looks like my script will be useful, then there is nothing for you to do except to answer my specific question and thank me for building a debugging and logging tool that every single Perl programmer would have a use for."
• "There is no fee yet, and it runs on my home computer only."

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.