
2023 年，那时候「两耳不闻窗外事，一心只读圣贤书」，在春招和秋招最激烈的时候我选择了们在图书馆里背书做题。大三暑假，我选择了留校备考。

2024 春，放榜时，我特意守在图书馆座位中，静待通知的那一刻出来。就当我满心欢喜迎接时，迎来的是一盆冷水。

当我看到惨不忍睹的成绩后，全身是懵的，虽然在此之前多次祈求上天垂幸，心存侥幸，然而现实仍给我当头一棒。或许是受到的刺激太大，连续几天身心全是木木的，血红色的分数在我梦魇中挥之不去。终于，心里慢慢接受了这个事实，星夜中独坐房台放声痛哭。

泪光中回顾了我一年苦逼的备考历程。炎炎夏日下在充斥汗味图书馆内做题，深冬腊月中抚着冻僵的手夜读，历历在目，无不诉说着心酸。可是为什么会是这种结果。。。

事后也算总结了教训，由于我过于乐观及对考研本身无经验，一战时发挥失利被刷。

当然，因为考研之事，自然也错过了春招秋招。校招，本是找工作的好机会，被我错过，简历投了上千家公司，几乎无一问津。

身边同学交集也逐渐变少，大四一年，每个人都有自己要忙的事，轨迹也基本定型。或已经积累足够的实习经验入职校招，或已经在父辈荫护下有长辈关照，或已经准备创业，或已经靠着不错的家底脱离竞争享受生活。

而我，只能像只无头苍蝇，在 BOSS，智联等 APP 消息列表中，看到一条条已读不回，心里无力感愈发强烈。

人活着，总是要有一些盼头？就比如我考研的那段日子，晨星带月，每早眼睛一睁，哦，我的任务是提高分数，多做几道题，多背几本书。短暂调整，直奔图书馆，又是忙碌而充实的一天，这也是我活下去的动力。

而我，自此之后，一蹶不振。考研彻底失败，春招也没有。每早醒来也只是望着天花板发呆很久，脑子空空的，没有任何动力，如行尸走肉一般。当下根本不知道该干什么，我又该何去何从？

考研失败，错过校招，再加上那段时间感情不顺，多重打击接连袭来，眉眼中多了些疲惫和倦怠。

那也是我此生中，或许是目前遇到的最大的失利，似乎人生跌至谷底。

伤心之余，日子还是要继续。某天，我释然了，也畅怀了。当下又还能如何呢？

或许是因为应激，或许是心有不甘，也或许是身上学生的稚嫩稚气未褪，不想过早投入社会。心中的想法愈发坚定，萌发生根：我要二战。

我的父母也没有多说什么，没有催着我找工作，也没有指责、埋怨。而是用缄默表达了对我的默许和支持。

我重新打开淘宝，下单了新版 880，660 系列的真题。

重新背起被我闲置已久的书包，重新踏上去图书馆的小路。宿舍距离图书馆不远，这条小路我走了三百多天，然而不过是两点一线、目不窥园。而我第一次见识陌上的冬去春来，云卷云舒时，才不由漾起一丝酸楚：我脱离世界太久了。

重逢阔别已久的图书馆，再次拿起手笔，看着之前书上做了无数遍的题，在草稿纸上慢慢演算既熟悉、又陌生的数学公式。

![](https://image-assets.dreams.plus/20250507141047173.jpg)

这次，我特意选了楼层高一点的自习室、靠窗的位置。

做题累了，就在座位上托腮远望深山、遍地绿树，看西北的风抚摸天上的云彩。月夜星辉时，我还特意盯着天上的月亮盈亏变化，正好数满一个月。

我的学校在山区，黄土高原，四周绿山环绕，夏季远处一览无余，晚上，没有城市的纸醉金迷的霓虹灯，能看见天上银河星光璀璨。

有时午后在座位上酣睡，高层遮挡较少，以阳光为被、以书本为枕。在日光沐浴下沉沉睡去。这样的日子，又持续了两个月。

![](https://image-assets.dreams.plus/20250507134057481.jpg)

早春过的很快，入夏，绿叶取代了招展的花枝，知了蝉鸣取代了春鸟嘤鸣。

我的本科迎来了尾声。毕业设计答辩完毕，同学们最后一次在校园内齐聚。

当我穿上学士袍、戴上学士帽，手捧毕业证书，恭恭敬敬接受院长挂穗，站在台上拍照时，我的本科四年结束了。

一声毕业照的快门咔嚓声响，给我四年的大学时间画上了句号。

![](https://image-assets.dreams.plus/20250507134551554.jpg)

但，我的脚步仍然没有结束。

身边的同学、室友一个接一个离开，打包行李，踏上轰鸣的火车，奔向远处，不知何时再相见。

而我，选择了留守学校，在图书馆，继续弥补我的遗憾。考研，是一个人的修行。

> 爱你来自于蛮荒，一生不借谁的光  \
> 你将造你的城邦，在废墟之上

## 生活还在继续

与图书馆为伴的时间很快，从五月份，就来到了七月份，作为毕业生，学校给我下达了最后通牒，毕业生必须限期离校。

我因为选择了二战，留守学校备考，此时也一时没了主意。

不过好在有人给我推荐了学校的「第二学士学位」项目，允许我在学校辅修一个双学位，到时候下学期可以继续留在学校，借用图书馆，心想也正合适我，于是申请了，被学校的第二学士学位录取。

九月，开学后，我再一次来到这个城市，这所学校。看见新生们在迎新大巴旁边叽叽喳喳，眼里尽是期待。

这个场景，忽然让我回到四年前，秋风习习，叶落梭梭，迎着朝霞。也是同一时间，我的父母亲自带着我给我送行，来到这所大学。

思绪回到从前，也是在 2020 年 9 月，我的父母带着我，坐了十几个小时的火车，三人满心欢喜踏入这个从未来过的西北重镇城市，来到这所学校里。

> 昔我往矣，杨柳依依  \
> 今我来思，雨雪霏霏

下火车时，正是凌晨五点，天刚刚破晓，黛紫染红了天空。

![](https://image-assets.dreams.plus/20250507133811658.jpg)

心中多了些悲凉。而今是我独自一人再次归来，继续我未完成的修行，是什么心情？满心悲凉、还是考研失败后的屈辱，或是对未来的迷茫。

再一次来到学校，校园里再也没有以前朝夕相处的同学，他们早已远去。

这下，在学校里，我就是彻底的孑然一身了。

入学后，我也认识了其他同样报了二学位的同学，不乏去年考研失败的、考公被刷的，跟我一样，都是立志于在校内再战，志在必得，继续未完成的事业。

老师允许我不上课，全心全力在图书馆备考。

我也如此。下一学期，我又开始投入紧张的备考，重拾去年时的状态。

在图书馆，继续刷我做了很多遍的题，回归到固定的轨迹，无非是四科。白天泡图书馆，晚上回到宿舍继续背单词、背书。这样的日子又持续了四个月。

2024 年的考研日期是 12 月 20 号左右，正值冬至，一年中黑夜最长的时候。这天我早早起来，冒着寒霜和黑夜踏入考场。

考试很快，下笔做题，就像我平常在图书馆里奋笔疾书写卷子那样，一气呵成，两天，做梦似的，就过去了。

## 落幕

4 月 3 日，早晨的闹钟把我唤醒。微信学信网给我弹出了一条通知，名单出来了。

悬着的心终于放下了，分数还可以，对得起我去年的努力。

考上了，拟录取通知下来了，看着报考系统上红色的「拟录取」时，刚开始或许有一点欣喜，但是没有想象的那么轰轰烈烈，并没有想象的那么开心。

考上了，然后，没然后了。

我想象中的，只要我接收到录取通知的时刻一到，我马上要买一箱啤酒，烤几个腰子牛排，暴饮暴食，熬夜通宵打游戏，想打多久就打多久，并没有发生。

只是蜷缩在昏暗的被窝里睡了很久很久。剩下的就是发呆，无尽无止地发呆、睡觉，过着混吃等死的日子。

偶尔也来到图书馆里，重温伏在书桌上的感觉。

![](https://image-assets.dreams.plus/20250507133510044.png)

> 草堂春睡足，窗外日迟迟

## 人生是旷野

打开很久没看的贴吧，信马由缰地浏览研究生学校的帖子。期间很幸运也找到了同学院的师兄，加上了他们的微信，向他们咨询了导师情况，接着跟师兄师姐聊了很晚，聊了读研生活和感想。

阴云很快再一次笼罩在脸上。

看着他们在抱怨读研压力大，一周两次组会，通宵做实验，甚至住在实验室，为论文数据发愁。

在四月中旬，我抽空给心仪的导师发了邮件，线下面谈选入组的事宜。

当我再次来到研究生学院，参观了实验室、工作室，逛了一圈，当我看到有师兄摆着一架行军床，上面还有要换的衣服和被子，我就知道这事肯定没那么简单。

是啊，我才理解到网上所说的，「研究生只有在录取和毕业的时候才是开心的」。

让我慢慢对研究生袪魅的是，读了研究生，也只不过是从一个牛马转换到另一个牛马而已，并不会让失业、收入改善多少。资本主义下任何人都只是待价而沽，出卖劳动力的工具人。决定就业的只是市场供需关系。

这也让我对研究生的生存逻辑有了更深入的了解。

就看现在的研究生「毕业即失业」现象比本科生并没有改善多少甚至还有严重趋势，说实话哈，有点不想读了。

**唉。**

当我们耗尽心力攀爬一座高山时，往往以为山顶的风景能消解所有疲惫，却可能发现，山顶的云雾遮蔽了预期中的壮丽。

这种"成功后的虚无感"恰如坦塔洛斯的处境，最渴求之物近在咫尺时，反而最令人清醒地认识到生命的本质。

当初我花费了那么多时间精力去考研，受了很多委屈，整个 2024 年都投入在上面，如今看来，这段经历是否值得？

人人都没有历史视角，我也不知道。但它就是个经历，是已经刻入我生命年表中的记录。

人生是旷野。以后的事情谁能说得清楚呢？未来的事情还是交给未来回答。至于读研是否值得，就当是投资未来了。

作为 00 后，我们所生活、经历的时代背景是十分魔幻和割裂的，这十几年恍如隔世，从网上调侃的「生于非典、考于新冠」，我经历了高考延期、三年封控、宿舍网课，也见识了多轮时代加速、急刹车等魔幻操作。

三年可以改变很多事，我是亲身经历过从 19 年到 23 年的变化的，18-19 年的时候社会的乐观顶峰，到 22 年又何其绝望与悲观。

「流动的现代性」在此显现得淋漓尽致。只能期望下一个三年好转吧。

当传统的人生脚本（本科、读研、工作、成家）越来越难以兑现承诺时，更需要培养冲浪者的生存智慧。就像在考研间隙观察月相变化的顿悟时刻，真正的救赎或许在于保持对生活诗意的凝视。

> 夫人之相与，俯仰一世，或取诸怀抱，悟言一室之内；或因寄所托，放浪形骸之外。虽趣舍万殊，静躁不同，当其欣于所遇，暂得于己，怏然自足，不知老之将至；及其所之既倦，情随事迁，感慨系之矣。向之所欣，俯仰之间，以为陈迹，犹不能不以之兴怀；况修短随化，终期于尽。古人云：“死生亦大矣。”岂不痛哉！

对我而言，这次考研二战的终极意义，或许不在改变外在境遇，而在培育一颗能感知四时流转、星移物换的丰盈心灵而已。


2025 年研招已经落幕，考上了，但似乎也并没有那么开心。日后，救赎之道仍待探索，毕竟，人生是旷野嘛。

考上了，但似乎也没有那么开心


I have tried to do technical writing in English on intend since 2022, when I made my mind of putting wheels on my shoulder for English study. Actually I have tried my English writing skill on intend by this way for make my language level better improved. And during these years I have experienced many challenges and troubles in conquering English.

The first one is vocabulary size. I allocated many of my vigors on expanding vocabularies and accumulated English expression particles in studying and reading. But soon I realized that reading technical text and literature text are two different realm logic.

The technical text are legible with perspicuous grammar syntax structure, and that's why I could read many of opensource project documents without any difficulties. The only challenge is reserve of terms and jargons. That's why do we need specialized professional English, for English has been contaminated by more loan words, and there are more amorphous word ideographic stemmer rules in each terms. To be honest I have complain about English more on this problem, it erects human-made thresholds among variable industries. The topic seems too be far-fetched. Let's go back to the technical writing. The another problem is English term are highly specialized, that is to say polysemy may lead to ambiguity if without any context details. For example, the word *layer* has distinguish meanings in software development and stratum geology. Also non-native speakers tend to confuse synonyms (e.g., "accuracy" vs. "precision") and need to rely on terminology databases or industry standards (e.g., IEEE Standard Glossary).

For special target portrayed, the passive voice in English is frequently used in technical writing (e.g. "The experiment was conducted..."). Non-native speakers may overuse the active voice, which affects objectivity. Complex sentences (e.g. conditional clauses, participle structures) are prone to grammatical errors. The concise principle of technical writing should be followed (e.g. IEEE recommends using short sentences).

Improper use of logical adjunction-connectors ("therefore", "however") between paragraphs can weaken the chain of reasoning. The English technical writing needs rigorousity suits for logical deduction chains. But for non-native speakers, the English adjunction connector words are too far exquisite to comprehend them easily.

Here, I found a pretty worth reading book titled *Science Research Writing for Non-native speakers of English*. [Here is the download link](https://z-library.sk/book/25451495/4d36ea/science-research-writing-for-native-and-nonnative-speakers-of-english.html). It's a practical guide designed to help researchers and students whose first language is not English master the conventions of scientific writing in English. Authored by Hilary Glasman-Deal, the book focuses on the structure, style, and clarity required in academic research papers. It systematically breaks down each section of a scientific manuscript—Introduction, Methods, Results, Discussion (IMRaD), and Abstract—providing clear templates, annotated examples, and phrase-level guidance.

Here is the table of contents:

![](https://image-assets.dreams.plus/images202502122348927.png)

Based on problem mentioned above, I have made a plan for training technical writing in English. This 12-week plan is designed to systematically improve scientific writing skills for technical writing. Adjust intensity based on schedule.

**Phase 1: Foundations (Weeks 1–3)**  
**Goal**: Master structure, grammar basics, and discipline-specific vocabulary.  

1. **Reverse-Engineer Papers**  
   - Select 3 high-impact papers in your field (e.g., from *Nature* or your target journal).  
   - Annotate each IMRaD section: Highlight how hypotheses/results are framed, transitions between paragraphs, and verb tenses.  
   - Create a "phrase bank" of recurring patterns (e.g., "Our data suggest..." in Discussions).  

2. **Grammar & Style Drills**  
   - Daily: Complete 1–2 exercises from *Science Research Writing for Non-Native Speakers* (e.g., tense consistency in Methods).  
   - Use *Academic Phrasebank* (University of Manchester) to practice hedging/emphatic language.  
   - Tools: Enable "Technical Writing" mode in Grammarly; analyze suggestions for passive voice/precision.  

3. **Vocabulary Building**  
   - Build a glossary of 50+ field-specific terms using *Elsevier’s Dictionary of Technical Terms*.  
   - Practice synonym differentiation (e.g., "demonstrate" vs. "indicate") via quizzes on *Quizlet*.  

**Phase 2: Drafting & Precision (Weeks 4–6)**  
**Goal**: Write structured drafts with clear logic and technical accuracy.  

1. **Section-by-Section Practice**  
   - **Abstract**: Write 10 one-sentence summaries of existing papers, then expand to 250-word abstracts.  
   - **Methods**: Describe a lab procedure twice: once in active voice (blog style), once in passive voice (journal style).  
   - **Results**: Convert raw data (graphs/tables) into 3 versions: overly detailed, too vague, and Goldilocks-level.  

2. **Peer Simulation**  
   - Join *r/AskAcademia* or *ResearchGate* to share drafts for feedback.  
   - Use the "Three Layers" editing technique:  
     - Layer 1: Logic flow (Does each paragraph answer "So what?").  
     - Layer 2: Technical accuracy (Verify units, abbreviations, citations).  
     - Layer 3: Language (Prepositions/articles, conciseness).  

3. **Tools Deep Dive**  
   - Learn LaTeX basics (Overleaf tutorials) for equations/formatting.  
   - Run drafts through *Hemingway Editor* to eliminate "Very Hard to Read" sentences.  

**Ongoing Habits:**  

- **Weekly**: Critique 1 poorly written paper (e.g., retracted papers on *Retraction Watch*) to recognize red flags.  
- **Monthly**: Attend 1 virtual workshop (e.g., *ACS Webinars* on writing).  
- **Toolkit**: Maintain a "Writing Swipe File" (YuQue/Notion) for brilliant sentences/structures you encounter.  

Hope for good progress.


I have tried to do technical writing in English since 2022. And now I have came up with a further plan.

About Technical Writing in English.


在 2024 年上半年，我开始了为期一年的背单词计划，每天坚持记忆、复习 200-400 个单词，坚持了将近一年，大约累计背了 16000 个单词，把 IELTS，TOFEL，专业四级和大半个 SAT 词书都背完了。一路走过来再回顾这些历程，虽然过程极度痛苦，日日夜夜，但好歹也算走过来了，想想也挺不容易的哈。

![](https://image-assets.dreams.plus/images20250116194715.png)

在背单词的过程中，我也累积了一些经验。我打算把这些经验总结一下，然后再分成几个篇幅来依次说说。本次想要分享的是：挑选词典。在 2024 年上半年，我买入了四本词典，都是牛津学习词典系列。

![牛津短语动词词典，和新旧两版同义词词典](https://image-assets.dreams.plus/imagesee97854c285b3202284930edd6fef07.webp)

![牛津习语词典](https://image-assets.dreams.plus/images20250116170944.webp)

我选的这些词典，它与像牛津词典、朗文词典等知名的综合大词典不同，它属于“专题词典”，针对某一目的或者主题来收录词条，使用目的性较强，专门为学习者设计，使用“专题词典”来对英语进行有目的的、针对性的学习，效率更高。这也是我目前正在学习的方法。

英语的学习难点在于词汇、词法。据统计，一个成年美国人的基础词汇量是 20000-30000 左右，也是一个美国高中生的词汇水平。也就是说，如果你想毫无障碍的阅读大多数美国语料，那么你的词汇量必须达到两万以上，才能勉强不卡壳。所以学习英语的过程也是在不断征服单词的过程。

## 同义词词典

首先是介绍同义词词典。

对任何有过背单词经历的同学来讲，英语的同义词现象非常常见，每次背单词的时候经常会受到同义词的困扰，每一个“含义”几乎都有 3-4 个同义词！

因为英语在历史的发展进程中吸收了大量的外来语，所以现在几乎是世界上词汇量最大的语言，而其中的同义词、近义词就占据了大半。确实，相比其他语言如日语、法语、西班牙语等等，**英语的同义词现象时最严重的。**

举个例子，“拒绝”的表达，就有 Refuse、Reject、Deny、Rebuff、Dismiss、Turn down、Oppose、Withhold、Repudiate、Resist 等等，它们都有“拒绝”之意。如果你单独把这些词一个一个去记，那么很难把它们“内化”成自己的一部分。在从外界接收、背诵了一大堆单词之后，久而久之，大脑还是处于无组织、混乱的状态。

假如你在英语写作和英语对话中，想要表达“拒绝”时，你能在大脑中一瞬间枚举出以上所有的表达吗？而且上面的同义词，在不同语境下都会有一些很细微的差别，你能思索一番后，举一反三，选取出最合适的表达词汇吗？例如：refuse 和 decline 都表示“拒绝”，但 decline 更礼貌，而 refuse 更直接。

还有，雅思考试、托福考试对单词的考题，大都是以“同义词替换”来考察的。需要识别同义词和近义词来回答阅读和词汇题。

所以归纳总结就非常有必要。这样才能把消极词汇转化为主动词汇。在背单词时，把不同的单词按照同一个或者相似的 idea 进行总结就尤为重要。归纳同义词和近义词不仅是词汇学习的一种技巧，更是一种提升语言能力的策略。它可以让学习者从“记单词”转向“用单词”，从而在实际交流中更自信、精准地表达自己。

还有，从同义词入手，可以显著提高背单词的效率，对提升词汇量都有着不小的帮助。

![](https://image-assets.dreams.plus/images20250116173639.webp)

这也是同义词词典存在的意义。我推荐牛津英语同义词词典，它按照首字母编序，为每个单词都枚举出了对应的同义词和近义词。

![](https://image-assets.dreams.plus/images20250116175401.webp)

如上图，举个例子，tedious 在表达“乏味、无聊”时的同义词，就有 boring,dreary,dull,monotonous,tire 等。它把对应的意思的相关近义词、同义词全部枚举出来，对归纳总结和提升词汇量都有不小的帮助。

它由于是 2001 年的早期初版，在淘宝上可能买不到新书了，只有二手书，价格低廉，大约 15 元以内就可以包邮到家。当然，不想花钱也可以下载电子书。同义词词典的初版在 Zlibrary 上可以找到电子版：[牛津同义词词典 - Zlibrary 链接](https://z-library.sk/book/22266968/4f2cc7/%E7%89%9B%E6%B4%A5%E8%8B%B1%E8%AF%AD%E5%90%8C%E4%B9%89%E8%AF%8D%E8%AF%8D%E5%85%B8.html)。

但是这本书还有一个新版，是 2014 年出版的，它还对近义词加上了辨析内容。

![](https://image-assets.dreams.plus/images20250116181118.webp)

它与初版相比，更注重于辨析，所以它只收录了常见同义词，删减了很多，而且价格也比初版更贵（160 元）

比如对“拒绝”的同义词，它的收录内容预览如下。

![](https://image-assets.dreams.plus/images20250116175951.webp)

**但是，我还是建议选初版的同义词词典。** 一来，我个人推荐在大量阅读的过程中学习同义词辨析，而不是词典中。二来，新版的同义词词典只收录了一些初级的、常用的词汇，对于进阶一点的词汇都删减了。**而且价格不菲，性价比不高。** 新版的词典我在网上没有找到电子版本。

所以还是推荐使用初版的，虽然初版词典没有辨析内容，但是它相较于新版的，词量更加全面。

当然，为了学习方便，我把这本词典做成了词表，[发布在了 Github 上](https://github.com/PrinOrange/my-english-word-books/tree/main/dictionaries/%E7%89%9B%E6%B4%A5%E8%8B%B1%E8%AF%AD%E5%90%8C%E4%B9%89%E8%AF%8D%E8%AF%8D%E5%85%B8/plain)，读者可以下载，导入不背单词、墨墨单词等单词 App 上。

同义词词典适合作为在学习过程中的总结阶段中使用，总结同义词可以帮助建立单词之间的联想，形成语义网络，助于更全面地理解一个词的含义和使用场景。长期积累有助于内化语言逻辑，逐步形成地道的英语语感。

## 短语动词词典

在英语学习阶段，只背“单词”本身是不够的，因为在英语中还有大量的“短语动词”，也就是 verb + adv./prep. 的形式，这类词的含义经常让人捉摸不透。

比如 take up 这个词，就是 verb. + prep. 的组合。

按照我们朴素的理解，“take”是“带走”的意思，“up”是“上面”的意思。乍一看，我肯会以为它是“把某件物体带到上面”的意思。

但实际上并不是，它是“占据”的意思。而“up”在这里不是介词而是副词，表示“彻底”的意思。和“把某件物体带到上面”没有任何关系。也就是说，我们无法单单从“take”或者“up”上推测这个短语动词的含义。类似的还有“take off”，是“起飞”的意思。

再换一个，比如 take over, make over, pull over，你能按照朴素的理解来推测它的含义吗？

但它们的含义是“接管”、“转让”和“停车”。

这就是短语动词的恶心之处，一个含义加上另一个含义，就生成了一个完全毫无关联的、新的含义。

短语动词很多是常见的动词加上一个常见的介词或副词，给人一种“很熟悉”的感觉，但实际上完全是另一个意思。而偏偏在英语的文本中（尤其是在互联网上），短语动词的使用频率又往往会占到四成水平。短语动词广泛用于英语的口语和非正式交流中，几乎每一个母语者都会经常使用。尤其是在英语口语中，母语者往往倾向于使用短语动词而不是正式词汇，因为它们更简单、自然。

对于非母语者来说，不积累足够多的短语动词，就会造成在阅读上的南辕北辙。**对于短语动词，其实没有什么好的办法，只能死记硬背，把它们“当成一个独立的新单词”来背。这也是一个难点所在**。

也不要指望自己像做数学题那样“推测”含义，因为短语动词的组合极为灵活，在英语的发展过程中大都是“约定成俗”的用语，**甚至没有什么逻辑，并不是简单的词义相加就能推测出来的。**

所以，我推荐“牛津短语动词词典”

![](https://image-assets.dreams.plus/images20250116184439.webp)

这本词典收录了大量的短语动词，并且总结出了一些常用义项。比如 run into 这个词，词典就给出了三种解释：遭遇、遇到、纠缠三重含义。

![](https://image-assets.dreams.plus/images20250116184809.webp)

它也是以词为单位的，把每个动词都列举出所有对应的短语动词，并依次编排，比如 rush 这个词

![](https://image-assets.dreams.plus/images20250116185052.webp)

短语动词大都是动介组合或者动副组合，其中的副词和介词又被称为小品词，像 turn out,make out，等，out 就是小品词，在短语动词中起到辅助意义的作用。

这本词典在附录中也总结了很多小品词，例举出了小品词的不同含义，总结的很全面，比如 over。

![](https://image-assets.dreams.plus/images20250116191451.webp)

这本书总结了 6000+ 左右的短语动词，已经满足了九成以上的场景覆盖需求，对于学习者来说已经完全足够了。这本书的价格也很亲民，40 元左右，影印书更便宜，9.9 元包邮。当然，它在 Zlibrary 上也有电子版：[牛津短语动词词典 - ZLibrary 链接](https://z-library.sk/book/18213158/3388a4/%E7%89%9B%E6%B4%A5%E7%9F%AD%E8%AF%AD%E5%8A%A8%E8%AF%8D%E8%AF%8D%E5%85%B8-%E8%8B%B1%E6%B1%89%E5%8F%8C%E8%A7%A3%E7%89%88%E7%AC%AC%E4%BA%8C%E7%89%88-oxford-phrasal-verbs-dictionarychineseenglishenglishchinese2nd-edition.html)

## 习语词典

在进阶阶段，接触到英语电影、小说的时候，里面会经常有一些修辞性的、本土化的表达，称之为习语“idiom”，类似于中文里面的“成语”。同样也不能只从字面上理解。

比如“得陇望蜀”就是个修辞性词语，来形容一方野心勃勃、贪得无厌。但是在上个世纪中，中方对苏联的外交翻译中，因为外交工作人员的失误，直接翻译成了字面意义上的“占领了甘肃和四川”，导致双方出现战略误解。

英语习语跟成语一样，它也跟英语文化紧密结合。如果想要深入接触英语文化，尤其是阅读英语本土文学作品，理解它们的表达，那么去学习一些习语则是必要的。许多习语反映了英语国家的文化、历史、传统和价值观。例如："Spill the beans"（泄露秘密）来源于古希腊的投票习俗。通过学习习语，可以更好地了解英语文化和母语者的思维方式。

对英语学习者来说是非常重要的，因为习语不仅是语言的重要组成部分，还能够丰富表达方式，帮助更好地理解英语文化和母语者的思维方式。

另一方面，英语习语有比正是表达更为灵活微妙的表达能力，更有感情色彩，这是常规表达中难以传递的。例如："It's raining cats and dogs."（下着倾盆大雨）、"Hit the nail on the head."（一针见血），"a piece of cake"（小菜一碟）。

学习习语时，你会接触到许多表达方式，增强对英语的敏感度和语感。例如："Break the ice" 不仅可以用作“打破僵局”，还能帮助你理解类似的表达如 "icebreaker"（破冰者/活动）。

除此之外，使用习语可以让你的英语表达更加生动自然，贴近母语者的语言风格。例如：与其说 "I'm very tired," 不如说 "I'm worn out."（我累坏了）。熟练使用习语能让你的语言表达从“标准化”提升到“地道化”。

这本书收录的也相对较为全面，选取一页来看

![](https://image-assets.dreams.plus/images20250116191057.webp)

它收录了大约一万句常用习语，不仅可以用来查阅，它也给出了很多用法例句，也非常适合在茶余饭后，没事的时候，来消遣时随意翻上一两页（不用刻意去背），坚持一年，对自己的表达能力的提升都有极大的帮助。

不过这本书在网上我也没找到电子版，但是价格也比较便宜，30-40 左右，也可以去拼夕夕拿 9.9 包邮的影印书，非常实惠。

以上推荐的三本词典大约如此。这些主题词典都会对英语进阶有很大的帮助。当然，更重要的一条：

**注重积累**。


根据我的一段学习英语的历程，本期推荐三本好用针对非母语者的英语学习词典：牛津短语动词词典、牛津习语词典和同义词学习词典。适合进阶阶段使用。

英语学习词典推荐


The time I start writing blog is when I was enrolled in University after the College Entrance Matriculation in 2020. And I had my some thoughts over technology and programming, which I would like to put them down as fruition for studying progress.

Now the 2025 is coming, also it's my fifth year since I starting my blog.

During my teenhood when I'm a senior high school student, my parent restricted my time spending on computer so that I have less chances with my computer. At that time, I didn’t have the ability to build my own blog website. So I back then prefer using QZone, or writing my thoughts on specified notebook.

And for a long time I accrued more valuable notes about programming and thinking, they entails with C++, Java and some software theories until 2021. But unfortunately, my QZone was banned for some censorship and most of my blog was deleted, years of hard work went down the drain, its a great pity, and that's when I made a decision of building my own blog site. I can not tolerate the deteriorating cyber environment and living in censorship with trepidation.

So I learned React.js, next.js and frontend UI design, finalize this blog website as my own my blog, I have my own free writing space now.

Throughout the years topics for my blog have always been "Thoughts on Programming and Life" but in fact the point is, my blog touches more programming than life experience.

That's because, the contents on life experience would be better on social media platforms of microblog, like twitter, weibo and QZone. I expect more fallbacks from my cyber friends when I publish my content to get more emotional values, because most of my friends are online in social media platforms rather than distributed blog site. I would hard to earn this effect if I publish on blog site.

Secondly, the most of contents over life experience are fragmentation that I would write them down anytime and anywhere. For example, when you cooked culinary delicacies, got out of kitchen and want to post them in public on mood. It's convenience for everyone to open App in several seconds and type them in mobile, and publish, all in one go. Rather than write them in blog site, I must pay more focus on the text formatting after I power up computer and launch blog platform. And naturally the long blog text is not suitable for fragment writing for no convenience.

Thus I write my life experience on social media(more on [my twitter](https://x.com/codemica)) and technologies on this blog site. But the cons are also remarkable, long time fragmentation writing conduces less deep thinkings and expression, I also noticed that my expression becoming more superficial than years before.

The next steps I will take efforts to do is pick my ability of deep writing up again, especially the content over life experience, which I would put more thoughts in.


This is my fifth year since I started writing blog. After these years I noticed that I have lost more about writing.

The Fifth Anniversary for My Blog


This issue can be seen as a classic case of historical inertia combined with outdated reforms in the education system. This encapsulates the core of the problem.

Frankly, I find it difficult to tolerate the myriad justifications people offer to defend this situation. It is merely a residual consequence of the glacial pace of educational reform, yet some have framed it as "developing logical thinking" or claimed that "university isn't a training camp." Such arguments are utterly untenable.

In reality, even if computer science majors studied more mathematics instead of physics, it would be far more beneficial.

Computer science fundamentally diverges from traditional engineering disciplines such as civil engineering, mechanical engineering, electronic engineering, and chemical engineering. These traditional fields are rooted in physics, whereas computer science is deeply grounded in mathematics.

Traditional engineering disciplines primarily engage with the physical world. Their foundations lie in natural sciences, particularly physics, and they boast histories spanning decades, if not centuries. The primary focus of these disciplines is the transformation of the physical realm.

Consider this: as a mechanical engineering major, it is inconceivable to bypass the study of mechanics—how else would you design gears? If you are in precision instrumentation, knowledge of optics and electronics is indispensable for designing sensors. For chemical engineering students, quantum mechanics and thermodynamics are fundamental to understanding molecular interactions. Similarly, hydraulic engineering requires mastery of fluid mechanics.

Each traditional engineering discipline is built upon natural sciences like physics, dedicated to leveraging these principles to reshape the material world.

In stark contrast, computer science follows an entirely distinct trajectory. It is a "formal science," entirely man-made, with most of its concepts abstracted directly from mathematics.

Modern computer science theory originated with Alan Turing, whose work on computability theory employed pure mathematical constructs to define the concept of a "computer." These theoretical foundations were later implemented to create various types of computing systems.

Computer science, at its core, studies theoretical frameworks. While engineers apply these frameworks to design chips and systems, the discipline itself focuses on abstract structures and models rather than the tangible, physical world.

Formal sciences—such as mathematics, logic, and computer science—emphasize abstract, logical constructs instead of physical phenomena. They rely on deductive reasoning and logical proofs rather than empirical observation, which aligns computer science closely with mathematics.

For instance, many foundational concepts in computer science, such as Turing machines, operating system models, and the Von Neumann architecture, are mathematical abstractions. These constructs do not exist in nature; they are products of human ingenuity.

Even programming concepts such as functions, pointers, parameters, and operators—or areas like complexity analysis—are rooted in mathematical models. Algorithm design exemplifies this reliance on mathematical abstraction.

So, what justification exists for requiring computer science majors to study physics? Will they be calculating the forces involved in moving servers? Or perhaps determining the melting point of silicon to fabricate CPUs?

Let us be candid: computer science is fundamentally a repository of mathematical abstractions. This alignment with mathematics is entirely unsurprising, given the discipline's origins.

And for those who argue, "We study electronics to design circuits for CPUs," it is crucial to clarify: digital circuits and logic gates are mathematical abstractions as well. The physical implementation of chips falls under the domain of electronic engineering, not computer science. The role of computer science is to provide the models, theories, and blueprints, while other fields handle physical realization.

Furthermore, most computer science graduates today pursue careers in software development. It is unrealistic to assume they are designing CPUs.

In China, computer science was only formalized as a university discipline in the 1980s, following the reinstatement of the national college entrance exams. However, the theoretical foundations of computer science had already been established during World War II. By the time China integrated it into its educational system, we were already lagging behind Western nations by no less than half a century.

During that era, computers were a rarity in China, and expertise in teaching the subject was even scarcer. Lacking domestic models to emulate, we resorted to copying. Since physics was a staple of other STEM fields, it was incorporated into computer science curricula as well.

And yet, we remain entrenched in these antiquated practices. Despite nearly four decades, our approach to computer science education continues to stagnate. For example, certain universities still teach C++ using VC6, a tool that is unequivocally obsolete by contemporary standards.

In conclusion, the shortcomings of computer science education in China can be attributed to historical inertia and outdated reforms. Unlike traditional engineering disciplines rooted in physics, computer science is grounded in mathematics and focuses on abstract models. The inclusion of subjects like physics in the curriculum reflects a failure to adapt to the unique nature and practical demands of this field.


China's computer science education is outdated, often including irrelevant subjects like physics, due to historical and systemic inertia.

Should Computer Science Majors Learn College Physics


In the United States, the date format is uniquely distinctive and stands out globally. Unlike the European "small to large" DMY format or the East Asian "large to small" YMD format, the U.S. uses MDY. Moreover, unlike other Europeans who prefer pure numeric date formats, Americans use a semi-numeric, semi-English format: English month + numeric date + numeric year. For example, today is November 27, 2024. While a British person might write it as 27/11/2024, an American would write it as November 27, 2024!

Below is a map of date formats around the world:

![](https://image-assets.dreams.plus/images20241128101343.webp)

In the map, blue areas represent DMY, yellow areas represent YMD, red areas use a mix of DMY and MDY, green areas use a mix of DMY and YMD, and pink areas exclusively use MDY. The only country that uses this date format is the United States.

A British author once complained American written form, and wrote this on his book.
> “Most British people write the day first, followed by the month. Businesspeople and older women still insist on putting the month first.” \
> —— _Have His Carcase_, by Dorothy Leigh Sayers

I am genuinely puzzled by the logic behind the American date format. Many former British colonies or Commonwealth countries have adopted the British DMY format. But why didn't the United States, once a British colony heavily influenced by British culture, inherit the DMY format?

In fact, the American insistence on their date format has led to some amusing anecdotes. For instance, a British woman and an American man planned a date and wrote "10/12/1997" in their letters. However, they never met. Why? Because the American man understood it as October 12, while the British woman understood it as December 10!

If the world only had YMD and DMY formats, even when Asians and Westerners read each other's texts, there would be no ambiguity.

For example, dates like "2024-11-11" and "11-11-2024" can be easily understood by looking at the position of the year, allowing one to quickly determine the date format and identify the corresponding month and day. The world would be a much better place.

However, the problem lies in the strong influence of the United States in computer science and technology, which has forced their culture, including the anti-human MDY date format, onto the world, including Europe.

If you encounter an English text with a date like "11/11/2024" and cannot determine whether it was written by an American or a British person, how would you interpret it?

As a result, many English-speaking countries, including several European nations, have had to compromise: when dates are ambiguous, the month should be written in abbreviated form. For example, the British would write the above date as 11 November, 2024, or 11 Nov. 2024.

Thus, the world is now caught in a three-way battle between MDY, YMD, and DMY.

The origins of the YMD and DMY formats reflect the long-term practical needs of Eastern and Western civilizations. The reasons for these differences are varied and inconclusive, but there are two plausible explanations from cultural needs and cognitive linguistics.

The first explanation is based on cultural needs.

For a long time, the Chinese did not adopt the Western Gregorian calendar but used the era name system. Era names held significant political importance in ancient China, reflecting the will of the state and the emperor. After Emperor Wu of Han, official documents often placed the era name at the beginning to show its importance. China, being an agricultural society, developed the lunar calendar, where agricultural activities were often organized by months for planting, cultivating, and harvesting. Hence, the Chinese prioritized the year and month. Other East Asian countries like Korea, Japan, and Mongolia were also influenced by the Chinese lunar calendar.

Europeans, on the other hand, had a different approach. During the Middle Ages, Europe was deeply religious, and Europeans frequently participated in religious activities such as Sundays and sermon days. Church activities emphasized specific dates of holidays and religious events, with months being secondary information and years changing less frequently, thus placed last. For example: "Die 31 mensis Decembris anno Domini 2024" (December 31, 2024). This tradition of prioritizing the "day" has continued in many European countries, influencing their date formats.

The second explanation comes from cognitive linguistics.

From a linguistic perspective, the Western DMY format is used because European languages generally follow a logical sequence from specific to abstract, with the date as a modifier expressed first, close to the core words of month and year. In many Indo-European languages, modifiers (such as specific dates or temporal features) usually precede the main information. Western address formats also share this characteristic, starting with the house number and street, followed by the city, state, or province. This format aligns with the European linguistic habit of "modifiers being close to the modified object" and fits their cultural emphasis on logic and linear time flow. Chinese, using a large-to-small logic (year → month → day), emphasizes the progressive relationship of time, aligning with the Chinese narrative structure of "background to specifics."

In my opinion, the best date format should be one that is friendly to both humans and computers, which is the YMD format popular in East Asian countries. YMD is more intuitive for humans and most convenient for organizing documents.

While the differences between YMD and DMY can be explained from various angles, what is the logic behind the American MDY format? What is the rationale for using MDY?

After extensive online research, I have not found a concrete reason.

I strongly suspect that some American just came up with this date format on a whim.

Since most languages (like Chinese and English) are read from left to right, imagine you need to sort a pile of documents by date. When you see a date like "20241111," you can easily scan the numbers 2-0-2-4-1-1-1-1 in sequence, quickly identifying the year and month prefix, and categorize it into a "broad range" for easier sorting. However, if the date format is the British DMY, like "12072024," you need to interrupt your reading flow, start scanning from the end (4-2-0-2), then correct the order to "2-0-2-4" to identify the year, and then scan "7-0," correcting it to "0-7" to identify July. Thus, when scanning a DMY date, extracting the year and month requires changing direction four times. While manageable in the short term, it becomes a significant mental burden with large workloads, greatly increasing the chance of errors due to carelessness.

The YMD format is also very computer-friendly. YMD dates can be directly sorted in computers, as the string format "2024-07-12" is sequentially encoded, making dictionary sorting straightforward.

Imagine you have two files:

```plaintext
2024-11-12-document1.docx
2024-12-07-document2.docx
```

With the date format prefix, the former file name will always have a higher dictionary order than the latter, allowing file explorers to sort by date directly using the file names.

Numeric dates like "20240712" also make it easy to compare two dates using simple computer comparison operators like `>` and `<`, without needing additional processing.

These advantages are not present in the DMY format.

American stubbornness is not limited to date formats; their measurement standards are also a mess. For example, Fahrenheit and imperial units (miles, inches, feet, gallons, ounces, etc.). The imperial system originated during the Roman Empire in Europe and has long been a confusing mess with no fixed standards, changing over different historical periods. It wasn't until the Middle Ages that Britain standardized these units.

However, when Britain established the imperial system, there were no strict, standard measurements. For example, an inch was defined as the length of three barleycorns laid end to end, and a foot was the distance from King Edward's nose to his outstretched hand. The problem is, using barleycorns to define an inch means a thousand barleycorns could have a thousand different lengths, and using body parts for length definitions means a thousand people could have a thousand different lengths. It remains a confusing mess.

The long-standing confusion in measurements was only resolved with the development of modern French natural science, leading to the strict definition of the metric system. The metric system uses reproducible physical experiments for definitions, making it much more rigorous than the imperial system.

Thus, today, the entire world, except the United States, uses the metric system. But the U.S. remains an outlier, stubbornly clinging to the imperial tradition under the guise of "cultural heritage" and "preserving freedom and diversity." The American refusal to adopt the metric system is as irrational as the Lilliputians in _Gulliver's Travels_ arguing over which end of an egg to crack. It's truly bizarre.


In the United States, the date format is unique in the world. It is different from the European "small to large" DMY and the East Asian countries' "large to small" YMD. It is actually MDY.

Complain on American Date Format


The idea I have is that those open-source developers generating electricity out of love might have taken the wrong path. **Open source is inherently a win-win situation**.

This reminds me of the Faker.js repository deletion incident and the well-received response from [@以撒 (Isaac)](https://www.zhihu.com/people/0a8c8a41d9b99d649639ce7b1c46fda4).

[Zhihu: How do you view the Faker.js open-source author deleting all the code?](https://www.zhihu.com/question/510180628)

Many dedicated open-source project authors contribute tirelessly, creating outstanding works and adding value to the open-source community. Their spirit is admirable, and I appreciate the contributions they have made.

However, what I find hard to understand is why authors, facing financial difficulties and struggling to maintain their own quality of life, would invest a significant amount of time and energy into projects, continuing to shine even at the cost of neglecting their own livelihoods.

In the end, it seems they are only moving themselves and, in the heat of the moment, neglecting their own well-being. They even have to endure criticism from freeloaders. Watching others benefit from forking their projects while they are left with empty hands, having to deal with a pile of issues on their own, is disheartening. Seeking donations is either futile or brings in barely enough, and they are told, "If you can't afford to play in the open-source arena, then don't play at all." The effort seems disproportionate to the lack of appreciation and returns.

The correct attitude is that **open source authors must first learn to be a sophisticated egoist. All open source is for their own sake, not others. Do not be a selfless contributor to generate electricity for love.**

**First of all, don't expect direct returns from open source projects. The open source model was inherently selfish when it first came out, and its goal was to reduce its own maintenance costs.** In the previous closed-source era, the larger the engineering project, the maintenance cost and demand analysis cost increased exponentially, and the software iteration and release cycle became longer. It was also difficult to directly feed back the software usage experience to the manufacturer. During the competition period, The harder it is to survive. In addition, there are still different users in the software audience who have different opinions, so what should we do?

Therefore, the source code is directly disclosed. If anyone has their own needs or finds any bugs, they can fork it themselves and the source code can be modified as you like. You are also welcome to submit your contribution. By the way, you can also gain some fame of the project, so that different software users can be taken care of. In addition, the open source model is open, and users' needs and problems can be responded to in a timely manner and pulled into the project. Users can help you solve them, and you can relax yourself. **Source code is not an asset, but a liability. The source code will change with the needs, exposing many potential problems, all of which require a lot of cost to maintain. Open source is a way to share liabilities and transfer costs to users, which is self-interested.** What if you want to make money with my project? No problem, MIT, Apache and other protocols have agreed: you are responsible for your own choices, you can make money, and the source code can be modified, but if you get in trouble, don't come to me.

So what about personal projects like faker.js and core.js? How do individuals make small projects big? Many open source works were originally written on a whim to solve and realize an idea in work or study. Linux is an example. The author originally wrote the project to learn about operating systems. If the idea is good, with promotion and fame gradually accumulated, more and more people will participate to help contribute Contribution, and the project will become bigger. Now that others have Contribution, it also incorporates ideas from many different users, **Then you actually have no natural obligation to protect yourself.** Because when you originally wrote it, it was for your own use, not to cater to users. **So since it is open source, users also have the obligation to maintain it after obtaining the rights to the source code, and the problems should be solved among them.**

In other words, I have tried my best on the project, and I have given you the source code and profit rights. If you have any ideas or requirements, you can fork and contribute, but if you encounter any problems, you can solve them yourself and do your best. Everyone can get what they need. **I just made my source code public. You can use it if you find it useful. If it doesn't, you can use it. If you like it, don't use it. Don't give me any trouble. After I open sourced it, it was you who begged me to use it, not me who begged you to use it.**

**Ok, this kind of "refined egoism" is the correct path for open source.** If you really want to use open source to gain fame and fortune, then it's not a big deal, and there's no shame in clearly stating the price.

**Remember that when doing open source, the important thing is for yourself, not for others, so don't wrong yourself.**


Remember: when doing open source, the important thing is for yourself, not for others, so don't wrong yourself.

Should I Do Open Source Selflessly?


Today, WeChat once again flooded my Moments with mini-programs, the previously rumored application-type.

However, this piece won't delve into the technical details of mini-programs, nor speculate (because we know very well...).

It also won't discuss what impact mini-programs will have on the Chinese Internet (product managers will discuss that...).

Let's talk about the Web, the Web.

When we commonly refer to the Web, we are actually abbreviating World Wide Web to "the Web."

Similar to H5, this term is an abbreviation of an abbreviation, so concise that in the end, nobody knows what it originally meant.

Don't say that the common people in China can't distinguish between the World Wide Web and the Internet; the same goes for ordinary Americans who can't differentiate between the Web and the Internet.

Many practitioners who don't seek in-depth understanding are not much better off. The term "Web" is consistently translated into Chinese technical articles in a way that leaves readers perplexed.

In the Chinese-speaking world, one of the clearest and most attentive explanations of this matter belongs to [@不鳥萬如一](https://www.zhihu.com/people/6bec872206d9884cd9535841b6a1f510).

For example, in his article [One Day World: WeChat does not "manage" external links, because in practice, WeChat Official Accounts do not allow any external links - 不鳥萬通讯 - Zhihu Column](https://zhuanlan.zhihu.com/p/20747514), he writes:

> The Chinese world has always confused [Internet](https://en.wikipedia.org/wiki/Internet)(internet) and [World Wide Web](https://en.wikipedia.org/wiki/World_Wide_Web)(web). The "open spirit of the Internet" that people remember so much is actually the open spirit of the World Wide Web. The openness of the World Wide Web is mainly reflected in one point: **Any article on the World Wide Web can be linked to each other at will through the URL** . If I want to introduce the website UbuWeb in the article, I can directly add its URL ubu.com to the six letters [UbuWeb](https://ubu.com/). You may think this is nonsense, but you can't do that in articles on WeChat public accounts; you can only add links within the WeChat ecosystem, such as [this](https://weixin.qq.com/cgi-bin/readtemplate%3Ft%3Dweixin_external_links_content_management_specification) (that is, the link to the above "Specification")

So Ruyi uninstalled WeChat ([Farewell to the world of WeChat for a day](https://blog.yitianshijie.net/2016/02/21/byebye-wechat/)) and wrote: [WeChat - the de facto local area network](https://blog.yitianshijie.net/2015/11/16/wechat-de-facto-lan/) , well, as someone who is increasingly hardcore about Open Web, I agree.

Ruyi may care most about articles, but what I care about more is applications, Web Apps.

The so-called Web App is an evolution of the Web: from providing text information (hypertext) to multimedia (hypermedia) to providing software application services. The translation of hard core is probably "World Wide Web-based applications", such as Youtube, Twitter, Medium, Github, etc. that you use in your web browser. **They can still be linked to each other at will through website addresses (URL), follow Web is an open standard, and you can use this service on almost any platform with a browser, so Web App is also open.**

If you've heard of Google's Progressive Web Apps, it actually stands for Progressive Open Web Apps, but that's just too long and wordy.

After all, the concept of the Web should include Open.

(The purpose of this article is not to advocate PWA, but if you are interested in PWA, you are welcome to read: [Next Generation Web Application Model — Progressive Web App](https://zhuanlan.zhihu.com/p/25167289))

If Hybrid architecture is just a concession to Web idealism, then the emergence of React Native has undoubtedly caused the collapse of some people's beliefs, followed by Weex, and then maybe WeChat as you guessed it.

Seeing that the method of "developing with the Web paradigm for Native platforms" is becoming more and more popular, although it seems that the people who benefit are Web front-end practitioners, I don't know whether I should be happy or not.

I'm not saying they are the “wrong technical direction”, from a pragmatic perspective they are great and solve problems.

**However, no matter how much they look like the Web, they are not part of the Open Web platform.**

RN/Weex doesn't have URLs at all (don't get me started on Universal Links or App Links, URLs and URIs are different)

Starting from the JS-SDK, WeChat has been a closed ecosystem.

Although this momentum originated from Facebook, it is more likely to spread wildly in China.

There are many people in the English world who are sensitive/hardcore about this kind of thing, such as Jeremy Keith, who wrote [Regressive Web Apps](https://adactio.com/journal/10708). Because PWA is not URL-friendly enough, it has nothing to do with Chrome development. The boss Alex had a quarrel, and Alex said anxiously:

> so, your choices are to think that I have a secret plan to kill URLs, or conclude I'm still Team Web.

You know, the reason Alex took Chrome to develop PWA was because he didn't like Hybrid destroying the Open Web.

If Twitter/FB is like WeChat and doesn't allow links to be linked casually, you may have to abandon Twitter, and then write a Byebye Twitter/FB article in anger like Ruyi.

However, what is being advocated every day in China is that XX helps the HTML5 ecosystem, but most of the time these so-called "HTML5 ecosystems" are contrary to the Web ecosystem, and there is no judgment.

I started to get a little incoherent.

In this Chinese world where HTML5 and the Web are extremely misused, I don't know how to cry out.

All I know is that when the Web can only survive as Native's "Markup Language", the Web will cease to exist.

When no one follows the Web standards and creates their own, the so-called cross-platform features of the Web disappear.

I've written about it before, and Chrome Product Leader Rahul also said it at I/O:

**The Web's Dicoverable, Linkable, Low Friction, Broad Reach, etc., are not the essence of the Web. The essence of the Web is Open and Decentralized. This is the original intention of the World Wide Web (WWW). This is the prerequisite for all these characteristics to be established.**

The belief in Open Web has brought browser manufacturers back together, and they are asking you:

**Hey, can we make the web great again?**

> Author : Xuan Huang \
> Origin Link: <https://huangxuan.me/2016/09/22/the-open-web/>


```ts
sss
```


The essence of the Web is Open and Decentralized. This is the original intention of the World Wide Web (WWW), and this is the prerequisite for all these features to be established.

原点日志

THOUGHTS