语言与文风2022abortretry.fail
“Be”很好，就这么简单
'Be' is nice, end of story
导读
这篇帖子讲的是 BeOS 的文件系统 BeFS 的设计之妙——把邮件、索引、元数据都当作文件系统的一部分，评论区则变成了一场对 BeOS 时代的集体怀旧。对写作者的价值在于：技术文章用第一手的个人经历和具体细节来讲述，远比干巴巴的规格介绍更有感染力。
可以直接用的写作要点
- 01
用亲身经历和具体细节（型号、配置、遗憾）讲故事，比罗列参数更能打动读者。
- 02
好的技术写作要能回答'为什么它好'，而不只是'它是什么'——比如 BeFS 的妙处在于'收件箱就是一个文件夹'这样的具体场景。
- 03
怀旧式写作的感染力来自真实的遗憾感：'要是闪电没劈坏它，我还在用'比任何赞美都有力。
HN 评论精选
用具体场景说明 BeFS 的超前：邮件即文件，文件系统即应用。
即使二十多年过去了，我们仍然没有出现像 BeFS 那样酷的东西。有了能把一切建立索引的文件系统，谁还需要邮件客户端？你的收件箱和邮件本身就是某个文件夹里的文件，Tracker 窗口只是把邮件特有的元数据显示为列而已。
Veliladon查看英文原文
Even now over 20 years later we still haven't had anything near as cool as BeFS. Who needs an email client when the file system can literally index it all and your inbox and email messages are literally files in a folder in a Tracker window that's just displaying email specific metadata for its columns.
好的设计体现在细节：不要求用户是专家也能理解系统。
今年夏天我作为 Google Summer of Code 的一员参与 Haiku 的开发，这让我更希望主流操作系统能借鉴它们对待用户体验的态度。都是些小事：出错时自动提示打开图形化调试器、进程按应用分组。这些合理的 UX 不指望我是个巫师才能看懂发生了什么、如何深挖。当然它也有粗糙之处（说实话所有操作系统都有），但能用的部分是真的好用。
dominicm查看英文原文
I worked on Haiku this summer as part of Google summer of code, and it just made me wish their attitude towards user experience was more prevalent in mainstream OSs. It's little things like errors automatically prompting you to open a graphical debugger or processes being grouped by application. There's sensible UX that doesn't expect me to be a wizard to understand what's going on or how to dig deeper. Obviously it has rough edges (as, well, honestly all operating systems do), but the things that do work work really well.
用具体配置和真实遗憾讲述怀旧故事，是第一手经历的力量。
BeFS 太惊艳了。说实话我很怀念 BeOS。我在一台 Dell GX1 上跑深度定制的 BeOS R5.05，那机器简直是为 BeOS 而生的：内核支持的最大内存 768MB，GX1 恰好最大 768MB；GX1 的 Rage 显卡在 BeOS 原生支持（含 3D 加速）的极短名单上；网卡、IDE 控制器也都支持。我把 CPU 升到 1.4GHz 的 Tualatin-S，可惜前端总线只能跑 100MHz，只能降到 1.04GHz——但依然飞快。唉，真想念那台机器，要不是被闪电劈坏，我还在用它。它旁边摆着我的 NeXTstation Turbo Color，我一直不合理地把它当主力机用到 2008 年。33MHz 的 040 配 128MB EDO 内存，跑 OPENSTEP 4.2 加一堆朋友移植的好东西，甚至搞定了 SSLv3 能加载新网站。真后悔把它卖了。哦对了，我还有一台 FCC 认证前的双 66MHz BeBox，很酷但慢得要死。我的 BeBox 照片：https://www.flickr.com/photos/helfer/albums/7215762…
helf查看英文原文
BeFS was amazing. I miss BeOS, TBH. I ran a heavily customized BeOS R5.05 install that had upgraded bits from OpenBeOS (later, HaikuOS), ZetaOS etc. I ran it as a daily driver on a Dell GX1 SFF that I swear was designed for BeOS: Max RAM the BeOS kernel supported without hackery was 768MB - The GX maxed out at 768MB; The GX1 had a Rage GPU that BeOS natively supported (Including 3D Acceleration!) which was a very short list; the GX1 had a supported NIC, IDE controllers, etc etc. I had upgraded the CPU to a 1.4GHz Tualatin-S that, sadly, had to run at 1.04GHz as the GX1 wouldn't run a FSB higher than 100mhz so my 133mhz FSB Tualatin had to bop down a little. Still screamed. sigh I miss that system. I would still be running it if lightning hadn't fried it. It sat next to my NeXTstation Turbo Color that I used for way longer than was reasonable as my primary system, lol. The NeXT was a daily driver till 2008. 33mhz 040 w/ 128MB 60NS EDO. OPENSTEP4.2 + lots of ported goodies friends and I did. Even managed to get SSLv3 working and load newer websites! :D ... wish I hadn't sold it. Oh yeah! I also had a Pre-FCC certification dual 66mhz BeBox. Cool machine. Slow as shit though. The 603e in it wasn't natively SMP capable IIRC. The GLU chip could either run one CPU with L2 cache or dual CPUs with L2 cache disabled. Coherency was done in software. Unless I am horribly misremembering. It was a nasty hack and showed. My BeBox! https://www.flickr.com/photos/helfer/albums/72157621937392496/ My GX-1 and my NeXT :D https://www.flickr.com/photos/helfer/6676203105/in/photolist-73AQ7K-baXhA6-7u6dAA
亲历者的纪念品和细节让公司历史变得可触摸。
2000 年我在 Be 公司工作了七个月，公司倒闭被收购时被裁了。留了几件当年的纪念品：我的名片、三楼休息室的照片（有一两次看到 CEO jlg 坐在那张沙发上高谈公司愿景）、还有一块用 BeBox 主板做的写字板——对，我还留着它。
allenbrunson查看英文原文
i worked at be, in the year 2000, for seven months. i got laid off when the company went out of business and got acquired. a few relics from my time there. my business card https://platinumball.net/be/business_card.jpg third floor break room. i saw jlg sitting on that couch, holding forth on the company, once or twice. https://platinumball.net/be/break_room.jpg a clipboard made out of a bebox motherboard. yep, i still have it https://platinumball.net/be/clipboard1.jpg https://platinumball.net/be/clipboard2.jpg edit: ugh, some people are reporting my links are forbidden. i removed my .htaccess file, which had some rules forbidding hot-linking. maybe that will help? https://platinumball.net/be
同类还值得读
像说话一样写作
Write like you talk
这篇短文主张写作应像说话一样自然、清晰，避免装腔作势的书面腔。
语言与文风2015 · 647 分 · 272 评4 条写作要点编辑精选法律语言难懂源于写作不佳，而非专业概念
Poor writing, not specialized concepts, drives difficulty with legal language
这是一项认知科学研究：法律文本难懂，主要不是因为充斥专业术语，而是因为写作者把句子写得又长又绕、修饰语层层嵌套、回指距离过远。
语言与文风2022 · 559 分 · 322 评5 条写作要点编辑精选写得简单
Write Simply
保罗·格拉汉姆在这篇短文里主张：好文章应该写得简单——用日常词汇、短句、直白的结构，不为显得聪明而堆砌复杂表达。
语言与文风2021 · 484 分 · 330 评4 条写作要点编辑精选Tortured phrases：科学写作中出现的一种可疑文风
Tortured phrases: A dubious writing style emerging in science
《自然》新闻报道了一种在科学论文中蔓延的怪现象：原本标准的术语被同义替换软件改写成了古怪说法，比如把 "cloud computing" 写成 "haze figuring"。
语言与文风2021 · 329 分 · 256 评4 条写作要点编辑精选乔治·奥威尔 1940 年对《我的奋斗》的书评
George Orwell's review of Mein Kampf (1940)
这是奥威尔1940年对《我的奋斗》的书评。
语言与文风2014 · 305 分 · 240 评4 条写作要点编辑精选