Revision as of 17:34, 11 April 2022 edit MrOllie (talk \| contribs) Extended confirmed users, Pending changes reviewers, Rollbackers 255,629 edits Restored revision 1035614251 by MrOllie (talk): Add any new comments at the bottom Tags: Twinkle Undo ← Previous edit		Revision as of 14:11, 11 November 2022 edit undo Rp (talk \| contribs) Extended confirmed users 2,953 edits the title and introduction are much more general than the rest of the content Next edit →
Line 448: Cheers.—[[User:InternetArchiveBot\|'''<span style="color:darkgrey;font-family:monospace">InternetArchiveBot</span>''']] <span style="color:green;font-family:Rockwell">([[User talk:InternetArchiveBot\|Report bug]])</span> 07:33, 7 December 2017 (UTC) == Title and scope == I feel this article suffers from a lack of definition. The title suggests that design patterns are a general notion in software development. I have only ever seen them as an practice that is specific to object-oriented software, introduced by Gamma et al.'s book. Some design patterns, such as MVC, existed prior to the book, but I've never seen the idea applied to other types of software. If it has been done, and if the term design pattern is actually applied in such cases, they are certainly the exception. We do have all kinds of established design patterns in software development that aren't tied to object orientation, such as client-server architecture, multi-tier architecture, dataflow architecture and pipelines, message passing, concurrent programming with shared memory and IPC primitives, software threads, software interrupts, etc. etc., but none of these are actually known by the name design pattern, as far as I know. The present article defines the term as if such things are included, and then goes on to discuss exclusively the specific concept introduced by Gamma et al. This is confusing and inconsistent. [[User:Rp\|Rp]] ([[User talk:Rp\|talk]]) 14:11, 11 November 2022 (UTC) Either the article should limit itself to discussing design patterns as known in object-oriented software development, and the title and introductory paragraph should be changed to reflect that; or it should at least start out by discussing them, before continuing to discuss how design patterns are applied in non-object-oriented software (which the present text doesn't even mention the existence of). Do you agree? Which approach would you prefer? [[User:Rp\|Rp]] ([[User talk:Rp\|talk]]) 14:11, 11 November 2022 (UTC)

Talk:Software design pattern: Difference between revisions