编程与软件工程nayuki.io
用标签而非层级重新设计文件组织方式
Designing better file organization around tags, not hierarchies (2017)
2018 — 2021，它一次次回到首页
黑点是上首页（≥ 50 分）的那次投稿，空心点是没冲上去的投稿，点越大分数越高。
导读
作者认为传统层级式文件系统与人类知识的丰富结构不匹配，主张用标签（而非文件夹层级）来组织文件，并探讨了无文件名、哈希寻址、不可变性、外部元数据等一系列重新设计文件系统的想法。文章多次登上 HN 首页，引发了关于标签与层级孰优孰劣的长期讨论。
为什么经久不衰：文件组织是每个计算机用户都面对的日常痛点，这篇文章把问题梳理得足够系统，以至于多年后仍被反复翻出来讨论。
HN 评论精选
分面分类早有成熟理论，但成本太高，所以层级体系才得以延续
图书管理员们一直在对世界知识进行分类，他们早在 1933 年就发展出了分面分类系统来应对这些问题。值得注意的是，层级结构嵌入了分类者的视角——比如杜威十进制法对宗教的分类就很荒谬：对基督教各教派做了极细的区分，却把所有非基督教宗教塞进几个敷衍的类目下。可惜我们大多数人请不起图书管理员来为自己量身定制分类体系，所以简单的层级分类一直沿用至今，分面分类只在数字资产管理等专业领域应用。
fmajid查看英文原文
Librarians have been classifying the world's knowledge since forever, and they developed faceted classification systems (Ranganathan, 1933) to deal with these issues. https://www.researchgate.net/publication/321840994_Ranganathan_and_the_faceted_classification_theory A notable one that hierarchies embed the point of view of the classifier, e.g. the Dewy Decimal's ridiculous classifications of religions (codes 200–299), making minute distinctions like 285 (Presbyterian, Reformed, Congregational), 286 (Baptist, Disciples of Christ, Adventist), then putting all non-Christian religions under a handful of afterthought headings 292–299: 294 for Hinduism, Buddhism, Sikkhism and other religions of Indian origin, 295 for Zoroastrianism and its descendants, 296 for Judaism, 297 for Islam and Bahaism lumped together, and 299 for New Age. Unfortunately, most of us do not have access to the services of a librarian to develop a taxonomy that corresponds to our own point of view then classify our files accordingly, which is why simple hierarchical taxonomies have endured and faceted ones seldom beyond specialized applications like Digital Asset Management.
标签组织只适合特定内容类型，层级对大量杂乱文件更实用
这东西的实用性高度取决于内容类型。对 mp3、视频或自己拍的照片（带元数据）也许可行，但我无法想象对我那两百万个不属于这些整齐类别的杂乱文件做基于标签的组织。我在做 X 项目时就去 X 目录，需要的一切都在 X 之下的层级里，我从不关心 X 之外的东西，也不想让 X 里的文件污染某个全局命名空间。目录层级对我来说是个很好的抽象，我用的所有工具也都很好地支持它。
megous查看英文原文
Usefullness of this is highly content specific. It maybe works for mp3s or videos/photos you made yourself and contain some metadata. I can't imagine tag based organization of all the random 2 mil. files I have that don't fit into these neat categories. I don't need access to most of these files unless I'm working on something relevant to them. When I work on X, I go to directory X and everything I need sits below X in some hierarchy. I'm never interested in anything that's below X unless I'm working on X. I don't want stuff from X to pollute some global namespace just because some mp3 or PDFs are present under X. That's true for hundreds of personal projects and tools I've made. Directory hierarchy is a pretty neat abstraction to me and all the tools I use already support it well.
标签会带来新的复杂性，层级虽不灵活但更易维护，问题可在应用层解决
作者在组织大规模关联数据方面有点落后于时代。标签作为一种通用想法太随意，缺乏组织标签本身的系统。语义网技术栈（分类法、本体、查询语言）是一种改进方向。简单层级就是……简单。标签也很简单，但人们一旦试图应用、查找、组织标签，它就迅速演变成新的复杂性。层级不够灵活，但更容易理解、维护和使用。我的主要顾虑是：层级并不真的需要被“修复”，把东西做得更复杂未必更好，完全可以在应用层组织文件而不必重写文件系统。
throwaway984393查看英文原文
I think the author is just a little bit behind the times in terms of organizing large corpuses of inter-related data. Tagging as a general idea is too fast-and-loose without a system/structure to organize the tags. Semantic Web stacks are one way to improve on this using taxonomies and ontologies, query languages and data specs; they almost mention it in the alternative systems ("touples") but don't dig into just how hard it is to manage data using unstructured references (or even structured ones!). Simple hierarchies are ..... simple. Tags are simple too, but they quickly devolve into new complexities as people try to figure out how to apply them, find them, organize them. Hierarchies aren't typically as difficult to manage because it boxes you into re-creating the same mental model for organization, just with different classifiers for each level of the hierarchy. They're less flexible, but they're easier to grok, maintain, and use. My major concern is that there isn't really a need to "fix" hierarchies, it's just a nagging problem that someone doesn't want to deal with, so their solution is to make something more complicated.... and more complicated might not make it better. It should also be feasible to design applications to organize the files without having to rewrite filesystems.
亲历者证实：这些理念在 Newton 和 WinFS 中都尝试过，落地极难
这是很好的思考，与我多次尝试做的事情高度重合，我很希望它最终能实现。例如我 1990-1996 年在 Apple 参与的 Newton 存储系统就把组织与存储分离，从而支持多套（标签和/或层级）组织系统，最终成为 Newton OS 中的“soup”系统，对象按内容而非层级检索。最近几年我又在微软参与 WinFS，它与本文的原则有大量重合，也恰恰证明了从“看起来都对的原则”到“成功落地的实现”有多难。
wrs查看英文原文
This is good thinking, and mostly overlaps with what I've tried to do a few times, so I would love to see it finally happen somehow. For example, the Newton storage system I worked on at Apple 1990-1996 was based on separating organization from storage so we could have multiple (tag and/or hierarchy) organization systems. That eventually became the "soup" system in the shipping Newton OS, where objects were retrieved by content rather than hierarchy. More recently, I spent some painful years working on Microsoft's WinFS, which had a ton of overlap with the principles here, and demonstrates just how hard it is to go from some nice principles that all seem like the Right Thing to an actual successful adopted implementation of the principles.
历次讨论
同类还值得读
开源应用架构
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编辑精选