Hacker News new | threads | past | comments | ask | show | jobs | submit DanielBMarkham (43801) | logout

Why do people chose names for tools or libraries starting with "Yet Another...". I know naming can be hard, but anything can be better.

Want a name, here are a few: Camel, Druid, Beetle, Quetzalcoatl, Omaha. You can even use a random website name generator, or character name generator to get names that don't mean anything but are readable.

I much prefer naming technologies with unique names, and acronyms are probably the best way of achieving that. It's much easier to discuss and google than using a common word.

Camel is an especially bad example, as there is already an Apache project by the same name, plus the Caml dialect of ML (of which OCaml is a much more popular descendant). Not to mention the animal, the brand of cigarettes, and the prog rock band...

CAMEL is also a protocol to let enhanced mobile services use SS7 interfaces as specified by 3GPP for Intelligent Networks (IN)

Eh, I prefer naming technologies with a mix of both a unique name and it's purpose, otherwise it all gets too crowded.

Personaly I find...

Camel = Bad

Camel Reverse Proxy = Better

But again it's personal taste

CaRP sounds a little fishy though.

Better than the Camel Reverse Auto Proxy!

Not sure if you are being sarcastic, but Camel and Druid are already taken: Apache Camel & Apache Druid :)

I used them as examples.

Personnally I like it.

It implies they know that the space is already pretty crowded. Yet, they find there was place for yet another because they bring an angle or feature that is worthy of existing.

Camel would imply it’s written in Perl.

In open source I assume anyone calling something “yet another X” is acknowledging that other X type programs exist, but don’t fit the needs or scratch the itch for the creator. You can take it or leave it.

I suspect in this case “yet another” was picked at least in part to make a cultural reference for humour value. Bung yarp into Google or similar and you'll get many images from Hot Fuzz.

Especially if the name spelled backwards is “PRAY” ;).

I think you wanted to use the adjective reverse.

There's even a website for it - https://www.thisworddoesnotexist.com/

It’s geek ironic, but yeah the trend is kinda thick. It’ll be interesting to see how easy it is compared to other reserve proxies. I am def not a dev op guy but there’s a few things where it feels like I am learning another coding language just to do something that seems like it would be easy to document and get done sooner but, you end up needing a certificate to learn how to use an image buck for instance.


yarp is much more googleable than "camel"

Remember that most of MS products have hyper descriptive and generic names.

Their SQL server is called SQL Server. Their MVC framework is called MVC.

Meanwhile their team messenger has changed names like 12 times.

And anything dev-y gets swallowed into the Azure brand.

YARP is a huge step up. If they'd followed their typical approach, this would be either "Reverse Proxy" or "Azure RequestFlows"

Yet I personally prefer both "Reverse Proxy" and "Azure RequestFlows" to YARP.

I guess it's personal taste.

Until you work with multiple platforms and you're trying to figure out if we're talking about Microsoft's reverse proxy, or and F5 somewhere, or maybe that Nginx.

It's an old tradition, dating back (at least) to yacc.

Yet Another {Foo}


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact