Hahahaha

Makes you realize that any possible name for a REST framework for Go is inherently an oxymoron...

Nobody thought of Hest? I admit it does sound kind of silly though, but it's got the 'H' at least, and it doesn't sound like Rest.

You could have named it Shwing, though that name is a bit exclusionary.

I'm more often annoyed by projects named after mythological creatures, vegetables or puns. They're fun for a while, but when I import something into a project, it helps if it's at least a little bit self-documenting – `import Rest` rather than `import Bazooka`, say.

There's a little bit of that in Haskell right now. It's kind of OK with, say, `profunctors` which probably has everything anyone could ever imagine about profunctors in Haskell. Furthermore, as a mathematical concept there is not a lot of possible variability in that library.

Similarly, `lens` right now has pretty much everything under the sun about lenses, though some prefer the simpler lens packages like `lens-family`.

I kind of feel less confident about the choice around `rest` since there are many interpretations and implementation choices which may lead to a desire for competition here. But I'll reserve actual judgement until I use it. I wouldn't at all mind a comprehensive, provably correct webmachine-like implementation of REST called `rest`.