News for hackers. Stuff that matters.
Re:Software Design Patterns Are Not Goals, They Are Tools by maffydub on Thursday May 19, 2016 @11:17AM (#11730853)
Sure, so some documentation isn't great (and, by having lots of documentation, you might be a bit disappointed at how simple it ends up being).

...but going back to my original point, isn't it more valuable to have a common vocabulary, meaning that I can say "visitor" rather than "pass in a function and descend a graph calling it on each node"?

Re:Software Design Patterns Are Not Goals, They Are Tools by emodendroket on Thursday May 19, 2016 @12:54PM (#11731583)
Well, in my opinion, no, because the fancy terminology obscures the simple idea.

Also, the naming of the pattern, along with implementation, may push people to copy a design that would be the best way to do it in C++ or Java ca. 2000 but unnatural in whatever they're working in.

Re:Software Design Patterns Are Not Goals, They Are Tools by gnaritas on Thursday May 19, 2016 @03:28PM (#11733032)
It's a simple word, visitor; that's not fancy terminology. Giving things names is not fancy, it's practical and it aids in communicating with other people who do the same thing. You're basically objecting to the fact that people like to give names to their idioms so they communicate better.
Re:Software Design Patterns Are Not Goals, They Are Tools by emodendroket on Thursday May 19, 2016 @04:39PM (#11733618)
No, I'm objecting to the use of terms which I feel make communication worse, rather than better. You're free to disagree.