ClipEgg:我们将复制与囤积混淆了
复制功能存在问题。这种情况已经持续了40年。
当你复制某样东西时,你实际上想要什么?
你想要的是对某个事物的引用。是一种表达“这个,这里,我想在别的地方使用这个”的方式。
而你得到的是什么?
你得到的是一切。图像、格式、字体声明、元数据、整个DOM子树。就像一辆装满家具的6MB货车,而你所需要的只是地址。
我们把复制和囤积搞混了。
而且这个数字令人震惊。
每天有400亿次复制操作发生。平均每次的负载是100KB的没人需要的东西。这相当于在RAM中有4个艾克萨字节的数据,在设备之间同步,并被粘贴到按令牌收费的AI工具中。
能源成本:每年3300万吨二氧化碳。相当于700万辆汽车的排放。仅仅是为了剪贴板格式。
旧的复制方式:这里是所有内容。囤积它。
新的复制方式:这里是一个引用。根据需要获取你所需的内容,前提是你被允许。
所以我构建了答案。
一个蛋。200字节。一个索取凭证,而不是货物。
接收者根据上下文将其打开。粘贴到终端?纯文本。粘贴到Figma?获取完整资产。粘贴到不该有访问权限的系统?什么都没有。
复制 = 糖霜。
剪切 = 蛋糕。
查看效果:https://daaaave-atx.github.io/clipe96
规格:https://github.com/daaaave-ATX/clipe96
查看原文
Copy is broken. It has been for 40 years.<p>When you copy something, what do you actually want?<p>A reference to a thing. A way to say "this, here, I want to use this somewhere else."<p>What do you get instead?<p>Everything. The image. The formatting. The font declarations. The metadata. The entire DOM subtree. A 6MB cargo truck full of furniture when all you needed was the address.<p>We confused copying with hoarding.<p>And the math is insane.<p>40 billion copy operations happen every day. Average payload: 100KB of stuff nobody asked for. That's 4 exabytes sitting in RAM, syncing across devices, getting pasted into AI tools that charge per token.<p>The energy cost: 33 million tons of CO2 annually. Seven million cars worth. For clipboard formatting.<p>Old copy: Here's everything. Hoard it.<p>New copy: Here's a reference. Fetch what you need, when you need it, if you're allowed.<p>So I built the answer.<p>An egg. 200 bytes. A claim ticket, not cargo.<p>The receiver cracks it open based on context. Paste into a terminal? Plain text. Paste into Figma? Hydrate the full asset. Paste into a system that shouldn't have access? Nothing.<p>Copy = Frosting.
Cut = Cake.<p>See it work: https://daaaave-atx.github.io/clipe96<p>Spec: https://github.com/daaaave-ATX/clipe96