3 ms·
More colourful, yes, but I couldn't see the reason behind the names immediately. "Dry" terms that actually happen to _describe_ their behaviour are immediately
by joshsharp 17y ago
More colourful, yes, but I couldn't see the reason behind the names immediately. "Dry" terms that actually happen to _describe_ their behaviour are immediately grasped and understood.
I understand that perhaps colourful and friendly names can be fun, but I suspect you'd have a hard time getting these accepted among the people that actually use the protocol.
- setori88 17y agomaybe - but I found I could perfectly understand each pattern by relating the analogy of the fun colourful names to the behaviour of the problem. Well at least I can say it worked for me ;) I walked away from the AMPQ design specs, feeling a bit tense. Though I immediately grasped restms.org meaning. I think it is well written, describing the point accurately and in brevity. Once you clone the repo, there are more docs in there which are quite a good read - specifically the restms_developers.txt doc.
- setori88 17y agohttp://github.com/pieterh/restms/tree/master http://github.com/pieterh/restms/tree/master
- jwilliams 17y agoWhich goes into "Reverse Housecat", "Multimaster Housecat", "Wolf Call"... I can't say they are obvious at first glance. Metaphor is great for explaining things - and as a guide. Those names might make a great sidebar. I just don't see the need to rename things when it's a firmly established domain.