Closed sleexyz closed 6 years ago
Rely
It has the "Re" naming convention of React and Redux. It implies safety, as it is reliable.
I think something that implies that it's for APIs would be good. I think servant
is a good name in that regard. You could also even reference servant
with a name with similar etymology, such as "Waiter" (obviously a bad name, but just an example).
@MatteoVH I think we're better off targeting the JS community. IDK how well known servant is, but even if they know it, people might be scared off if it's inspired by ~ Haskell ~.
Some other ideas that being with ''Re":
Rebar -- It's a strong & safe support beam. Build your app on a stable foundation. Ready -- The api is always ready(?) Rebus -- A good crossword reference and an Originate inside joke
~Barista~
(Servant for coffee) not available on NPM
What about something bridge related? What are your thoughts on the current branding of "API bridging"? Is there a better way to convey what this system does?
Here is my brain dump, sorted only in order of NPM availability, otherwise order is random. some of them are crappy, some of them are good.
The h1
's are all available on NPM. The h2
's are taken, but probably disputable. The h3
's are active npm projects. The h4
's are just snippets of ideas.
Resonate is also available
We'll want to pick a name that will
Also it should be available on NPM.