petdance

No matter what you do, at least one person will be unhappy about it.

> I have tried to use budget surplus to reward open source projects we use.

"We've never heard of that happening, so no."

What does "dead" mean?

I suggest that there are no meaningful conclusions to be gleaned from the TIOBE rankings.

Can you dedicate employee time to help on the projects?

> It's too bad Raku didn't have a different name from the start.

We thought that it would take a year or two, not decades.

Also, the intent was to have a Perl 5 compatibility mode.

The reference to "Programming Perl" was no doubt helped along by Perl developer Jesse Sheidlower who worked at the OED in the early 2000s. From his Wikipedia page: "Although not a computer programmer by training, Sheidlower introduced Perl to the North American offices of Oxford University Press and developed tools for data manipulation when no programmers were available. He is also one of the core developers of Catalyst, a popular Perl web development framework."

> I use almost none of its more esoteric features

Which features do you see as esoteric?

What makes ugrep better for your use cases?

That still might run afoul of locked down networks like I've seen at banks. Users couldn't install any binaries at all, but with something like ack it's just cut & paste some text into a text file. ack can literally be a select-all, Ctrl-C, switch windows, "cat > ack", Ctrl-V.

What do you love about ugrep?

"grep | head" doesn't limit the length of output lines, but "grep | cut" would.

However, ack and ripgrep's default unpiped output is grouped by file, and if you pipe the output, it doesn't do the grouped output.

The idea of "supposed to be used" is also different for ack than it is for grep. ack is specifically less of a general-use tool than grep. It's meant for searching source code. This is also why I have never said that ack is a replacement for grep.