编程与软件工程aosabook.org编辑精选
开源应用架构
The Architecture of Open Source Applications
2011 — 2024，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
《开源软件架构》（AOSA）是一本在线免费书，邀请知名开源项目的作者亲自剖析其内部设计，涵盖 SQLAlchemy、LLVM、Audacity、Apache、Bash 等系统。它不是泛泛而谈的教程，而是从真实代码出发，讲清楚关键模块为何这样划分、哪些决策带来了后续的遗憾。
为什么经久不衰：它提供了极少数由项目核心作者亲笔写下的架构自述，把开源代码背后的权衡、错误与修正摊开来讲，今天读仍能学到书本外的一手工程判断。
HN 评论精选
列出书中多篇精彩章节，并提议未来可以纳入更多现代开源项目的架构剖析。
我最喜欢的是 Michael Bayer 写的 SQLAlchemy 一章（很好地观察到它是在 SQL 之上先构建核心语言层，再分出声明式/ORM 系统），以及 Chris Lattner 的 LLVM 和 James Crook 的 Audacity（其中关于 wxWidgets 的讨论很有意思）。不过第一、二卷里几乎每篇都值得一读！希望能看到更多，比如 Blender（尤其是 2.80 的 GUI、Python 脚本集成、图形卡/渲染/建模）、GIMP/Inkscape/Krita、Saltstack/Ansible、GTK/Qt、i3/sway、Wayland/Xorg、VSCode/Electron、React/Vue、Android SDK、Unity/Unreal、.NET Core、black/clang-format、sphinx/pandoc、systemd/mesa/cairo，以及各种语言实现（CPython、TypeScript、LuaJIT、GHC、Swift）等等。
tony查看英文原文
Favorites: - SQLAlchemy by Michael Bayer: https://www.aosabook.org/en/sqlalchemy.html (nice observation of core language on top of SQL, then the separate declarative/orm system) - LLVM by Chris Lattner: https://www.aosabook.org/en/llvm.html - Audacity by James Crook: https://www.aosabook.org/en/audacity.html (interesting mentionings of wxwigets) Note that pretty much everything in volume 1 and 2 is interesting, though! What would be nice to see, non-exhaustive: - Blender: Especially 2.80, an analysis of its GUI/widgets, integrated python scripting, and everything else (wiring into graphics cards, rendering, shapes). There's a lot of stuff that could be covered - Gimp / Inkscape / Krita - Saltstack / Ansible / Fabric or PyInvoke : These have nice abstractions on top of system functionality / programs and delivery magic that'd be fun to go into - GTK, QT - Tiling window managers, e.g. i3, swaywm, awesome - Wayland, Xorg - Kdevelop, VSCode, Atom, Electron - React, Vue, Angular (it'd be nce to see more js) - Android SDK - Unity3D SDK, Unreal SDK - .NET Core - black (python formatter), clang-format, prettier - docutils, sphinx, pandoc - systemd, mesa, cairo, pulseaudio - implementations of python (cpython), typescript, lua, luajit, haskell ghc, swift
认为书中所选项目与多数企业 Web 工程师的日常相距较远，呼吁补充分布式系统和典型 Web 应用的架构案例。
这确实有意思，但我要说，这份清单上的大多数软件对 99% 的软件架构师/工程师（也就是我们这些在大型企业做 Web/服务端应用的人）并不相关。当然这不是作者的错，只是我经验里很少有组织愿意公开解释这类东西。希望能看到大型分布式系统、典型 Web 应用（UI、Web 层、数据层，再加点事件机制）、以及任何需要持续跨网络通信的系统的架构。Nick Craver 对 Stack Overflow 的讲解就很好，希望有更多类似例子。
sytringy05查看英文原文
This is interesting, however I'd say most of the software on this list not relevant for 99% of software architects / engineers ( ie all of us working on web / server side applications for BigCorp). It's not the fault of the authors of course, in my experience there's not many organisations interested in explaining stuff like this out in the open. It would be great to see the architecture of: - a large scale distributed system - a typical web app with UI, web tier, data tier maybe thrown in some eventing for good measure. - maybe anything else that needs to talk across a network all the time. Nick Craver from Stackoverflow does a great job of explaining this for how SO do it, any other good examples would be great.
以 Bash 一章为反面教材，说明单一、干净的解析器架构如何让 Oil 项目避免重复解析器带来的问题。
顺带一提，Oil 项目在某种程度上是（反向）受这篇非常有帮助的 Bash 架构描述启发而做的：作者在文中表达了对解析器架构的一些遗憾。我在 2016-2017 年的几篇博客里引用过它……这种有原则的架构后来在几个意想不到的地方得到了回报。总结：除了作者自己表达的遗憾，Bash 实际上还为自己这门语言准备了多个临时拼凑、并不正确的解析器，错误到另一个项目（bash-completion）得写代码来掩盖。Oil 则对所有用途使用同一个解析器，而且不会把交互提示符、别名展开这些正交关注点混进去。
chubot查看英文原文
FWIW the Oil project was partly (negatively) inspired by the very helpful description of bash's architecture: https://aosabook.org/en/bash.html The maintainer expresses some regret about the parser architecture. I referenced this in several 2016-2017 blog posts: OSH Parses Shell Scripts Up Front in a Single Pass. Other Shells Don't - http://www.oilshell.org/blog/2016/10/13.html OSH Can Be Parsed With Two Tokens of Lookahead - http://www.oilshell.org/blog/2016/11/17.html The Thinner Waist of the Interpreter - http://www.oilshell.org/blog/2017/01/26.html Word Evaluation - http://www.oilshell.org/blog/2017/03/09.html ---- This principled architecture ended up paying off in a couple unexpected ways, which I wrote about earlier this year: Oil Uses Its Parser For History And Completion - http://www.oilshell.org/blog/2020/01/history-and-completion.html Oil's Parser Doesn't Worry About Aliases and Prompts - http://www.oilshell.org/blog/2020/01/alias-and-prompt.html Summary: in addition to the regrets expressed by the maintainer in the article, bash actually has multiple ad hoc, incorrect parsers for its own language! They are incorrect to the point that a separate project (bash-completion) has code to paper over the errors. Oil uses the same parser for all use cases. Moreover, its parser isn't littered with orthogonal concerns like the interactive prompt and expanding aliases. ---- However I still need help finishing the project -- see what I've cut here: http://www.oilshell.org/blog/2020/08/risks.html And feel free to contact me (address on home page and in profile)
回忆以 Apache 架构为训练范本的经历，感慨年轻工程师缺乏对真实系统构建与权衡的了解。
多年前 AOSA 启发了我，我曾把 Apache 的架构当作学习范例（大约 18-20 年前）。很遗憾，很多年轻软件工程师完全不知道那些被大量使用的真实系统是怎么构建的，也不了解让产品在现实中稳定运行所需处理的各种权衡和边角情况。当时我们组织的第一步就是从源码编译 Apache（包括几个关键附加模块），配置它跑通一小组测试；通过的人才能进一步读源码。那段时光很有趣！
astatine查看英文原文
I was inspired by the AOSA many years ago and I had studied (and held out) as an example the Apache architecture (about 18-20 years ago). It is indeed a pity that so many younger software engineers really have no idea of how heavily used real-world systems get built. Nor do they understand all the various tradeoffs and corner cases that need to get handled to make products work well in real life. Building Apache from source (including a few key addon modules) and configuring it to work for a small set of tests was step 1 at my organization then. Those successful at this would then get into the source itself. Fun times!
历次讨论
同类还值得读
编程语言简史：简短、不完整且多半错误
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编辑精选学习 Haskell 时我希望知道的事
What I Wish I Knew When Learning Haskell
Stephen Diehl 整理的 Haskell 学习指南（以幻灯片/参考文档形式呈现），旨在让初学者快速了解学习 Haskell 时最需要知道的核心库、概念和工具。
编程与软件工程上首页 7 次 · 2013–2020dev.stephendiehl.com