<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>每日HackerNews</title><link></link><description></description>
            <item>
                <title>还有其他人收到含糊其辞的 GitHub 勒索通知吗？ Anyone else get a vague GitHub shakedown notice?</title>
                <link>https://lists.osgeo.org/pipermail/qgis-developer/2026-July/068430.html</link>
                <guid>https://lists.osgeo.org/pipermail/qgis-developer/2026-July/068430.html</guid>
                <pubDate>Fri, 10 Jul 2026 18:03:23 +0000</pubDate>
                <description><![CDATA[<p>QGIS 开发邮件列表的贡献者 Greg Troxel 最近收到 GitHub 的通知，称其“代码质量”功能将于 2026 年 7 月 20 日正式上线。该邮件警告将引入新的“按提交者计费”模式及人工智能使用费用。

Troxel 对此感到担忧，因为他并未订阅付费方案，没有加入 GitHub 赞助者计划（GitHub Sponsors），且已退出了不再活跃的组织。尽管如此，他仍收到了这份声称他参与了 GitHub 赞助者计划的通知，他对此表示否认。他怀疑这封邮件可能是一个错误，或者是 GitHub 试图向未主动使用付费功能的用户收取费用的手段。

他正在向 QGIS 社区求助，以确定其他人是否收到了类似的通知，QGIS 项目的配置是否可能触发了针对贡献者的这些通知，以及仓库协作者是否面临意外账单的风险。</p><p>Greg Troxel, a contributor to the QGIS-Developer mailing list, recently received a notification from GitHub regarding the transition of its "Code Quality" feature to general availability on July 20, 2026. The email warns of new "per-committer" and AI-usage fees.

Troxel is concerned because he does not use paid plans, is not enrolled in GitHub Sponsors, and has removed himself from defunct organizations. Despite this, he received the notice, which claims he is part of GitHub Sponsors—an assertion he disputes. He suspects the email may be an error or an underhanded attempt to generate revenue from users not actively utilizing paid features.

He is reaching out to the QGIS community to determine if others received similar notices, whether the QGIS project’s configuration might have triggered these notifications for contributors, and if there is a risk of surprise billing for repository collaborators.</p>]]></description>
            </item>
            
            <item>
                <title>让我们重新发明滚轮 Let's Reinvent the Scroll Wheel</title>
                <link>https://scrollpods.app/blog/lets-reinvent-the-scroll-wheel</link>
                <guid>https://scrollpods.app/blog/lets-reinvent-the-scroll-wheel</guid>
                <pubDate>Fri, 10 Jul 2026 17:33:34 +0000</pubDate>
                <description><![CDATA[<p>你需要启用 JavaScript 才能运行此应用。</p><p>You need to enable JavaScript to run this app.
</p>]]></description>
            </item>
            
            <item>
                <title>AMD Ryzen AI Halo 上手体验 Hands-On with the AMD Ryzen AI Halo</title>
                <link>https://www.microcenter.com/site/mc-news/article/amd-ryzen-ai-halo-review.aspx</link>
                <guid>https://www.microcenter.com/site/mc-news/article/amd-ryzen-ai-halo-review.aspx</guid>
                <pubDate>Fri, 10 Jul 2026 17:32:56 +0000</pubDate>
                <description><![CDATA[<p>请启用 JavaScript 和 Cookie 以继续。</p><p>Enable JavaScript and cookies to continue</p>]]></description>
            </item>
            
            <item>
                <title>```Show HN：用 AI 重组我 2001 年的大学乐队``` Show HN: Reviving my 2001 college band with AI</title>
                <link>https://www.fadingmaize.com</link>
                <guid>https://www.fadingmaize.com</guid>
                <pubDate>Fri, 10 Jul 2026 17:31:21 +0000</pubDate>
                <description><![CDATA[<p>歌曲与人声
活跃的创意之声
原声吉他、主唱、词曲作者
查理（查克）·萨波纳拉
Fading Maize 作品集背后的原创词曲作者及主唱。
此次复兴以查理的原创性为核心，同时由他负责对新版本提供反馈、审批及创意微调。</p><p>Songs and voiceActive creative voiceAcoustic guitar, lead vocals, songwriterCharlie (Chuck)SaponaraOriginal songwriter and lead voice behind the Fading Maize catalog.The revival keeps Charlie's authorship at the center while he provides feedback, approvals, and creative tweaks for the new versions.</p>]]></description>
            </item>
            
            <item>
                <title>《终结者2》的科技：口述历史（2017） The tech of 'Terminator 2' – an oral history (2017)</title>
                <link>https://vfxblog.com/2017/08/23/the-tech-of-terminator-2-an-oral-history/</link>
                <guid>https://vfxblog.com/2017/08/23/the-tech-of-terminator-2-an-oral-history/</guid>
                <pubDate>Fri, 10 Jul 2026 17:30:29 +0000</pubDate>
                <description><![CDATA[<p>这段口述历史探讨了詹姆斯·卡梅隆执导的《终结者2：审判日》（1991年）幕后开创性的视觉特效制作。当时工业光魔（ILM）的计算机图形部门尚处于起步阶段，团队既要面对研发新技术的挑战，又要克服硬件性能的局限。

在视觉特效总监丹尼斯·穆伦的带领下，约40名艺术家组成的团队开创了多种技术，例如用于角色拼接的“全身贴图”（Body Sock）、为“多重合金”T-1000量身定制的反射着色器，以及先进的变形软件。由于当时的商业动画工具非常简陋，团队成员既是艺术家也是软件开发者，他们常需即兴编写C-shell脚本和“胶水代码”，以实现卡梅隆雄心勃勃的视觉构想。

团队在昂贵且高负荷的硬件上长时间工作，依靠“亲力亲为”的精神，通过手动制作复杂的变形动画，并在缺乏现代软件辅助的情况下解决了诸多技术难题。最终呈现的特效——如液态金属转换和T-1000的终结片段——在影史上至今仍是传奇。该项目不仅巩固了工业光魔作为数字先驱的地位，也为许多艺术家开启了职业生涯，他们后来都成为了定义视觉特效行业未来的中坚力量。</p><p>This oral history explores the groundbreaking visual effects work behind James Cameron’s *Terminator 2: Judgment Day* (1991). As ILM’s computer graphics department was still in its infancy, the team faced the dual challenge of inventing new technologies while working with limited hardware.

Led by visual effects supervisor Dennis Muren, the crew of about 40 artists pioneered techniques like "Body Sock" for character stitching, custom reflection shaders for the "poly alloy" T-1000, and advanced morphing software. Because commercial animation tools were rudimentary, the team functioned as both artists and software developers, often writing custom C-shell scripts and "glue code" on the fly to meet Cameron’s ambitious vision.

Working long hours on expensive, processing-intensive hardware, the team relied on a "DIY" spirit, hand-animating complex transformations and solving technical problems without the benefit of modern software. The resulting effects—such as the liquid metal transitions and the T-1000’s death sequence—remain legendary in cinema history. This project not only cemented ILM’s status as a digital pioneer but also launched the careers of many artists who would go on to define the future of the visual effects industry.</p>]]></description>
            </item>
            
            <item>
                <title>《JEPA 注解版》 The Annotated JEPA</title>
                <link>https://elonlit.com/scrivings/the-annotated-jepa/</link>
                <guid>https://elonlit.com/scrivings/the-annotated-jepa/</guid>
                <pubDate>Fri, 10 Jul 2026 17:04:36 +0000</pubDate>
                <description><![CDATA[<p>联合嵌入预测架构（JEPAs）代表了自监督学习从像素级重构向抽象表示空间预测的范式转移。与将计算资源浪费在无关噪声上的生成模型不同，JEPAs 通过强制模型利用可见上下文预测被遮盖区域，从而捕捉诸如物体身份和物理动态等语义结构。

核心架构包括：
*   **I-JEPA**：使用上下文编码器和目标编码器（通过指数移动平均更新）来预测缺失的图像块，在无需对比负样本的情况下避免了模型坍塌。
*   **V-JEPA / V-JEPA 2**：将该方法扩展至视频领域。模型学习潜在的时空动态，不仅能实现分类，还能为具身智能体提供目标导向的规划能力。
*   **LeJEPA**：一种改进方法，用“草图各向同性高斯正则化”取代了启发式稳定性方法，以强化最佳嵌入分布。

在概念上，JEPAs 是基于能量的模型（EBMs）。通过在压缩的潜在空间内最小化预测误差，它们充当了模拟物理现实的“世界模型”。以 Yann LeCun 为代表的支持者认为，这种方法比自回归标记预测更适合物理世界的智能，因为它要求模型内化世界的底层约束和物理定律，而非仅仅学习人类的语言模式。</p><p>Joint Embedding Predictive Architectures (JEPAs) represent a shift in self-supervised learning from pixel-level reconstruction to prediction within abstract representation space. Unlike generative models that waste capacity on irrelevant noise, JEPAs capture semantic structures—such as object identity and physical dynamics—by forcing a model to predict masked regions from visible context.

Key architectures include:
*   **I-JEPA:** Uses a context encoder and a target encoder (updated via exponential moving average) to predict missing image patches, avoiding collapse without needing contrastive negatives.
*   **V-JEPA/V-JEPA 2:** Extends this to video, where the model learns latent spatiotemporal dynamics, enabling not just classification but also goal-directed planning for embodied agents.
*   **LeJEPA:** A refined approach that replaces heuristic stability methods with "Sketched Isotropic Gaussian Regularization" to enforce an optimal embedding distribution.

Conceptually, JEPAs function as Energy-Based Models (EBMs). By minimizing prediction error in a compressed latent space, they serve as "world models" that simulate physical reality. Proponents, such as Yann LeCun, argue this approach is more suitable for physical-world intelligence than autoregressive token prediction, as it requires the model to internalize the underlying constraints and physical laws of the world rather than just human linguistic patterns.</p>]]></description>
            </item>
            
            <item>
                <title>计算：一种通用且基础的概念 Computation as a Universal and Fundamental Concept</title>
                <link>https://ergo.org/courses/computation-as-a-universal-and-fundamental-concept</link>
                <guid>https://ergo.org/courses/computation-as-a-universal-and-fundamental-concept</guid>
                <pubDate>Fri, 10 Jul 2026 17:02:50 +0000</pubDate>
                <description><![CDATA[<p>蒂姆·拉夫加登（Tim Roughgarden）对计算机科学的探索始于艾伦·图灵（Alan Turing）1936 年的发现：某些问题从根本上是任何算法都无法解决的，例如“停机问题”。在超越理论极限之后，拉夫加登研究了为什么有些可解问题很容易解决，而另一些则极其困难。

他强调了算法捷径（如 Dijkstra 算法）的威力，这些捷径使计算机无需通过暴力搜索即可找到高效的解决方案。然而，这种效率在遇到诸如“旅行商问题”（TSP）等难题时会遇到瓶颈。这些难题构成了“NP完全”问题的基础，该框架揭示了成千上万种不同的任务是相互关联的；如果其中一个能被高效解决，那么所有的任务都能被解决。

这引出了计算机科学中最重要的未解之谜——“P 对 NP”问题。通过将历史数学探究与现代计算理论相结合，拉夫加登阐述了这些局限性如何影响从密码学到人工智能的方方面面。该课程专为大众设计，揭示了计算机能实现——以及很可能永远无法实现——的深刻边界。</p><p>Tim Roughgarden’s exploration of computer science begins with Alan Turing’s 1936 discovery that some problems are fundamentally unsolvable by any algorithm, such as the "halting problem." Moving beyond theoretical limits, Roughgarden investigates why some solvable problems are easy while others remain stubbornly difficult.

He highlights the power of algorithmic shortcuts—like Dijkstra’s algorithm—which allow computers to find efficient solutions without brute-force searching. However, this efficiency hits a wall with problems like the Traveling Salesman Problem (TSP). These difficult puzzles form the basis of "NP-completeness," a framework revealing that thousands of diverse tasks are linked; if one is solved efficiently, they all are.

This leads to the "P versus NP" question, the most significant unsolved mystery in computer science. By bridging historical mathematical inquiry with modern computational theory, Roughgarden illustrates how these constraints shape everything from cryptography to artificial intelligence. Designed for a general audience, the course demystifies the profound boundaries of what computers can—and likely never will—achieve.</p>]]></description>
            </item>
            
            <item>
                <title>蜗牛牙齿超越蜘蛛丝，成为自然界最强材料 Snails' Teeth Beats Spider Silk as Nature's Strongest Material</title>
                <link>https://www.smithsonianmag.com/smart-news/spider-silk-loses-top-spot-natures-strongest-material-snails-teeth-180954346/</link>
                <guid>https://www.smithsonianmag.com/smart-news/spider-silk-loses-top-spot-natures-strongest-material-snails-teeth-180954346/</guid>
                <pubDate>Fri, 10 Jul 2026 17:01:03 +0000</pubDate>
                <description><![CDATA[<p>朴茨茅斯大学的研究人员发现，帽贝（一种以刮食岩石上的藻类为食的海生螺类）的牙齿是地球上最坚硬的天然材料。

这些牙齿由嵌入蛋白质基质中的含铁针铁矿纳米纤维组成，其抗拉强度远高于蜘蛛丝，并可与优质碳纤维相媲美。首席研究员阿萨·巴伯（Asa Barber）表示，这种材料的强度极其惊人，理论上一根纤维就能支撑数千磅的重量。

尽管如蓝丝黛尔石或纤锌矿型氮化硼等材料以超高硬度（抗刮擦或抗压痕能力）著称，但帽贝的牙齿在天然抗拉强度（抗拉伸断裂能力）方面实现了突破。科学家们目前正将这些牙齿的结构成分视为潜在的蓝图，以开发下一代工程材料和机械。</p><p>Researchers from the University of Portsmouth have discovered that the teeth of limpets—marine snails known for their ability to scrape rock—are the strongest natural material on Earth. 

Composed of iron-containing goethite nanofibers embedded in a protein matrix, these teeth exhibit a tensile strength significantly greater than spider silk and comparable to high-quality carbon fibers. According to lead researcher Asa Barber, the material’s strength is so immense that a single strand could theoretically support thousands of pounds.

While other materials like lonsdaleite or wurtzite boron nitrate are known for superior hardness (the ability to resist scratching or indentation), the limpet’s teeth represent a breakthrough in natural tensile strength (the ability to resist pulling apart). Scientists are now looking to the structural composition of these teeth as a potential blueprint for developing next-generation engineering materials and machines.</p>]]></description>
            </item>
            
            <item>
                <title>另类时钟设计与时间系统 Alternate Clock Designs and Time Systems</title>
                <link>https://serialc.github.io/altClocks/</link>
                <guid>https://serialc.github.io/altClocks/</guid>
                <pubDate>Fri, 10 Jul 2026 16:33:05 +0000</pubDate>
                <description><![CDATA[<p>这项探索质疑了我们传统计时系统的效率，该系统依赖于 24 小时、60 分钟和 60 秒的任意基数。批评者认为，这种结构前后矛盾且难以计算，与公制系统精简的逻辑形成了鲜明对比。

作者提出了几种替代时钟设计，以测试实现更直观方案的可能性：

*   **十进制（Base 10）时钟：** 将一天分为 10 小时，每小时 100 分钟，通过简单的十进制进位简化了换算。
*   **24 小时制时钟：** 一种经典的变体，通过让时针每天旋转一圈来消除上午/下午的混淆。
*   **其他进制：** 实验性设计包括供爱好者使用的二进制（Base 2）时钟、十六进制（Base 16）时钟，以及受罗盘导航启发、按 36 小时划分的“度数”时钟。

虽然这些系统突显了我们当前时钟在数学上的局限性，但也强调了传统计时方式在文化和历史上的分量。归根结底，作者邀请读者构想一种衡量我们日常生活的更合乎逻辑的框架，从而证明时间既是一种自然常数，也是一种设计选择。</p><p>This exploration questions the efficiency of our traditional timekeeping system, which relies on an arbitrary base of 24 hours, 60 minutes, and 60 seconds. Critics argue this structure is inconsistent and difficult to calculate, contrasting sharply with the streamlined logic of the metric system.

The author presents several alternative clock designs to test the potential for a more intuitive approach:

*   **Decimal (Base 10) Clock:** Divides the day into 10 hours of 100 minutes, simplifying conversions to a basic decimal shift.
*   **24-Hour Clock:** A classic variation that removes AM/PM confusion by allowing the hand to complete a single rotation per day.
*   **Alternative Bases:** Experimental designs include binary clocks (base 2) for enthusiasts, hexadecimal (base 16) clocks, and a 36-hour "degree" clock inspired by compass navigation.

While these systems highlight the mathematical limitations of our current clocks, they also underscore the cultural and historical weight of traditional timekeeping. Ultimately, the author invites readers to imagine a more logical framework for measuring our days, proving that time is as much a design choice as it is a natural constant.</p>]]></description>
            </item>
            
            <item>
                <title>QuadRF 可以探测无人机并穿墙监测 WiFi。 QuadRF can spot drones and see WiFi through my wall</title>
                <link>https://www.jeffgeerling.com/blog/2026/quadrf-can-spot-drones-and-see-wifi-through-my-wall/</link>
                <guid>https://www.jeffgeerling.com/blog/2026/quadrf-can-spot-drones-and-see-wifi-through-my-wall/</guid>
                <pubDate>Fri, 10 Jul 2026 16:30:09 +0000</pubDate>
                <description><![CDATA[<p>QuadRF 是一款紧凑型手持式相控阵无线电设备，基于树莓派 5 (Raspberry Pi 5) 和 FPGA 构建，专为 4.9–6 GHz 频段内的高级信号处理和波束成形而设计。该设备利用树莓派的 MIPI 通道进行高带宽数据传输，实现了低延迟、高速的射频流传输，从而具备了无人机追踪和穿墙可视化 WiFi 信号等功能。

该项目由前 SpaceX 工程师马丁·麦考密克 (Martin McCormick) 开发，旨在让复杂的射频分析不再局限于政府级工具。虽然当前原型的用户界面仍有待完善，但该设备功能强大，包括一个可实时映射射频信号的定制增强现实 (AR) 可视化工具。

尽管最初是作为更大规模月球级天线阵列项目的一部分构思的，但手持式 QuadRF 已展现出作为业余爱好者和专业人士通用工具的巨大潜力。该设备通过 Crowd Supply 活动发布，提供了一种创新且开源的射频可视化方案。虽然预生产软件仍需优化，但其性能——尤其是追踪无人机等设备的能力——表明高端射频工程正变得日益便携和普及。</p><p>The QuadRF is a compact, handheld phased-array radio built around a Raspberry Pi 5 and an FPGA, designed for advanced signal processing and beamforming within the 4.9–6 GHz range. By utilizing the Pi’s MIPI lanes for high-bandwidth data transfer, the device achieves low-latency, high-speed RF streaming, enabling capabilities like drone tracking and visualizing WiFi signals through walls.

Developed by Martin McCormick, a former SpaceX engineer, the project aims to make sophisticated RF analysis accessible beyond government-grade tools. While the user interface for the current prototype remains a bit rough, the device features impressive functionality, including a custom Augmented Reality (AR) visualizer that maps RF signals in real-time. 

Though originally conceived as part of a larger Moon-scale antenna array project, the handheld QuadRF is already showing great potential as a versatile tool for hobbyists and professionals alike. Available via a Crowd Supply campaign, it offers an innovative, open-source approach to RF visibility. While pre-production software requires refinement, its performance—particularly its ability to track devices like drones—demonstrates that high-end RF engineering is becoming increasingly portable and accessible.</p>]]></description>
            </item>
            
            <item>
                <title>写给闪卡的一封情书 A Love Letter to Flashcards</title>
                <link>https://lesleylai.info/en/flashcards/</link>
                <guid>https://lesleylai.info/en/flashcards/</guid>
                <pubDate>Fri, 10 Jul 2026 16:00:44 +0000</pubDate>
                <description><![CDATA[<p>作者起初对作为死记硬背工具的抽认卡持怀疑态度，但最终通过 Anki 采用了间隔重复法，以支持 STEM 等累积性学科的深度学习。在承认抽认卡可能助长浅层学习这一常见批评的同时，作者认为，只要使用得当，它们对于保持熟练度以及建立高级推理所必需的“组块化”概念至关重要。

作者的方法优先考虑质量而非数量：抽认卡绝不能取代最初的理解过程，且亲自编写的卡片比导入或 AI 生成的卡片效果更好。除了简单的定义外，作者还会为“顿悟时刻”、直觉甚至是反复出现的练习题制作卡片，以弥合初步学习与长期记忆之间的差距。

通过将抽认卡与数字笔记相结合，并保持精简且目标明确的复习流程，作者成功地在漫长的学习间隔中保留了复杂的知识。尽管目前除了医学教育外，关于 Anki 效能的实证数据有限，但作者发现，该技术将学习从一种易逝的临时性努力转变为持久的知识基础，使他们即使在多年后也能重新投入复杂的项目，而无需从零开始。</p><p>Initially skeptical of flashcards as a tool for rote memorization, the author eventually embraced spaced repetition through Anki to support deep learning in cumulative fields like STEM. While acknowledging common criticism—that flashcards can encourage superficial learning—the author argues that when used correctly, they are essential for maintaining fluency and building the conceptual "chunking" necessary for advanced reasoning.

The author’s approach prioritizes quality over quantity: flashcards should never replace the initial process of understanding, and they are most effective when personally authored rather than imported or AI-generated. Beyond simple definitions, the author creates cards for "aha moments," intuition, and even recurring practice problems to bridge the gap between initial study and long-term retention. 

By integrating flashcards with digital note-taking and maintaining a lightweight, high-intent review process, the author successfully retains complex knowledge across long gaps in study. Despite limited empirical data on Anki’s efficacy outside of medical education, the author finds that the technique transforms learning from a volatile, temporary effort into a durable foundation, allowing them to resume complex projects years later without starting from scratch.</p>]]></description>
            </item>
            
            <item>
                <title>RCA Victor 是如何在 1939 年向教室推销音响服务的 How RCA Victor sold Sound Service to classrooms in 1939</title>
                <link>https://pncnmnp.github.io/blogs/rca-victor-education.html</link>
                <guid>https://pncnmnp.github.io/blogs/rca-victor-education.html</guid>
                <pubDate>Fri, 10 Jul 2026 15:34:04 +0000</pubDate>
                <description><![CDATA[<p>这篇博文探讨了1939年《生活》杂志上一则关于RCA Victor“学校音响服务”的广告。

作者将这一史料置于1929年RCA与胜利留声机公司（Victor Talking Machine Company）合并的历史背景下进行考察。在大萧条前夕，RCA通过股票置换交易收购了胜利公司的有形资产，从而获得了在经济衰退期间实现转型的基础设施。在20世纪30年代的金融动荡中，RCA将目标锁定在教育领域以开辟新的收入来源，通过向学校提供音响系统、录音机和唱片目录，推动了课堂的现代化。

作者将早期的课堂技术推广与现代慕课（MOOCs）和人工智能等教育工具的兴起进行了引人深思的类比。尽管RCA当时主要将音乐作为一种经久不衰的教育商品，但诸如ERPI课堂电影（ERPI Classroom Films）等竞争对手也同时引入了纪录片和教学媒体。文章最后反思了人类通过技术重塑教育的执着追求，并探讨了未来一代回顾当今的“人工智能教育”时代时，是否会像我们审视20世纪30年代的课堂创新一样。</p><p>This blog post explores a 1939 *LIFE* magazine advertisement for RCA Victor’s “Sound Service for Schools.” 

The author places this artifact within the historical context of RCA’s 1929 merger with the Victor Talking Machine Company. By acquiring Victor’s tangible assets through a stock-swap deal just before the Great Depression, RCA secured the infrastructure to pivot during the economic downturn. Amidst the financial instability of the 1930s, RCA targeted the education sector to create new revenue streams, offering schools sound systems, recorders, and record catalogs to modernize the classroom.

The author draws compelling parallels between this early push for classroom technology and the modern rise of educational tools like MOOCs and AI. While RCA focused primarily on music as an evergreen educational commodity, competitors like ERPI Classroom Films were simultaneously introducing documentaries and instructional media. The piece concludes by reflecting on humanity’s persistent drive to reinvent education through technology, questioning how future generations will look back on today’s “AI in Education” era just as we now view the classroom innovations of the 1930s.</p>]]></description>
            </item>
            
            <item>
                <title>欧洲最大工会要求在气温超过30摄氏度时拥有停止工作的权利 Europe's Largest Unions Demand Right to Cancel Work on Days Above 30C</title>
                <link>https://novaramedia.com/2026/07/09/europes-largest-unions-demand-right-to-cancel-work-on-days-above-30c/</link>
                <guid>https://novaramedia.com/2026/07/09/europes-largest-unions-demand-right-to-cancel-work-on-days-above-30c/</guid>
                <pubDate>Fri, 10 Jul 2026 15:33:11 +0000</pubDate>
                <description><![CDATA[<p>继六月份创下高温纪录后，欧洲各大工会正要求欧盟委员会制定相关法律，以保护劳动者免受极端高温的侵害。每年约有 1.3 亿名劳动者面临热应激风险，这已导致大量工伤及数百人死亡。工会正致力于推动设立具有法律约束力的最高气温限制。

拟议的措施包括：当气温超过 30°C 时，体力劳动岗位（如建筑和农业）必须强制停工；久坐岗位则在气温超过 32.5°C 时强制停工。目前，欧洲各地的保护措施差异巨大，导致许多雇员仍处于危险的工作环境中。

在英国，英国工会联盟（TUC）正为争取类似标准而开展运动。他们指出，虽然法律规定了工作场所的最低温度，但却缺乏最高温度限制。工会联盟建议，雇主应在气温达到 24°C 时采取降温措施，并在气温达到 30°C（体力劳动为 27°C）时允许停止工作。劳工领袖们强调，随着气候变化使极端高温成为工作场所的常态，必须尽快更新安全法规，以确保劳动者的福祉。</p><p>Following a record-breaking June, major European trade unions are demanding that the European Commission enact legislation to protect workers from extreme heat. With approximately 130 million workers exposed to heat stress annually—leading to significant injuries and hundreds of deaths—unions are pushing for legally enforceable maximum temperature limits.

Proposed measures include mandatory work suspension when temperatures exceed 30°C for physically demanding roles (such as construction and agriculture) and 32.5°C for sedentary positions. Currently, protections vary significantly across the continent, leaving many employees vulnerable to dangerous working conditions.

In the UK, the Trades Union Congress (TUC) is campaigning for similar standards, arguing that while minimum workplace temperatures are legally established, maximum limits are non-existent. The TUC proposes that employers must take cooling measures at 24°C and allow work to stop if temperatures hit 30°C, or 27°C for manual labor. Labor leaders emphasize that as climate change makes extreme heat a permanent workplace reality, updated safety regulations are urgently required to ensure worker welfare.</p>]]></description>
            </item>
            
            <item>
                <title>埃及沙漠下发现古城及古老教堂 Lost city discovered beneath Egypt's desert with ancient church</title>
                <link>https://www.dailymail.com/sciencetech/article-15956159/Incredible-lost-city-discovered-Egypts-desert.html</link>
                <guid>https://www.dailymail.com/sciencetech/article-15956159/Incredible-lost-city-discovered-Egypts-desert.html</guid>
                <pubDate>Fri, 10 Jul 2026 15:32:11 +0000</pubDate>
                <description><![CDATA[<p>拒绝访问。您没有权限访问此服务器上的 "http://www.dailymail.com/sciencetech/article-15956159/Incredible-lost-city-discovered-Egypts-desert.html"。参考编号 #18.a7a4c117.1783697531.b0c17cb https://errors.edgesuite.net/18.a7a4c117.1783697531.b0c17cb</p><p>Access Denied You don't have permission to access "http://www.dailymail.com/sciencetech/article-15956159/Incredible-lost-city-discovered-Egypts-desert.html" on this server. Reference #18.a7a4c117.1783697531.b0c17cb https://errors.edgesuite.net/18.a7a4c117.1783697531.b0c17cb</p>]]></description>
            </item>
            
            <item>
                <title>我的临时邮箱黑名单把我屏蔽了。 My burner email blocklist blocked me</title>
                <link>https://benjamin.piouffle.com/blog/burner-email-blocklists/</link>
                <guid>https://benjamin.piouffle.com/blog/burner-email-blocklists/</guid>
                <pubDate>Fri, 10 Jul 2026 15:31:12 +0000</pubDate>
                <description><![CDATA[<p>该作者曾开发过一款屏蔽“一次性”电子邮箱域名的工具，但现在他反对在用户注册时系统性地拒绝那些注重隐私的电子邮件服务。

其核心观点在于区分“公共共享收件箱”（临时的、任何人皆可访问）与“个人别名”（永久的、私人的转发地址，如 Firefox Relay 或 Apple 的“隐藏邮件地址”）。虽然公共收件箱常被滥用，但个人别名是用户保护身份、管理垃圾邮件及追踪数据泄露的重要工具。

作者认为，域名屏蔽列表对蓄意的垃圾邮件发送者而言并无成效，因为他们可以轻易通过自定义域名或 Gmail 别名绕过限制。因此，这些列表主要惩罚的是注重隐私的用户，却无法阻止真正的攻击者。

作者建议，服务商应停止将电子邮件验证视为衡量“可信度”的手段，而不应采取硬性屏蔽措施。如果必须使用列表，也应明确区分共享的一次性邮箱与个人别名。开发者应摒弃非黑即白的拒绝策略，转而将域名声誉纳入更广泛、更细致的风险评估体系中。</p><p>The author, who once created a tool to block "burner" email domains, now argues against the systematic rejection of privacy-focused email services during user signups. 

The core of the argument is a distinction between **public shared inboxes** (temporary, accessible to anyone) and **personal aliases** (permanent, private forwarding addresses like Firefox Relay or Apple’s "Hide My Email"). While public inboxes are often used for abuse, personal aliases are essential tools for users to protect their identity, manage spam, and track data breaches.

The author contends that domain blocklists are ineffective against determined spammers, who can easily bypass them using custom domains or Gmail aliases. Consequently, these lists mainly punish privacy-conscious users while failing to stop actual attackers. 

Instead of hard-blocking, the author suggests that services should stop treating email verification as a proxy for "trustworthiness." If lists must be used, they should clearly differentiate between shared burners and personal aliases. Developers are encouraged to move away from binary rejections and instead incorporate domain reputation as part of a broader, more nuanced risk-assessment strategy.</p>]]></description>
            </item>
            
            <item>
                <title>统一内存详解：为什么迷你电脑能运行 70B 模型，而大型显卡却不行 Unified Memory, Explained: Why Mini PCs Can Run 70B Models a Big GPU Can't</title>
                <link>https://vettedconsumer.com/unified-memory-explained-why-mini-pcs-can-run-70b-models-a-big-gpu-cant-and-where-they-slow-down/</link>
                <guid>https://vettedconsumer.com/unified-memory-explained-why-mini-pcs-can-run-70b-models-a-big-gpu-cant-and-where-they-slow-down/</guid>
                <pubDate>Fri, 10 Jul 2026 14:36:01 +0000</pubDate>
                <description><![CDATA[<p>统一内存架构的迷你主机因优先考虑“容量”而非原始速度，已成为运行大型语言模型（LLM）的热门选择。与传统台式机因显存受限而存在性能上限不同，这些系统在 CPU、GPU 和 NPU 之间共享同一内存池。这使得相对平价的迷你主机能够加载庞大的模型（如 700 亿参数模型），而这些模型在过去通常需要昂贵的高端工作站显卡才能运行。

然而，这种容量优势是以性能大幅下降为代价的。LLM 的文本生成速度主要受限于内存带宽；由于迷你主机的带宽远低于独立显卡，其生成文本的速度就像“慢速阅读者”一样。此外，计算密集型的“预填充”阶段（读取长提示词）也是迷你主机中较弱的集成显卡难以应付的环节。

归根结底，这些机器不是追求速度的利器，而是解决容量问题的工具。它们非常适合那些需要运行大型、高内存占用模型，且模型无法在标准显卡上加载的用户。对于较小的模型或需要高速交互的任务，独立显卡依然是更好的选择。请根据模型规模而非营销参数来选择硬件。</p><p>Unified-memory mini PCs have become popular for running large language models (LLMs) because they prioritize **capacity** over raw speed. Unlike traditional desktops, where a GPU’s limited VRAM creates a hard ceiling, these systems share a single pool of system RAM across the CPU, GPU, and NPU. This allows a relatively affordable mini PC to load massive models—like a 70-billion-parameter model—that would otherwise require an expensive, high-end workstation card.

However, this capacity comes at a significant cost in performance. LLM text generation is primarily limited by memory bandwidth; because these mini PCs have significantly lower bandwidth than dedicated GPUs, they generate text at a "slow reader" pace. Furthermore, the "prefill" phase (reading long prompts) is compute-intensive, where the weaker integrated GPUs in mini PCs often struggle.

Ultimately, these machines are not speed-demons but capacity tools. They are ideal for users who need to run large, memory-hungry models that simply won't fit on a standard GPU. For smaller models or tasks requiring high-speed, interactive performance, a dedicated discrete GPU remains the superior choice. Match the hardware to the model’s size, not the marketing specs.</p>]]></description>
            </item>
            
            <item>
                <title>古钱币：斯巴达钱币如何？ Ancient Coins: What About Spartan Coins?</title>
                <link>https://coinweek.com/ancient-spartan-coins/</link>
                <guid>https://coinweek.com/ancient-spartan-coins/</guid>
                <pubDate>Fri, 10 Jul 2026 14:34:44 +0000</pubDate>
                <description><![CDATA[<p>斯巴达以拒绝使用传统货币而闻名，为了抑制财富积累并专注于军事，他们更倾向于使用笨重的铁条。几个世纪以来，这个城邦主要依赖物物交换或外来货币，长期保持着坚定的反物质主义文化。

随着斯巴达国力的衰落，这一传统立场最终发生了转变。从公元前3世纪的阿雷乌斯一世（Areus I）开始，斯巴达国王为了资助雇佣兵，开始铸造皇家货币。后来的领导人如克里昂米尼三世（Cleomenes III）和纳比斯（Nabis）铸造了带有君主肖像和当地神祇的银制四德拉克马，反映出该城邦正向更传统的经济模式靠拢。

在被纳入亚该亚同盟后，斯巴达采用了统一的区域货币。罗马征服之后，该城在盖乌斯·尤利乌斯·尤里科里斯（C. Julius Eurycles）等地方长官的授权下，发行了地方性的青铜货币，并最终以罗马皇帝的名义进行铸造。如今，这些钱币被归类为“拉科尼亚”或“拉刻代蒙”货币。虽然稀有的斯巴达皇家钱币价格昂贵，但它们作为历史记录，见证了一个骄傲的社会在希腊化和罗马时期对经济现实的逐渐适应。</p><p>Sparta is famously known for rejecting traditional currency, preferring cumbersome iron spits to discourage wealth accumulation and prioritize military focus. For centuries, the city-state relied on barter or foreign coinage, maintaining a staunchly anti-materialistic culture.

This traditional stance eventually shifted as Sparta’s power declined. Starting in the 3rd century BCE, Spartan kings—beginning with Areus I—began issuing royal coinage to fund mercenaries. Later leaders like Cleomenes III and Nabis minted silver tetradrachms featuring royal portraits and local deities, reflecting a move toward a more conventional economy.

Following its integration into the Achaean League, Sparta adopted a standardized regional currency. After the Roman conquest, the city issued local bronze coinage under the authority of magistrates like C. Julius Eurycles and, eventually, under the names of Roman Emperors. Today, these coins are classified under "Laconia" or "Lacedaimon." While rare royal Spartan coins command high prices, their existence serves as a historical record of a proud society’s gradual adaptation to the economic realities of the Hellenistic and Roman worlds.</p>]]></description>
            </item>
            
            <item>
                <title>ATProto 上的 ActivityPub ActivityPub over ATProto</title>
                <link>https://berjon.com/ap-at/</link>
                <guid>https://berjon.com/ap-at/</guid>
                <pubDate>Fri, 10 Jul 2026 14:34:25 +0000</pubDate>
                <description><![CDATA[<p>在社交媒体往往充满敌意的部落主义氛围中，Robin Berjon 提出了一种技术桥梁，旨在统一两个强大的协议：ActivityPub (AP) 和 AT Protocol (ATProto)。

Berjon 认为，虽然两者都致力于打破社交媒体的壁垒，但它们解决的是不同的问题。ActivityPub 擅长社交网络，但与电子邮件类似，容易受到服务器管理员的控制。相反，ATProto 在用户自主权和“可信退出”方面提供了更优越的架构，允许用户拥有自己的数据，并在不同提供商之间迁移，而不会丢失身份或关注者。

作者提出了一个设计构想：在 ATProto 个人数据服务器 (PDS) 之上实现 ActivityPub 路由。通过利用 ActivityPub 中“Actor”文档指向 ATProto 端点的灵活性，用户既能享受 AP 去中心化和联邦化的覆盖范围，又能保留 ATProto 主权且可迁移的数据所有权。

尽管存在一些细微的技术障碍——例如协调 REST/RPC 方法以及统一身份/句柄系统——但 Berjon 认为这些是可以克服的实际挑战，而非决定性的阻碍。通过整合这些互补技术，我们可以构建一个比传统联邦和封闭平台壁垒更具韧性、以用户为中心的网络。</p><p>Amidst the often-hostile tribalism of social media discourse, Robin Berjon proposes a technical bridge to unify two powerful protocols: ActivityPub (AP) and the AT Protocol (ATProto).

Berjon argues that while both aim to dismantle social media silos, they address different problems. ActivityPub excels at social networking but remains vulnerable to server-admin capture, similar to email. Conversely, ATProto offers a superior architecture for user agency and "credible exit," allowing users to own their data and move between providers without losing their identity or followers.

The author suggests a design provocation: implementing ActivityPub routes atop an ATProto Personal Data Server (PDS). By leveraging the "Actor" document’s flexibility in ActivityPub to point to ATProto-based endpoints, users could enjoy the decentralized, federated reach of AP while retaining the sovereign, portable data ownership of ATProto.

While minor technical hurdles exist—such as reconciling REST/RPC methods and aligning identity/handle systems—Berjon believes these are practical, bridgeable challenges rather than dealbreakers. By integrating these complementary technologies, we could create a more resilient, user-centric web that transcends the current limitations of both traditional federation and closed-platform silos.</p>]]></description>
            </item>
            
            <item>
                <title>Show HN: Runloom – 面向 Python 自由线程（free-threaded）的 Go 风格协程 Show HN: Runloom – Go-style coroutines for Python free-threaded</title>
                <link>https://github.com/robertsdotpm/runloom</link>
                <guid>https://github.com/robertsdotpm/runloom</guid>
                <pubDate>Fri, 10 Jul 2026 14:32:36 +0000</pubDate>
                <description><![CDATA[<p>**Runloom** 是一个高性能库，为 Python 引入了 Go 风格的有栈协程（stackful coroutines）。通过利用手写的汇编上下文切换、基于 C 语言的工作窃取调度器以及高效的 `netpoll` 实现，它使开发者能够编写跨所有 CPU 核心并发运行的阻塞式代码。

主要特性包括：
*   **易用性**：支持 `monkey.patch()`，无需 `async/await` 即可将标准阻塞式 I/O（套接字、时间等）转换为非阻塞的协作式代码。
*   **高性能**：专为自由线程（free-threaded）CPython (3.13t/3.14t) 设计，吞吐量和生成速率可与 Go 媲美。
*   **架构**：实现了 M:N 调度器，将任务分配到多个操作系统线程中，有效绕过了传统单线程 Python 并发的限制。
*   **兼容性**：为旧代码提供 `asyncio` 桥接，并可通过预编译的 wheel 包在主流操作系统和架构上使用。

尽管由于 CPython 执行帧的原因，Runloom 每个纤程的内存开销约为 Go 的 3.3 倍，但它为 Python 实现多核并行提供了一种强大的方式。它并不会加速单个 Python 字节码的执行，但能够让单个进程的阻塞式 Python 逻辑扩展到所有可用的硬件核心上。</p><p>**Runloom** is a high-performance library that brings Go-style stackful coroutines to Python. By utilizing hand-rolled assembly context switching, a C-based work-stealing scheduler, and an efficient `netpoll` implementation, it enables developers to write blocking code that runs concurrently across all CPU cores.

Key features include:
*   **Ease of Use:** Supports `monkey.patch()` to turn standard blocking I/O (sockets, time, etc.) into non-blocking cooperative code without needing `async/await`.
*   **Performance:** Designed for free-threaded CPython (3.13t/3.14t), it achieves throughput and spawn rates comparable to Go.
*   **Architecture:** Implements an M:N scheduler that distributes tasks across multiple OS threads, effectively bypassing the limitations of traditional single-threaded Python concurrency.
*   **Compatibility:** Provides an `asyncio` bridge for legacy code and is available via prebuilt wheels for major OS/arch combinations.

While Runloom’s memory overhead per fiber is roughly 3.3× that of Go due to CPython’s evaluation frames, it offers a powerful way to achieve multi-core parallelism in Python. It does not accelerate individual Python bytecode execution, but it allows a single process to scale blocking Python logic across all available hardware cores.</p>]]></description>
            </item>
            
            <item>
                <title>Scarf 已经不再使用 Haskell。 Scarf has moved away from Haskell</title>
                <link>https://avi.press/posts/2026-07-10-after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell.html</link>
                <guid>https://avi.press/posts/2026-07-10-after-7-years-in-production-scarf-has-reluctantly-moved-away-from-haskell.html</guid>
                <pubDate>Fri, 10 Jul 2026 14:31:11 +0000</pubDate>
                <description><![CDATA[<p>Haskell 的长期拥护者兼董事会成员 Avi Press 解释了为什么他的公司 Scarf 在新项目开发中放弃 Haskell，转而选择 Python。

在承认 Haskell 的可靠性和类型安全性的同时，Press 指出，人工智能驱动的开发浪潮已从根本上改变了编程的经济学。AI 代理依赖于快速反馈循环、低成本执行和低摩擦环境。Haskell 较长的构建时间、复杂的依赖管理以及较高的“冷启动”开销，造成了严重瓶颈，阻碍了 AI 辅助的工作流程。相比之下，Python 提供了有效利用现代大语言模型（LLM）所需的敏捷性，能够实现快速迭代和交付。

Press 警告说，如果 Haskell 社区继续侧重于学术研究（如依赖类型），而非构建性能和 AI 集成等工业需求，将面临停滞的风险。他敦促社区优先考虑“对代理友好”的工具（如更快的编译速度和更好的文档），以保持竞争力。最终，他认为如果 Haskell 不进化以适应 AI 驱动的范式，它将难以在快速发展的生态系统中竞争。对于 Scarf 而言，这一决定是对现代软件领域中生产力和速度紧迫需求的务实响应。</p><p>Avi Press, a longtime Haskell advocate and board member, explains why his company, Scarf, is moving away from Haskell for new development in favor of Python. 

While acknowledging Haskell’s reliability and type safety, Press argues that the rise of AI-driven development has fundamentally shifted the economics of programming. AI agents thrive on fast feedback loops, cheap execution, and low-friction environments. Haskell’s heavy build times, complex dependency management, and high "cold start" overhead create significant bottlenecks that hinder AI-assisted workflows. By contrast, Python offers the agility required to leverage modern LLMs effectively, allowing for rapid iteration and faster shipping.

Press warns that the Haskell community risks stagnation by focusing on academic research (like dependent types) rather than industrial needs like build performance and AI integration. He urges the community to prioritize "agent-friendly" tooling—such as faster compilation and better documentation—to remain relevant. Ultimately, he posits that unless Haskell evolves to accommodate the AI-driven paradigm, it will struggle to compete with faster-moving ecosystems. For Scarf, the decision was a pragmatic response to the urgent need for productivity and speed in the modern software landscape.</p>]]></description>
            </item>
            
            <item>
                <title>成功的企业会变得盲目 Successful Companies Go Blind</title>
                <link>https://ianreppel.org/how-successful-companies-go-blind/</link>
                <guid>https://ianreppel.org/how-successful-companies-go-blind/</guid>
                <pubDate>Fri, 10 Jul 2026 14:30:46 +0000</pubDate>
                <description><![CDATA[<p>墨西哥洞穴鱼为企业停滞提供了一个生动的隐喻：正如生活在洞穴中的鱼因黑暗环境不再提供奖励而进化到失去视力一样，成功的公司也常会患上“能力盲点”。

当高增长公司将员工人数置于标准之上时，它们创造了一个让工程卓越性退化为残余特征的环境。那些带着“视力”——即识别糟糕基础设施或过时实践的能力——入职的员工，往往会被否决。这导致了一种职业层面的细胞凋亡，他们对质量的追求被逐渐抹除。

为了掩盖这种腐败，公司建立了以官僚控制为先的“卓越中心”，进一步扼杀了内在动力。在市场壁垒的保护下，这些公司凭借早期成功积累的“脂肪”生存，依然保持盈利。管理者常将这种衰退误认为是企业文化，并将员工离职归咎于外部因素，而非自身内部的黑暗。归根结底，留在这样的环境中是一种自我适应；想要重获“视力”，唯一的办法就是离开洞穴，去新的水域游弋。</p><p>The Mexican cavefish provides a striking metaphor for corporate stagnation: just as cave-dwelling fish evolve to lose their sight because the dark environment no longer rewards it, successful companies often develop "competence blindness." 

When high-growth companies prioritize headcount over standards, they create an environment where engineering excellence becomes a vestigial trait. Employees who arrive with "sight"—the ability to recognize poor infrastructure or outdated practices—are often overruled, leading to a form of professional apoptosis where the desire for quality is programmed out of them. 

To hide this rot, companies create "centers of excellence" that prioritize bureaucratic control, further stifling intrinsic motivation. Protected by market barriers, these firms remain profitable while operating on "stored fat" from earlier successes. Managers often mistake this decline for culture, blaming turnover on external factors rather than their internal darkness. Ultimately, staying in such an environment is a form of self-adaptation; the only way to regain "sight" is to exit the cave and swim in new waters.</p>]]></description>
            </item>
            
            <item>
                <title>瑞安航空航班窗户“脱落”，男子险些被吸出机舱 Man nearly sucked out of 'detached' window on Ryanair flight</title>
                <link>https://www.rte.ie/news/2026/0710/1582735-world-ryanair/</link>
                <guid>https://www.rte.ie/news/2026/0710/1582735-world-ryanair/</guid>
                <pubDate>Fri, 10 Jul 2026 14:06:00 +0000</pubDate>
                <description><![CDATA[<p>请启用 JavaScript 和 Cookie 以继续。</p><p>Enable JavaScript and cookies to continue</p>]]></description>
            </item>
            
            <item>
                <title>Proton AG 的服务目前出现了一些问题。 Proton AG Services is currently experiencing some issues</title>
                <link>https://status.proton.me/incidents/01lxtcq155lc</link>
                <guid>https://status.proton.me/incidents/01lxtcq155lc</guid>
                <pubDate>Fri, 10 Jul 2026 14:04:35 +0000</pubDate>
                <description><![CDATA[<p>我们目前正在经历一起影响 Proton 服务登录的故障。我们的工程团队正在积极调查，并致力于尽快恢复正常访问。对于此次服务中断，我们深表歉意，并在有进一步消息时会及时更新。</p><p>We are currently experiencing an incident affecting login across Proton services.Our engineering teams are actively investigating and working to restore normal access as quickly as possible.We apologize for the disruption and will provide further updates as soon as more information is available.</p>]]></description>
            </item>
            
            <item>
                <title>朋克，或者为什么我不再直播了 Punk, or why I don't stream anymore</title>
                <link>https://geohot.github.io//blog/jekyll/update/2026/05/03/punk-or-why-i-dont-stream.html</link>
                <guid>https://geohot.github.io//blog/jekyll/update/2026/05/03/punk-or-why-i-dont-stream.html</guid>
                <pubDate>Fri, 10 Jul 2026 14:02:10 +0000</pubDate>
                <description><![CDATA[<p>这篇文章哀悼了以参与为基础的本真文化的消亡，认为其已被表演性的“奇观”和精心策划的营销所取代。作者主张，以人工智能、社交媒体和算法消费为特征的现代数字生活，导致了“电极刺激（wireheading）”现象，即用户在缺乏现实参与的情况下，体验到一种虚假的成就感。

作者指出，互联网这台“机器”已有效地胜过了真正的人类体验，将个人身份转变为统一且顺从的数据。随着我们的“内在现实”成为全球信息战的主要战场，作者警告称，我们已不再是遭遇物理上的征服，而是正经历心理上的同化。尽管作者认为现代人工智能不过是自我长达数十年退化的顶点，却并未提供简单的解决方案，并指出这场“新战争”需要的是灵魂本身。归根结底，本文以愤世嫉俗的视角观察了技术如何吸收人类文化，剥离其棱角，并将空洞、预先咀嚼过的版本反馈给人类，最终使个体失去了人生的方向盘。</p><p>This essay laments the death of authentic, participation-based culture, arguing that it has been replaced by performative "spectacle" and curated marketing. The author contends that modern digital life—characterized by AI, social media, and algorithmic consumption—has led to "wireheading," where users experience the illusion of achievement without real-world engagement. 

The author suggests that the "machine" of the internet has effectively outcompeted genuine human experience, transmuting individual identity into uniform, compliant data. As our "inner reality" becomes the primary theater of a global information war, the author warns that we are no longer being physically conquered but psychologically assimilated. While the author observes that modern AI is merely the climax of a decades-long erosion of self, they offer no easy solution, noting that the "new war" demands the soul itself. Ultimately, the piece serves as a cynical observation of how technology absorbs human culture, strips it of its rough edges, and feeds back a hollow, pre-chewed version that leaves the individual without a steering wheel.</p>]]></description>
            </item>
            
            <item>
                <title>像对待人类一样编写易于维护的代码。 Write code like a human will maintain it</title>
                <link>https://unstack.io/write-code-like-a-human-will-maintain-it</link>
                <guid>https://unstack.io/write-code-like-a-human-will-maintain-it</guid>
                <pubDate>Fri, 10 Jul 2026 14:00:21 +0000</pubDate>
                <description><![CDATA[<p>人们很容易任由大语言模型（LLM）生成冗余代码，并想当然地认为既然是 AI 在写代码，那么诸如“DRY”（不要重复自己）之类的可维护性问题就不再重要了。然而，这是一种危险的谬误。

大语言模型通过模仿你代码库中已有的模式、捷径和架构习惯来生成代码。当你不断合并重复的逻辑或“快速而草率”的解决方案时，你不仅是在外包工作，更是在训练模型将糟糕的编码习惯作为你项目的标准。每一次复制粘贴的条件语句都在强化一种错误的模式，导致模型在未来的响应中优先采用这些“反模式”。

最终，你的代码库将充斥着技术债务，而你将越来越难以通过提示词（Prompt）来摆脱困境。为避免这种情况，你必须将代码库视为一份高质量的蓝图。通过保持代码整洁且结构化，你可以确保 LLM 提供持续的高质量输出，而不是自动制造未来的维护难题。归根结底，你依然应该像对待人类维护者那样去编写代码，因为 AI 终究会学会模仿你最坏的习惯。</p><p>It is tempting to let Large Language Models (LLMs) generate redundant code, assuming that since the AI handles the typing, maintainability concerns like "DRY" (Don't Repeat Yourself) no longer matter. However, this is a dangerous fallacy.

LLMs generate code by mimicking the patterns, shortcuts, and architectural habits already present in your codebase. When you repeatedly merge duplicated logic or "quick and dirty" solutions, you aren't just outsourcing the work—you are training the model to adopt poor coding practices as your project’s standard. Every copy-pasted conditional reinforces a bad pattern, causing the model to prioritize these "anti-patterns" in future responses. 

Eventually, your codebase becomes cluttered with technical debt that is increasingly difficult to prompt your way out of. To avoid this, you must treat your codebase as a high-quality blueprint. By maintaining clean, structured code, you ensure the LLM provides consistent, high-quality output rather than automating the creation of future maintenance headaches. Ultimately, you should continue to write code as if a human will maintain it, because the AI will inevitably learn to mimic your worst habits.</p>]]></description>
            </item>
            
            <item>
                <title> Ryanair Passenger Sucked Toward Broken Window After Midair Engine Failure</title>
                <link>https://simpleflying.com/ryanair-thessaloniki-diversion-window-damage/</link>
                <guid>https://simpleflying.com/ryanair-thessaloniki-diversion-window-damage/</guid>
                <pubDate>Fri, 10 Jul 2026 13:35:33 +0000</pubDate>
                <description><![CDATA[<p></p><p></p>]]></description>
            </item>
            
            <item>
                <title>青铜时代晚期崩溃 Late Bronze Age Collapse</title>
                <link>https://acoup.blog/2026/01/30/collections-the-late-bronze-age-collapse-a-very-brief-introduction/</link>
                <guid>https://acoup.blog/2026/01/30/collections-the-late-bronze-age-collapse-a-very-brief-introduction/</guid>
                <pubDate>Fri, 10 Jul 2026 13:03:07 +0000</pubDate>
                <description><![CDATA[<p>“青铜时代晚期崩溃”（约公元前 1220–1170 年）指的是地中海东部和近东地区国家体制的普遍破坏与衰落。虽然这场崩溃并非“彻底”——许多定居点得以幸存并过渡到了铁器时代——但它标志着迈锡尼文明、赫梯帝国和埃及新王国遭受了严重且程度不一的挫折。

相关证据主要源于考古发现，即各大宫廷中心遗址中的“破坏层”。虽然较旧的理论将其归咎于外部的“多利亚人入侵”或火山爆发，但现代学术界倾向于将其视为多种相互关联因素共同造成的“完美风暴”。这可能包括气候引发的农作物歉收、激烈的国家间战争、经济不稳定，以及难民和掠夺者（如“海上民族”）的大规模迁徙。

崩溃的影响是深远的：希腊经历了一段严重的“黑暗时代”，伴随着去城市化和线性文字 B 的失传。然而，随之而来的政治真空促成了新的、具有历史意义的实体崛起，包括腓尼基城邦以及以色列和犹大王国。最终，这场崩溃起到了一种变革性的作用，打破了青铜时代中央集权的“大国格局”，并创造了重塑古典世界发展轨迹的区域条件。</p><p>The "Late Bronze Age Collapse" (c. 1220–1170 BC) refers to the widespread destruction and decline of state systems across the Eastern Mediterranean and Near East. While the collapse was not "total"—many sites survived and transitioned into the Iron Age—it marked a severe, if uneven, setback for the Mycenaean, Hittite, and New Kingdom Egyptian empires.

Evidence is primarily archaeological, featuring "destruction layers" at major palace centers. While older theories blamed external "Dorian invasions" or volcanic eruptions, modern scholarship favors a "perfect storm" of interrelated causes. This likely included climate-driven crop failures, intense inter-state warfare, economic instability, and mass movements of refugees and raiders (such as the "Sea Peoples"). 

The effects were profound: Greece suffered a severe "Dark Age" involving deurbanization and the loss of the Linear B script. However, the resulting political vacuum allowed for the emergence of new, historically significant entities, including the Phoenician city-states and the kingdoms of Israel and Judah. Ultimately, the collapse functioned as a transformative event, breaking the centralized Bronze Age "concert of powers" and creating the regional conditions that shaped the trajectory of the classical world.</p>]]></description>
            </item>
            
            <item>
                <title>AI 不懂宽恕，也无法遗忘。 AI doesn't know how to forgive and cannot forget</title>
                <link>https://tejassuds.com/blog/ai-cannot-forget</link>
                <guid>https://tejassuds.com/blog/ai-cannot-forget</guid>
                <pubDate>Fri, 10 Jul 2026 13:00:06 +0000</pubDate>
                <description><![CDATA[<p>“原谅并遗忘”是一个成语，但在工程学术语中，它描述了人工智能目前所缺乏的两种截然不同的人类能力。人类记忆是一个主动、自适应且“读-改-写”的过程；我们通过遗忘作为一种压缩方式来归纳总结，并通过再巩固过程来“消解”记忆中的情感温度。由于人类记忆的代谢成本很高，遗忘是一种生存机制。

相比之下，人工智能系统——无论是通过静态训练权重、上下文窗口还是向量检索——都运行在“只读”架构上。机器不具备衰退机制，也不理解“温度”或情感负荷的概念。它们的“遗忘”要么是偶然的（灾难性干扰或上下文死区），要么是强制的（类似失忆症式的删除）。

由于机器在保存信息时不需要面对稀缺性或能量成本，它们没有释放信息的内在动机。真正的原谅需要具备一种能力，即在完全清晰地保留怨恨的同时选择不采取行动——这一操作目前在任何标准的人工智能框架中都不存在。通过部署具备完美且永久记忆的系统，我们可能会破坏人类关系所依赖的社交礼仪——即“遗忘的馈赠”。</p><p>"Forgive and forget" is an idiom, but in engineering terms, it describes two distinct human capabilities that AI currently lacks. Human memory is an active, adaptive, and "read-modify-write" process; we forget as a form of compression to generalize, and we "drain the heat" from memories through reconsolidation. Because human memory is metabolically expensive, forgetting is a survival feature.

In contrast, AI systems—whether through static training weights, context windows, or vector retrieval—operate on "read-only" architecture. Machines do not possess the mechanism to decay, nor do they understand the concept of "heat" or emotional charge. Their "forgetting" is either accidental (catastrophic interference or context dead zones) or forced (amnesia-like deletion).

Because machines face no scarcity or energy cost to hold information, they have no functional incentive to release it. True forgiveness requires the ability to hold a grievance in full resolution while choosing not to act on it—an operation that currently exists in no standard AI framework. By deploying systems with perfect, permanent recall, we risk disrupting the social grace—the "gift of forgetting"—upon which human relationships depend.</p>]]></description>
            </item>
            
            <item>
                <title> Java 27: What's New?</title>
                <link>https://www.loicmathieu.fr/wordpress/informatique/java-27-whats-new/</link>
                <guid>https://www.loicmathieu.fr/wordpress/informatique/java-27-whats-new/</guid>
                <pubDate>Fri, 10 Jul 2026 12:34:01 +0000</pubDate>
                <description><![CDATA[<p></p><p></p>]]></description>
            </item>
            
            <item>
                <title>好的工具是无形的。 Good Tools Are Invisible</title>
                <link>https://www.gingerbill.org/article/2026/07/10/good-tools-are-invisible/</link>
                <guid>https://www.gingerbill.org/article/2026/07/10/good-tools-are-invisible/</guid>
                <pubDate>Fri, 10 Jul 2026 12:32:06 +0000</pubDate>
                <description><![CDATA[<p>作者认为，真正优秀的工具应该是“无形”的——它会淡化在背景中，让你专注于手头的工作。程序员常犯的一个错误是，将解决工具自身局限性所带来的“乐趣”误认为是真正的生产力。

许多用户对 Vim 或 Linux 等复杂工具产生了近乎宗教般的狂热，将它们陡峭的学习曲线和频繁的配置需求美化为某种英雄式的“黑客”成就。作者指出，这往往源于一种基于身份认同的部落主义：承认工具的缺陷会被视为对自我的攻击。由于将克服技术障碍带来的“聪明”感与实际产出混为一谈，用户往往会选择那些阻碍而非提升效率的工具。

归根结底，作者认为生产力应以“挂钟时间”来衡量，而不是看你与软件“博弈”时有多享受。好的工具应当提供出色的默认设置，而不是将设计决策转嫁给用户。无论你更偏好图形界面还是终端，衡量工具优劣的标准不在于其复杂程度或所营造的“格调”，而在于它能否隐于无形，让你在完成任务时不再有不必要的阻碍。</p><p>The author argues that a truly great tool should be "invisible"—fading into the background so you can focus on your work. A common pitfall among programmers is mistaking the "fun" of solving a tool’s inherent limitations for genuine productivity. 

Many users develop a religious devotion to complex tools like Vim or Linux, framing their steep learning curves and need for constant configuration as heroic "hacker" achievements. The author suggests this often stems from identity-based tribalism, where admitting a tool’s flaws feels like an attack on the self. By confusing the "clever" sensation of overcoming a technical hurdle with actual output, users often choose tools that hinder their efficiency rather than help it. 

Ultimately, the author contends that productivity is measured by "wall-clock time," not by how much you enjoy wrestling with your software. Good tools should provide excellent defaults rather than offloading design decisions onto the user. Whether you prefer a GUI or terminal, the mark of a superior tool is not its complexity or the "vibe" it projects, but its ability to disappear, allowing you to complete tasks without unnecessary friction.</p>]]></description>
            </item>
            </channel></rss>