Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Unicorn

getunicorn.io

Post reply on HN
Print view View original

21–30 of 68 posts

Re: Unicorn

#21

Post by monsur »

Naming aside, I think there is some value in a fluent, cross-language methodology for making HTTP requests. While each library adheres to the conventions of its specific language, the overall pattern for making requests looks the same across languages. If you are someone working with APIs in different languages, there is value in having this consistency.

Re: Unicorn

#22

Post by cheald »

nijiko wrote: post #7
tptacek wrote: post #2

Extremely confusing name, given that Unicorn happens to be the name of both an extremely popular Ruby web server and its extremely popular Python port.

My little cousin decided it and I didn't have the heart to break his...

I sympathize, but at least use a variant on it. Picking that name and logo for an HTTP request library with Ruby and Python bindings is extremely bad form given that there's an existing HTTP server project that uses that name and is associated with that logo.

Re: Unicorn

#24

Post by dljsjr »

I'm going to operate completely under the assumption that the library authors didn't choose the Unicorn name with intentional malice, and that their motivations were entirely benevolent. It looks like a nice enough library, congrats on all of your hard work.

That said, this name is going to foster a lot of ill will in the community, for all of the reasons already mentioned:

https://news.ycombinator.com/item?id=5597411

https://news.ycombinator.com/item?id=5597402

https://news.ycombinator.com/item?id=5597455

Additionally, as has been mentioned, the GitHub Angry Unicorn, whether permission was given or not, is most likely related to the fact that GitHub uses the Unicorn Rack server and are proponents of the software. In addition, the Ruby port of this library presents itself as "unicorn-rest", which could very easily be interpreted as either disingenuous or as a form of "coat-tail riding" off the name/notoriety of the existing Unicorn.

Re: Unicorn

#26

Post by eurleif »

nijiko wrote: post #7
tptacek wrote: post #2

Extremely confusing name, given that Unicorn happens to be the name of both an extremely popular Ruby web server and its extremely popular Python port.

My little cousin decided it and I didn't have the heart to break his...

How about changing it to "Unicrest", as a play on unicorn/request?

Re: Unicorn

#27

Post by nijiko »

cheald wrote: post #22
nijiko wrote: post #7

Earlier quoted context omitted.

My little cousin decided it and I didn't have the heart to break his...

I sympathize, but at least use a variant on it. Picking that name and logo for an HTTP request library with Ruby and Python bindings is extremely bad form given that there's an existing HTTP server project that uses that name and is associated with that logo.

Yes, I think I will be giving him some bad news today unfortunately.
Post reply on HN