Please consider renaming your binary to not match a shell builtin

[brandonbloom]

Hello,

A few weeks ago, I was playing with https://github.com/honeycombio/beeline-go which makes use of your project in some capacity. Today, I was very confused when a ./configure script was hanging. I was even more confused because initial inspection showed the name of the program that it was hanging on to be echo.

Of course:

$ which echo
echo: shell built-in command

But after some head scratching, I realized:

$ /usr/bin/which echo
/my/go/path/bin/echo

It's pretty bad form to name your binary the same as such a common shell builtin. It leads to some pretty stunningly confusing behavior, even for somebody who never directly uses your project.

Please consider renaming it to echod or echo-server or something of that nature to avoid this time bomb exploding in some other unfortunate dev's face in the future.

Cheers,
Brandon

[vishr]

@brandonbloom Echo is a framework/library and it doesn't release any kind of binary with that name. Whoever is creating a binary should not create it with that name.

[brandonbloom]

You're right. My apologies. Problem is over here: https://github.com/honeycombio/beeline-go/blob/9adb5c235b865f43dd103e11ceb5d45ceb05c4e1/examples/echo/main.go