5 ms·
"We've decided to call our REST framework - wait for it - Rest."
by thathonkey 12y ago
"We've decided to call our REST framework - wait for it - Rest."
- lelf 12y agoThis thread's queue for useless bikeshedders is full, sorry.
- thathonkey 12y agoI disagree that the name for something like this is a trivial decision. Especially when considering the name for a framework which will need to be discoverable on Google to gain popularity. And even more especially when you choose to name the framework for working with a technological concept in one specific programming language the same thing (albeit different casing) as that technological concept itself. How is that not a really important decision that should be considered practically? If I want to query Google for REST vs. Rest, or even converse with people about it, you don't think that will quickly become (needlessly) confusing assuming the framework becomes popular? And if you aren't expecting the framework to become popular, does that make it OK to choose such a lazy name? But, hey, at least you got to namedrop the term "bikeshedding" along with your highly specious argument.
- andrus 12y agoGoogle "haskell rest". Done. See @sfvisser's comment: https://news.ycombinator.com/item?id=7965468 https://news.ycombinator.com/item?id=7965468
- thathonkey 12y agoI fail to see how that solves the problem for anyone other than people who already know that they're looking for a Haskell REST framework that might be called Rest.
- pstop 12y agoConsidering the key for any new user, when encountering problems when unfamiliar with the material, is to use a unique term to find answers on the web. Calling your framework after the technology is arrogant, foolish, and wholly unimaginitive.
- deleted 12y ago[deleted]