Eh honestly, I prefer the naming of things "what they are" as opposed to these open source names. Sometimes I wonder if ruby programmers aren't eating enough. Building an API might mean you use Cucumber, and Grape.
The problem with naming things "what they are" is that the scope of the project can change over the years, so that the name selected 5 years ago doesn't appropriately reflect what the project does now.
