编程与软件工程perl.plover.com
《设计模式》并非模式（2002）
“Design Patterns” Aren't (2002)
2011 — 2021，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
这是 Mark Dominus（Perl 社区知名作者）2002 年的一场演讲幻灯片，质疑 GoF《设计模式》一书：它对 Christopher Alexander 建筑学思想的借鉴其实偏离了原意，Alexander 追求的是让使用者参与设计决策、形成真正的“模式语言”，而 GoF 只是把常见 OOP 代码套路编目成册。演讲还以 Iterator 模式为例，指出许多“模式”不过是语言表达能力不足的补丁。
为什么经久不衰：它对“设计模式”的批判视角在近二十年间反复引发讨论，提醒读者把模式当作共享词汇而非教条，至今仍是软件设计争论的经典参照。
HN 评论精选
设计模式的价值在于共享词汇，而非刻意套用
我的理解是，设计模式只是一种共享词汇，而不是值得追求去使用的东西——除非是当你意识到已有的某个“词”能简洁地描述你那堆乱糟糟的句子时，用它来替代。
lfowles查看英文原文
My impression was that design patterns are just shared vocabulary, not something to aspire to use (other than realizing there was an existing "word" that would succinctly describe your jumbled spaghetti sentence and using that instead). Edit: I've been wanting to read A Pattern Language for a while, but this snippet from Amazon made me chuckle. If I didn't know better, I would have given it a 50/50 shot of being from APL or GoF! >The elements of this language are entities called patterns. Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice.
模式是沟通工具，也帮助理解框架和代码评审标准
我一直把设计模式主要看作向后来接手的程序员传达你正在做什么的方式。比如 MVC：即使你不熟悉某语言或框架，读按此模式构建的代码时也知道各部分该找什么。作者说得对，常见问题应该用库来解决；但这些库往往正是在实现模式的通用部分，理解模式能帮你更快用好它们。
shubb查看英文原文
I've always seen design patterns principally as a way of communicating what you are doing to other programmers who come later. For instance, MVC is a very popular design pattern. When you read code built according this pattern, even if you are not familiar with the language or framework, you know what kind of thing to expect to find in different parts of the program. They can also be useful in a context where not everyone in the team is used to writing code in a disciplined way - like coding standards and ideas like YAGNI, they can give an objective set of standards at code review. Adopting a few of these strategies in a code base provides a standard people can refer to about what goes where. Where the question is whether James should have stuck this database code in the class that renders the web page, being able to point to a well documented strategy and say "that code doesn't go there because we're doing that" can be better than excessive conflict. The author is right that if you have a common problem, you should probably be solving it with a library (preferably someone else's). However, often these libraries and frameworks are implementing the generic bits of the design pattern, and understanding that pattern gives you a shortcut to knowing how to use them well.
模式既是交流语言，也暴露了语言本身的不足
我听过最好的解释是：设计模式不是写代码时亦步亦趋的模板，而是谈论代码的公共语言。第二好的解释是：模式往往是语言缺陷的信号，比如迭代器模式、访问者模式，或用 async/yield 取代显式状态机。
captainmuon查看英文原文
The best explanation I heard of design patterns is, that they are not a template to slavishly follow when producing code, but a common language to talk about code. So you should be able to go and identify, look, this is an iterator, this is a command pattern, this is a monad, and you have a clear and concise way to reason about your code and talk to other people. The second best explanation is that patterns are often a sign of shortcomings in the language. OP gives the example of iterators. Another example is the visitor pattern. Or async/yield as a replacement for explicit state machines. A thing I'd really like to see in a language would be language level support for the command pattern (being able to capture arbitrary blocks of code, lift the execution to an object, and undo/redo it). Or to be able to include the state of an object in the type system - not like Rust does it with typestates, but to be able to say `Child` is a `Person` where `age < 18`, and if the compiler can't prove that the condition always holds, then it will force you to write the precondition checks or check it at runtime.
为 GoF 辩护：它比演讲承认的更接近 Alexander 的思想
我喜欢他关于 Alexander 追求设计决策下放的观点，但从《建筑的永恒之道》来看，Alexander 还在说：现代建筑师在解决错误的问题；小尺度与大尺度的模式会相互增强或干扰；真正掌握设计后可以抛开模式语言，让方案有机生长。GoF 在第 3 点上其实比演讲者承认的更接近 Alexander——书中明确说其实现不是唯一方式。
phlakaton查看英文原文
I like his point about Alexander going after delegation of design decisions, though I don't necessarily think that's the only point he was driving at. From "The Timeless Way of Building" I got that he's also driving at this: 1. Modern (not necessarily just modernist) architects are generally terrible at achieving what Alexander refers to as "living space" because they're solving for the wrong things. 2. Small-scale patterns and large-scale patterns can constructively or destructively interfere with each other from urban planning right down to construction details of a room. 3. If you've really mastered design, you can leave behind the pattern language and cookie-cutter implementations: your solutions will organically develop with these large-scale/small-scale synergies. I'd suggest that GoF is a little closer to Alexander in these respects than the presenter gives credit for, particularly for point #3. The book studiously makes the point that its implementation of these patterns is not meant to be the only way to implement them. It also makes no attempt to be an exhaustive catalog. The fact that some of these patterns have standard and different implementations in other languages (e.g. iterator method hooks and generators in Python) doesn't necessarily mean that the pattern itself is useless outside of its OOP niche. I'm glad WikiWikiWeb is back up so we can debate all of this on the one true forum for debating design patterns. :-)
历次讨论
同类还值得读
开源应用架构
The Architecture of Open Source Applications
《开源软件架构》（AOSA）是一本在线免费书，邀请知名开源项目的作者亲自剖析其内部设计，涵盖 SQLAlchemy、LLVM、Audacity、Apache、Bash 等系统。
编程与软件工程上首页 9 次 · 2011–2024aosabook.org编辑精选编程语言简史：简短、不完整且多半错误
A Brief, Incomplete, and Mostly Wrong History of Programming Languages
一篇以戏谑、故意不准确的方式回顾编程语言史的博客文章，用夸张轶事和讽刺定义串起 Lisp、C、C++、Java、JavaScript、PHP 等语言。
编程与软件工程上首页 8 次 · 2009–2021james-iry.blogspot.comSQLite 是如何测试的
How SQLite is tested
SQLite 官方文档页，系统介绍 SQLite 的测试体系：多种测试方法（TCL 测试、模糊测试、回归测试、静态分析等）和海量测试用例，展示了这个小型开源项目如何靠极致测试获得…
编程与软件工程上首页 8 次 · 2009–2025sqlite.org编辑精选高级编程语言（2009）
Advanced programming languages (2009)
Matt Might 的经典文章，按用途推荐“高级编程语言”：如果追求就业就选主流语言，如果追求表达力、学术研究或创业，则推荐 Haskell、OCaml、Scala 等函数式语…
编程与软件工程上首页 8 次 · 2009–2022matt.might.net我的 Forth 与栈机器经历
Yosefk - My history with Forth & stack machines
作者以亲身经历回顾了使用 Forth 语言和栈式机器的历程：既赞叹其简洁优雅、代码量小、可自举的优点，也坦率指出栈操作在实际编程中的痛苦，以及 Forth 社区文化中的问题。
编程与软件工程上首页 8 次 · 2010–2024yosefk.com编辑精选