The Blog of Matthew Elder

I have been incubating an idea in my mind for awhile now on a HTTP library for haskell. Please don’t typecast my library — seriously this is not YAHWS (Yet Another Haskell Web Server)! My goals are unique and my path is righteous. Trouble is, I need a name. Grep below if you will and lets figure this thing out.

Goals

Be ever vigilant!

• Simplicity and Composability
• Stability and Mainstream Browser Compatibility
• Scalability

Anti-Goals

These will be slashed without mercy.

• Optimization
• Efficiency
• Configurability

So what should I name it?

I want the name to reflect the Goals of the project. So I have the following words so far which could be the name, a part of the name, or sound like the name. I have downplayed the scalability theme because it is so buzzy right now. I really want to emphasize stability and compatibility — to be considered in the leagues with Apache yet be something completely different. Here are the words I have looked up:

• Congruency
• Ambassador
• Emissary
• Elite
• Steadfast
• Constancy
• Hydrogen (the lightest stable element)
• Ninja (masters the art of HTTP-Fu and REST style)
• Cardinal: serving as an essential component; “a cardinal rule”; “the central cause of the problem”; “an example that was fundamental to the argument”; “computers are fundamental to modern industrial structure”

These are just some ideas but I am heavily leaning towards emissary or cardinal. Any comments are welcome! Also, feel free to slash and trash my goals.