petdance

https://github.com/petdance/beyondgrep is the repo for the site.

I am surprised to see that there is a word in Klingon for vacation: http://klingonska.org/dict/?q=vacation

Dear Mr. Stallman,

I don't think that's how open source works, but hey, can't hurt to ask.

Learn this one weird trick to match a backslash!

I'd heard that there were brutal scenes of torture in GTA V, but I had no idea.

I'd suggest that for most cases that are not source code that you stick with grep.

I put in a redirect from http://betterthangrep.com/ack-standalone to the new location, but it's temporary. I never intended for anyone to use that command line as ad hoc API, nor did I realize that people were scripting against it. :-/

So, sorry I broke it, and, I can't promise that URLs are going to stay where they are unless I explicitly say that I am promising that.

Depends on what your needs are. Do you want the coloring and grouping? Do you want Perl regular expressions? Do you want to only search source code? Do you want to be able to specify specific filetypes, like "ack foo --perl" or "ack foo --nohtml"?

git grep is neither superset nor subset of ack. Each tool has its place.

> You don't uninstall grep

Beautiful. Thank you. I am stealing that for when I discuss this in other places.

Also, take a look at http://beyondgrep.com/more-tools/. There are a dozen other tools on there as well that you might well like as much as ack and ag.

An abundance of tools is good.

It's OK to have two similar tools in your toolbox. When you need the --output option, for example, you use ack. When you want crazy speed, you use ag.

You don't have to choose one over the other. That's why I changed the name from "betterthangrep.com" to "beyondgrep.com". There's no need to have a ranking of "I use this over that."

Excellent. I've added it to the to-do list of articles to put on beyondgrep.com

https://github.com/petdance/beyondgrep/issues/12

Chances are that if there are any performance changes, it might even be a decrease in speed because of having to find .ackrc files. We haven't gone profiling 2.0 yet, but that's near the top of our list.

I'm the author of the article, and I chuckled at that myself on my final pass through the article.

The difference is that the deal-breaker in the 2nd case is that the "RTFM, dude" response shows the candidate to be 1) rude, and 2) someone who can't carry on a conversation. Asking questions to open conversations about what's on the resume isn't a trick question where the interviewer is waiting to pounce and say "A-ha! You like IE! Begone!"

A great list. I've been sending this to people with the disclaimer "half of the rules are about software development in general, so go ahead and read it anyway."

I think that makes you sound like a little kid, an amateur. You're an adult, so don't ask other people what you should wear.

Please remember that a GitHub account is the start of a portfolio, but only a start. You must have some sort of curated guide that will help the reader through the morass of stuff in your account. Otherwise, you're leaving it up to chance that the reader will find what you want her to find.

http://petdance.com/2011/08/your-github-account-is-not-your-...

If the original comments about replace were motivated by "Diagnosis and error correction" or "Improvement", I don't see it.

> Can we not be critical on the internet any more?

You can, but why? What good is served?

> I think the point everyone is trying to make here is. Should every person spend 5-10 minutes doing this?

Exactly. People tell me "Nobody needs ack, you just write wrappers around find+grep" and I say "You could, but I published it and now people don't have to."

Dictionary.app says mistake is "an action or judgment that is misguided or wrong: coming here was a mistake | she made the mistake of thinking they were important."

Perhaps you're thinking of "accident".

> There is only one case that justifies reimplementing things

Who are you to decide how she may spend her time? Why in the world do you think that she has to justify to you what projects she creates?

The problem is that being abusive and belittling to others is harmful to the open source community, especially when it revolves around someone who has gone and contributed to the community actual working code.

I'm glad you liked the article, and it seems to have struck a chord. One of the things I've found very handy is that I now have a place to point people on, say, StackOverflow when someone asks "How do I get started in open source?" I started 89starts.com as an offshoot of the article, but I haven't yet gotten it ready for prime time.

Agreed about documentation, and at the top of my to-do list for today is making final edits to another article for them on open source documentation. Should be out in a week or two I think.

I'm the author of the article, and throwing away the tickets was suggested many times by different people.

We had a pretty big discussion in #parrot about the value of this ticket set. People on the project plowed through the Trac database and closed tickets, and even with that we still hundreds that tracked all sorts of development. Many were bug reports, and many were effectively to-do items, and many were bug reports that had been resolved but still couldn't be closed for various reasons, such as needing an automated test to verify it.

It's nice to start over clean, but sometimes there's too much baby with the bathwater.

I suggest that one's time isn't so valuable that you can't spend half an hour of unnecessary discussion. (In the case of the OP, I see that we're talking about more time than that.)

You never know who you will meet again in your future, or who your interviewer knows that you will meet in your future. It's a small world.

You want to be well-remembered. Walking out goes against that goal. Anything short of direct hostility, I suggest sucking it up and going through it to the end.

Sad that there's no mention of the huge role Perl + CPAN play in their infrastructure:

* http://help.duckduckgo.com/customer/portal/articles/216392-a... * https://github.com/duckduckgo/duckduckgo/wiki/DuckDuckGoPerl * http://www.perlmonks.org/?node_id=848999

They've also been visible in sponsoring the Perl community.

This is not something to be celebrated. It's an embarrassment and it encourages the same behavior in others.

Perhaps someone with a projector that could show entertaining films against the brick walls on either side of us.

That says more about Linus that anything else I've read.