一年三个月不上班，平摊相当于 1/4 的时间不工作。那我宁愿选择分到每一周少上一天，每个月再额外少上一天，不舒服多了？

用缩写就没有这个烦恼，比如 PS 、IJ 、CL

有些有开屏广告的 app 可能有 bug （或者是 feature ），回桌面再点进去也会放开屏广告，有时候就会造成被杀的效果

iCloud 备忘录

@agagega
typo: 室内

说室外是因为在沈阳吗😂

面板固定不牢固这个问题，我两年前买的 Ultrafine 也有，感觉做工就这样吧

Slack 在国内可以正常访问，而且可定制性更强些，但多了要收费，替代品就是 TG

@haruhi
最近在用一台 M1 Pro ，也遇到这个问题了…

至于说「为什么不用 Qt 做，为什么不用 xxx 做」这种问题，Qt 当然有许可证问题，但更大的问题其实是——客户端这块蛋糕早就被内卷王中王的前端们虎视眈眈很久了，他们心中原生技术就是应该扔进垃圾桶的东西，每个系统都应该自带 NodeJS 运行时重写一切东西； Electron 、uniapp 、RN 都是摧毁「旧秩序」的利器，当然要大力推广。

@marcong95
手机端这个逻辑是这样的：网页端不涉及安装，在任何一台电脑上都能登录，所以大家喜欢网页端；手机屏幕小，性能相对也差点，所以网页版体验明显不如原生 App ；现在很多公司在手机上一方面拒绝网页端（失去了前面的优点），又本质上搞了个各种套 Web 组件的 App （后面体验好的优点也没有了）。

桌面这里也是相似的：大家能接受网页版，反感没有网页版，非要装软件，结果打开发现是网页套壳的产品；但桌面端有一个问题，它运行的软件更多是生产力属性而不是移动端的消费属性，交互比移动端更复杂，而且可能同时运行很多应用，在这种情况下 Electron 的劣势就体现了出来。

这就造成了一个奇怪的现象：以阅读为主，操作相对简单的网站（如新闻、社区、购物），反而要你下 App 才能用；工具类，对性能有要求的软件，打开都是 Web 套壳。

然而 Swift 的理念之一还是 keep things explicit ，花样多不代表坑就多，只能说这几年确实用力猛了点。

@jackbrother
Swift 的字符串操作繁琐是因为字符串涉及到不定长编码，本来就该这样，Rust 的字符串也不能直接用下标访问字符。

就是台比较贵的电脑，喜欢就买，哪有那么多必要不必要的。我买得比较早，还记得当年快递还没到，晚上觉都睡不着。现在看来最大的遗憾还是十年前没有买一台 iPhone 4 ，那时候真是惊艳啊。

往小了说这是 Swift core team 的问题，往大了说这是苹果对开发者社区的态度问题…虽然 Swift 确实是开源的，但社区对它的影响力极其有限，而且 SwiftUI 相关的语法强推一波做得也不好看。

苹果不像微软盘子这么大，能让 C#无所不能。Swift 在官方支持里就只能用来开发 Apple 平台的软件，其他 Swift on Server 的项目都没有官方支持。本来 Swift 是个很好的语言，只能说成也苹果败也苹果了。

今天看来，Mac 转 ARM ，OS X 改名并增加大版本，APFS 都来了…

Can OneDrive be stored on an external drive? How does pinning a file work when I use an external drive? Are there multiple copies of my data?

> I've seen several threads on this topic but let me clarify with an emphatic yes: external drives are fully supported without any difference in the end-user experience.
>
> That said, external drive support as it exists today is implemented differently than it was in the past because of how File Provider works. Very few users are running this configuration, but for them, it's an important scenario because often their content won't fit on the home drive. File Provider doesn't support creating the sync root on any drive except for the home drive. So, we had to find a way to support external drives within these constraints.
>
> When you choose a path to sync your OneDrive, we use that path to derive where we put your OneDrive cache path. If that path is on an external drive, we'll put the cache path there. We wanted to honor this preference because the cache path is where your pinned content is stored, as I'll explain below.
>
> When your cache path is placed on an external drive, OneDrive tries to minimize the number of copies of your data it makes, and in most cases, only one copy will exist, usually in the sync root. If your home drive runs into disk pressure, the operating system will evict (dataless) files from the sync root, but they can always be obtained again from the cloud if needed. In some cases a file might exist in both places for a short time, but over time we will ship fixes that will optimize this further.
>
> Pinned files on an external drive have behavior quirks that are worth understanding. If you pin a file, it will download to the cache path only, and will show both the checkbox and "not downloaded" state icons. This is because the file is dataless in the sync root but exists as a full file in the cache path. However, if you pin a file and also double-click it to open it, we will bring it into your sync root, so there are two copies, one in each location. Note that files brought into your sync root in this manner can still be evicted by macOS when it encounters disk pressure, but when this happens, only the file in the sync root is evicted. We still keep the data in your cache path, so you can always get to the file's content, even if you are offline.

看起来是可以的，不过我还没试。

Flexcil ？

iTerm 真不戳