I have complained about how go projects add a 'go' prefix or suffix as a badge for brand recognition. I suppose in the object oriented world of namspacing it's almost a requirement. But since I fundamentally disagree that naming an executable by it's implementation language that would be weird:
- cppbind or cbind when it's currently named bind
- c#outlook and not outlook
I think I made my point.
I've been working on a project call goose. I started the project a few months ago and only realized, last night, that 'go' was the prefix. (at least it was not go-oose). In this project I've included tcl, lua and lisp as interpreted languages and the whole thing is written in go. So does that mean I should change the name to something like: