请问HN：我该如何逃离操作系统切换成本的地狱？
我目前陷入了我的iPhone和一系列新笔记本电脑之间的循环。我相信这个流程图对其他人来说也很熟悉：你从一台MacBook开始，它坏了，现在你不断地重新配置你的笔记本电脑，以实现某种生产力并与手机同步。
我原以为可以通过NixOS配置来解决这个问题，想法是我的机器配置是一个git仓库，如果笔记本电脑坏了，我可以简单地在新机器上复制它。
实际上，我花在不同窗口、iPhone和新的Linux安装之间来回切换未保存密码的时间，远远超过了其他计算机活动。
像大多数消费者用户一样，我从来没有真正理解iCloud是如何工作的，更不用说OneDrive了，通常我还在努力阻止它们自动执行一些让我困惑的操作。我目前的状态是试图在两台Windows机器之间设置syncthing，却因为OneDrive的自动操作搞得桌面一团糟，我希望这里有人能提供第三方视角，帮助我停止在配置上浪费时间。
我最后的局部最优状态是“iPhone / MacBook，一切都能正常工作，即使iCloud有些奇怪，我也能进行开发工作，通常我的手机和笔记本电脑是一样的”。我希望能说“x手机和x笔记本电脑，一切都能正常工作，当某样东西坏掉或丢失时，我可以神奇地在新设备上恢复软件设置，而不会丢失文件或已安装和配置的软件数据”。
这真的能做到吗？我是在对着风车发呆吗？似乎每个大公司都在试图在硬件上实现这种条件下的供应商锁定，但即使假设你这样做了，你也只能实现文件层面的数据保护，每台新机器仍然需要另一个新的vsCode安装/配置步骤，其他应用程序也是如此。
我明白硬件生命周期和供应商锁定是存在且将永远存在的，但我觉得应该被抛弃的观念是，软件配置在硬件生命周期中无法无痛地迁移。
查看原文
I am currently stuck in a loop between my iPhone, and a series of new laptops. I'm sure the flowchart is familiar to others: you start with a macbook, it breaks, and now you're constantly reconfiguring your laptop to achieve some version of productivity and sync with your phone.<p>I thought I'd be able to solve this with a NixOS config, the thinking being that my machine config is a git repo, and if/when a laptop breaks I can simply duplicate it on the new machine.<p>What's actually happening is that I'm spending more time wrestling unsaved passwords across windows, iPhone, and new Linux installs than any other computer activity.<p>Like most consumer users, I never really understood how iCloud worked, much less OneDrive, and more often than not am wrestling them to not do things automatically that confuse me. My current state is trying to setup syncthing across two windows machines, only to have an automatic OneDrive action create a mess of my desktop, and I'm hoping someone here will have a 3rd person view and help me stop wasting time on configuration.<p>My last local maxima was "iPhone / MacBook, everything just works even if iCloud is weird I can do dev work and generally my phone and laptop are the same". I'd like to be able to say "x phone and x laptop, everything just works and when something gets broken/lost I can magically restore the software setup on a new device to replace it without losing data as in files or data as in installed and configured software"<p>Can this even be done? Am I tilting at windmills? It seems like every major company is trying to achieve this under the condition that you have vendor lock in at the hardware, but even assuming you do that you will only achieve data protection as in files, and every new machine will need another new vsCode install/config step, as will every other application.<p>I get that there is and always will be both a hardware lifecycle and vendor lock-in, what I feel should be left in the past is the idea that software configuration cannot be moved across the hardware lifecycle painlessly.