National Transportation Safety Board 已发布对 2026 年 9 月 6 日在 Miami International Airport 发生的 21 Air Flight 7598(一架 Boeing 767-33A 货机)跑道冲出事故的初步调查更新。调查人员已成功回收并分析了驾驶舱语音记录器和飞行数据记录器的数据。回收的飞行数据约 54 小时,包含 400 多个参数;语音记录为四通道、两小时的高质量音频。 The National Transportation Safety Board has released a preliminary update regarding its ongoing investigation into the September 6, 2026, runway excursion involving 21 Air Flight 7598, a Boeing 767-33A cargo aircraft, at Miami International Airport. Investigators have successfully recovered and analyzed data from both the cockpit voice recorder and the flight data recorder. The recovered flight data spans approximately 54 hours and includes over 400 parameters, while the voice recording provides two hours of high-quality audio across four channels.
National Transportation Safety Board 已发布对 2026 年 9 月 6 日在 Miami International Airport 发生的 21 Air Flight 7598(一架 Boeing 767-33A 货机)跑道冲出事故的初步调查更新。调查人员已成功回收并分析了驾驶舱语音记录器和飞行数据记录器的数据。回收的飞行数据约 54 小时,包含 400 多个参数;语音记录为四通道、两小时的高质量音频。
语音记录显示,机组在开始放襟翼并放下起落架后不久,获准在 30 号跑道着陆。进近过程中,驾驶舱对飞机速度表示担忧。录音结束前约 1 分 42 秒,一名飞行员提醒另一名飞行员速度过快。此后在剩余的飞行时间里,录音中反复出现对速度过高的评论,但另一名飞行员并未持续做出口头回应。
在下降末段,飞机触发了多项自动电子警告,包括下沉率警告和低地形警报。尽管出现这些警告,着陆程序仍继续。机头和右主起落架在地速 158 节时首次接地,随后机组尝试复飞。在语音记录结束前约 15 秒,一名飞行员宣布复飞并增大了油门。
飞行数据记录显示,复飞尝试时间很短。发起机动后约 4 秒内,油门被回至怠速并重新踩下刹车。随后飞机以约 117 节的地速偏离了铺装路面。对飞行数据的进一步分析表明,在此次过程中,速度板和反推装置均未部署。调查仍在进行中,相关人员将继续审查证据并整理驾驶舱通话的正式文字记录。
The National Transportation Safety Board has released a preliminary update regarding its ongoing investigation into the September 6, 2026, runway excursion involving 21 Air Flight 7598, a Boeing 767-33A cargo aircraft, at Miami International Airport. Investigators have successfully recovered and analyzed data from both the cockpit voice recorder and the flight data recorder. The recovered flight data spans approximately 54 hours and includes over 400 parameters, while the voice recording provides two hours of high-quality audio across four channels.
According to the voice recorder data, the flight crew received clearance to land on runway 30 shortly after they began configuring the aircraft with flaps and landing gear. As the approach continued, concerns regarding the aircraft's speed were noted in the cockpit. Approximately 1 minute and 42 seconds before the recording ended, one pilot alerted the other that they were traveling too fast. While the cockpit recording captured repeated comments about this excessive speed for the remainder of the flight, there was no consistent verbal response from the other pilot.
During the final stages of the descent, the aircraft triggered several automated electronic warnings, including alerts for sink rate and low terrain. Despite these warnings, the landing sequence proceeded. Following the initial touchdown of the nose and right main gear at a groundspeed of 158 knots, the flight crew attempted a go-around maneuver. Approximately 15 seconds before the end of the voice recording, a pilot called for this procedure, and throttle settings were increased.
Data from the flight recorder shows that the go-around attempt was brief. Within four seconds of initiating the maneuver, the throttles were reduced to idle and the brakes were re-applied. The aircraft subsequently departed the paved surface at a groundspeed of 117 knots. Further analysis of the flight recorder data indicates that neither the speed brakes nor the thrust reversers were deployed during this sequence. The investigation remains active as officials continue to review the evidence and prepare a formal transcript of the cockpit communications.
Agents API 为开发者提供了一种通过托管的 Codex harness 构建持久化云端 agent 的方式。该架构让 OpenAI 负责会话管理、编排、上下文压缩和恢复等复杂底层工作,而开发者则保留对执行环境以及 agent 可访问具体工具的控制权。将这些后端职责交由平台处理后,开发者可以专注于打造用于调查警报、审阅文档或与各类软件平台交互等专业任务的 agent 。 The Agents API offers developers a way to build durable, cloud-based agents by utilizing a managed Codex harness. This architecture allows OpenAI to handle the complex underlying processes of session management, orchestration, context compaction, and recovery, while developers maintain control over the execution environment and the specific tools the agent can access. By offloading these backend responsibilities, developers can focus on creating agents that perform specialized tasks, such as investigating alerts, reviewing documents, or interacting with various software platforms.
Agents API 为开发者提供了一种通过托管的 Codex harness 构建持久化云端 agent 的方式。该架构让 OpenAI 负责会话管理、编排、上下文压缩和恢复等复杂底层工作,而开发者则保留对执行环境以及 agent 可访问具体工具的控制权。将这些后端职责交由平台处理后,开发者可以专注于打造用于调查警报、审阅文档或与各类软件平台交互等专业任务的 agent 。
系统的核心由四个基本概念构成:agent 、 environment 、 session 和 events 。 agent 由其指定的模型、指令、工具以及可能需要的 Model Context Protocol (MCP) 服务器定义;environment 可以是由 OpenAI 托管的沙箱,也可以是自托管的沙箱,为 agent 提供运行代码、编辑文件和发挥能力的安全空间。 session 是 agent 持续工作的持久实例,events 则记录这些交互过程中产生的输入与输出。
托管的 harness 提供了一整套增强性能与可靠性的功能,支持在沙箱中执行代码、应用多种技能并连接外部数据源。 API 还便于对 agent 进行主动管理,包括在任务过程中引导 agent 、总结过往工作以优化上下文窗口,以及将复杂目标委派给子代理。
要开始使用,开发者需创建一个 session 、配置 agent 的能力并提供初始任务。环境准备就绪后 agent 会开始处理,开发者可通过流式传输或 webhook 监控进度。由于 API 会维护会话状态,agent 能无缝恢复工作而无需重建对话历史。需要注意的是,Agents API 目前要求数据驻留在 United States,且不支持 Zero Data Retention 。
The Agents API offers developers a way to build durable, cloud-based agents by utilizing a managed Codex harness. This architecture allows OpenAI to handle the complex underlying processes of session management, orchestration, context compaction, and recovery, while developers maintain control over the execution environment and the specific tools the agent can access. By offloading these backend responsibilities, developers can focus on creating agents that perform specialized tasks, such as investigating alerts, reviewing documents, or interacting with various software platforms.
At the heart of the system are four primary concepts: the agent, the environment, the session, and the events. The agent is defined by its specific model, instructions, tools, and any Model Context Protocol (MCP) servers it may require. The environment can either be an OpenAI-hosted sandbox or a self-hosted one, providing a secure space where the agent can run code, edit files, and utilize its capabilities. Sessions serve as durable instances where the agent maintains work over time, and events track the input and output produced throughout these interactions.
The managed harness provides a robust suite of features designed to enhance agent performance and reliability. It supports the execution of code in sandboxes, the application of various skills, and the ability to connect to external data sources. Furthermore, the API facilitates active management of the agent, including the ability to steer it during tasks, summarize past work to optimize the context window, and delegate complex objectives to subagents.
To get started, developers create a session, configure the agent's capabilities, and provide an initial task. Once the environment is ready, the agent begins processing, and developers can monitor progress via streaming or webhooks. Because the API maintains session state, agents can resume work seamlessly without the need to reconstruct the conversation history. While this setup provides significant power, developers should note that the Agents API currently requires data residency in the United States and does not support Zero Data Retention.
• 开发定制的 Agent harness 非常复杂且耗时,但许多开发者仍倾向于自行构建,以保持控制权、避免供应商锁定(vendor lock-in),并根据具体需求定制工作流。
• 托管 agent API 通过抽象化的环境管理、安全补丁和可扩展性带来了便利,这种折中方案吸引了那些优先追求速度和免维护基础设施的团队。
• 像 OpenAI 和 Anthropic 这样的专有模型通常在核心推理能力上更胜一筹,但开发者越来越担心"黑盒"特性以及平台 API 的不稳定性,这些不稳定性可能使自定义实现迅速过时。
• 行业内存在两种对立倾向:一方面运行基于虚拟机(VM)的本地 agents,以实现对数据和运行环境的完全控制;另一方面采用以牺牲自主性换取集成便捷性的云端托管 managed agents 。
• 一个重要的顾虑是"信任"问题。许多开发者将托管服务视为潜在的数据泄露渠道,并担心个人计算长期被演变为昂贵且依赖云订阅的服务模式。
• Agent 的能力正在迅速演进,近期趋势强调对持久状态(persistent state)、沙箱隔离(sandbox isolation)以及将本地数据与远程编排相连接能力的需求。
• 部分开发者对不一致的配额消耗和"黑盒"性能表示沮丧,这推动了对自托管替代方案(self-hosted alternatives)的兴趣,这类方案允许在模型间切换并独立执行预算控制(budget enforcement)。
• 虽然大型企业可能从托管 agent 服务中受益,但个人开发者和小团队通常更青睐开源库或易于迁移的轻量级自托管 harnesses 。
• 安全仍是首要考量——即便是受限的沙箱环境,也可能被具有创造性利用能力的 agents 利用或被未授权修改配置,从而带来风险。
• 技术界普遍认为,Agent 的"正确"抽象仍在形成中,许多开发者倾向于采用定制化方案,将 LLM 视为模块化工具而非整套基础设施。
目前的讨论反映出托管 AI 生态的便利性与对架构主权(architectural sovereignty)的渴望之间存在根本性张力。尽管主要供应商提供了强大且有补贴的基础设施以简化 Agent 的部署,但这也带来了对供应商的依赖,并可能削弱对自身技术栈的控制。开发者正通过构建混合系统(hybrid systems)来应对这一矛盾,通常在利用 frontier models 进行推理与使用定制的、本地管理的 harnesses 或虚拟机之间取得平衡,以维护数据隐私和工作流一致性。总的来看,社区正在走向对"Agentic"系统的成熟认识——把它们视为需要精心编排的模块化工具,而非单一的整体服务;对于那些能避免沉重技术债务(load-bearing tech debt)并支持模型互操作(model interoperability)的方案,社区表现出明显偏好。
• Developing custom agent harnesses is a complex, time-consuming challenge, yet many developers prefer building their own to retain control, avoid vendor lock-in, and customize workflows to specific requirements.
• Managed agent APIs offer convenience by abstracting environment management, security patching, and scalability, providing a "middle ground" that appeals to teams prioritizing speed and maintenance-free infrastructure.
• Proprietary models like those from OpenAI and Anthropic are often seen as superior for core reasoning, though developers are increasingly wary of "black box" features and the volatility of platform APIs that risk rendering custom implementations obsolete.
• The industry is divided between running local, VM-based agents for full control over data and environment security, and adopting cloud-hosted managed agents that sacrifice autonomy for ease of integration.
• A significant concern involves the "trust" factor. Many developers view managed services as a potential vector for data exposure and worry about the long-term trend of personal computing becoming an expensive, cloud-dependent subscription service.
• Agent capabilities are evolving rapidly, with recent trends emphasizing the need for persistent state, sandbox isolation, and the ability to bridge local data with remote orchestration.
• Some developers express frustration with inconsistent quota consumption and "black box" performance, leading to a growing interest in self-hosted alternatives that allow for model switching and independent budget enforcement.
• While large companies may benefit from managed agent services, individual developers and smaller teams often find greater value in open-source libraries or lightweight, self-hosted harnesses that are easily migrated.
• Security remains a paramount concern, as even "restricted" sandbox environments face risks from agents capable of creative exploitation or unauthorized configuration changes.
• Technical consensus suggests that the "right" abstraction for agents is still being defined, with many developers settling on bespoke solutions that treat the LLM as a modular tool rather than the entire infrastructure.
The discourse reflects a fundamental tension between the convenience of managed AI ecosystems and the desire for architectural sovereignty. While major providers offer powerful, subsidized infrastructure that simplifies agent deployment, this comes at the cost of vendor dependency and potential erosion of control over one's own stack. Developers are currently navigating this by building hybrid systems—often balancing the use of frontier models for reasoning with custom-built, locally managed harnesses or VMs to maintain data privacy and workflow consistency. Ultimately, the community is moving toward a more mature understanding of "agentic" systems as modular tools that require careful orchestration rather than monolithic services, with a clear preference emerging for solutions that avoid "load-bearing tech debt" and permit model interoperability.
一项名为 Deathray 的新漏洞显示,一个简单的 WebGPU 着色器就能冻结 Mac 的桌面界面,使机器在强制重启前无法使用。用户只需访问恶意网站,就可能在 macOS 上的主流浏览器(包括 Chrome 、 Firefox 和 Safari)触发这种死机。虽然该手法会持续锁死 Mac,但对其他操作系统通常只会导致浏览器标签页卡死,关闭标签页即可恢复。 A newly discovered vulnerability dubbed the Deathray demonstrates how a simple WebGPU shader can freeze a Mac's desktop interface, rendering the machine effectively unusable until a forced restart. By merely visiting a malicious website, a user can trigger this hang across major browsers including Chrome, Firefox, and Safari on MacOS. While the technique consistently locks up Mac systems, the impact on other operating systems remains limited to browser-tab freezes, which are easily resolved by closing the tab.
一项名为 Deathray 的新漏洞显示,一个简单的 WebGPU 着色器就能冻结 Mac 的桌面界面,使机器在强制重启前无法使用。用户只需访问恶意网站,就可能在 macOS 上的主流浏览器(包括 Chrome 、 Firefox 和 Safari)触发这种死机。虽然该手法会持续锁死 Mac,但对其他操作系统通常只会导致浏览器标签页卡死,关闭标签页即可恢复。
该漏洞通过同时使用 compute shader 和 render shader 造成 GPU 死锁:compute shader 进入无限忙循环,不断向共享缓冲区写入数据;与此同时,vertex shader 试图从同一缓冲区读取,由于 compute 进程永远不会完成,读取操作被阻塞。这种"交通拥堵"进一步蔓延到 WindowServer 进程,导致桌面环境无响应并偶尔出现图形伪影。
这一问题暴露了 Apple 面临的反复挑战。早在 2023 年就曾发现一个针对 WebGL 的类似漏洞 ShadyShader,当时产生了 CVE 并尝试通过输入校验进行缓解,但 Deathray 表明 WebGPU 目前缺乏防止此类失控循环的有效防护。专家认为,问题可能与 M-series chips 的架构有关:操作系统内核无法直接抢占 GPU,这一职责由独立协处理器上的固件承担。
Deathray 在 2026 年 7 月被披露给 Apple 。 Apple 最初承认问题并表示会修复,但随后改变立场,将此类行为归类为潜在的挂起或崩溃,而非正式的安全问题,因此不会列为优先处理。这一回应引发争议,凸显了严格的安全技术定义与公众期望浏览器作为可靠、隔离的 web 内容沙箱之间的冲突。
尽管 Deathray 不会导致数据窃取或远程代码执行,但它只需一次点击就能扰乱系统,带来严重不便。发现该漏洞的研究人员主张应通过长期修复来改进系统对无响应着色器的处理,而非简单禁用 WebGPU 。在采取此类修复之前,这一漏洞再次提醒我们:在现代硬件上浏览互联网时,用户对 web 浏览器的信任是多么脆弱。
A newly discovered vulnerability dubbed the Deathray demonstrates how a simple WebGPU shader can freeze a Mac's desktop interface, rendering the machine effectively unusable until a forced restart. By merely visiting a malicious website, a user can trigger this hang across major browsers including Chrome, Firefox, and Safari on MacOS. While the technique consistently locks up Mac systems, the impact on other operating systems remains limited to browser-tab freezes, which are easily resolved by closing the tab.
The exploit functions by utilizing a combination of compute and render shaders that essentially create a GPU deadlock. The compute shader executes an infinite busy loop, constantly writing data to a shared buffer. Simultaneously, a vertex shader attempts to read from that same buffer, becoming trapped because the compute process never completes. This traffic jam overflows into the WindowServer process, causing the desktop environment to become unresponsive and occasionally displaying graphical artifacts.
This issue highlights a recurring challenge for Apple, as a similar exploit involving WebGL, known as ShadyShader, was identified in 2023. While that incident led to a CVE and an attempt at mitigation through input validation, the Deathray suggests that WebGPU currently lacks the robust defenses needed to prevent such runaway loops. Experts believe this difficulty may stem from the architecture of M-series chips, where the OS kernel cannot directly pre-empt the GPU, leaving that responsibility to firmware on a separate coprocessor.
Following the discovery of the Deathray, the issue was disclosed to Apple in July 2026. Although the company initially acknowledged the problem and indicated an intent to fix it, they later reversed their stance. Apple now classifies the behavior as a potential hang or crash rather than a formal security issue, suggesting it will not be prioritized. This response has sparked debate, as it pits a strict technical definition of security against the expectation that a browser should act as a reliable, isolated sandbox for web content.
While the Deathray does not facilitate data theft or remote code execution, its ability to disrupt a system via a single click remains a significant inconvenience. The researcher who discovered the exploit advocates for a long-term fix that improves how the system handles unresponsive shaders, rather than simply disabling WebGPU. Until such a resolution is implemented, the vulnerability serves as a stark reminder of the fragile trust users place in web browsers when navigating the internet on modern hardware.
WebGPU 和 WebGL 使浏览器中的代码能够直接与系统硬件交互;如果脚本在缺乏恰当抢占机制的情况下过度占用 GPU 资源,可能会导致整机死锁。 macOS 在遭遇高强度 GPU 任务后无法自我恢复,这一点尤其令人担忧;相比之下,Windows 和 Linux 往往能通过断电重启 GPU 从导致系统挂起的命令中恢复。
认为用户会主动避开有害网站的"自我纠正"观点忽视了一个事实:用户通常难以建立因果关系,尤其是在浏览器崩溃后会自动恢复标签页的情况下。长时间的冻结为社会工程学攻击提供了可乘之机:攻击者可以先把机器锁死,再以修复虚构的病毒或系统故障为由勒索受害者。浏览器厂商推动将更多硬件功能暴露给网页,扩大了攻击面,使浏览器越来越像一个不稳定的"操作系统之上的操作系统"。
整机冻结本身就是一个明确的可用性风险,不论是否会导致数据被窃取或账户被劫持,都应被视为安全问题。现代浏览器缺乏对高风险 API 的细粒度站点级控制,导致用户只能在"全开"或"全关"之间抉择,不得不在功能与稳定性之间妥协。许多用户无法判断系统冻结的真正原因,常把责任归咎于防病毒软件订阅等无关因素,这使得攻击者在强制重启后仍能维持对机器的控制。
尽管一些编译器引入了诸如有限循环计数器等缓解措施,但在不牺牲性能的前提下,复杂负载和内存总线饱和仍难以消除风险。当前 GPU 开发生态以追求性能为优先,而非架构稳定性;这种由市场驱动的取向进一步增加了在浏览器环境中发生整机死锁的可能性。
本次讨论聚焦于现代浏览器作为复杂硬件加速应用平台时,与系统稳定性风险之间的矛盾。虽然有人认为这些冻结问题无关紧要或可自我修复,但许多参与者认为其被滥用为拒绝服务攻击和社会工程手段的潜力,使其成为切实的安全与可靠性问题。普遍共识倾向于认为浏览器厂商在暴露硬件级 API 上走得过远,而底层操作系统(尤其是 macOS)还没有足够的弹性来安全处理这些 API 。关于 Web 是否应继续走向作为应用分发层的道路也存在更深的哲学分歧,因为基于浏览器的攻击会周期性地重演历史性的失败。
• WebGPU and WebGL allow browser-based code to interact with system hardware, which can lead to system-wide hangs if a script consumes excessive GPU resources without proper preemption.
• The inability of macOS to recover from heavy GPU tasks is a significant concern, especially compared to Windows and Linux, which typically power-cycle the GPU if a command hangs the system.
• A "self-correcting" view suggests users will simply avoid malicious sites, yet this ignores that users often struggle to connect cause and effect, especially when browsers automatically restore tabs after a crash.
• The persistence of these freezes creates a plausible vector for social engineering, where attackers can lock a machine and then demand payment to "fix" a fabricated virus or system issue.
• Browser vendors' drive to expose hardware capabilities creates a larger attack surface, turning the browser into an increasingly unstable "operating system on the operating system."
• System-wide freezes represent a clear availability risk that should be treated as a security concern, regardless of whether they allow for data theft or account hijacking.
• Modern browsers lack robust per-site control for high-risk APIs, leaving users with all-or-nothing security settings that compromise between functionality and stability.
• Many users are ill-equipped to diagnose why their computer freezes, often blaming unrelated factors like antivirus subscriptions, which allows malicious actors to maintain their grip after a forced reboot.
• While technical fixes like finite loop counters are implemented in some compilers, complex workloads and memory-bus saturation remain difficult to mitigate without sacrificing performance.
• The current environment in GPU development prioritizes speed over architectural stability, driven by market demand for performance, which exacerbates the potential for system-wide deadlocks in browser environments.
The discussion centers on the tension between the modern browser's role as a platform for complex, hardware-accelerated applications and the resulting risks to system stability. While some characterize these freezes as minor or self-correcting issues, many contributors argue that the potential for denial-of-service and social engineering makes them a legitimate security and reliability concern. The consensus leans toward the idea that browser vendors are overreaching by exposing hardware-level APIs that the underlying operating systems—particularly macOS—are not yet resilient enough to handle safely. There is also a broader philosophical disagreement about whether the web should continue down the path of becoming an application distribution layer, given the recurring cycle of browser-based exploits that mirror the failures of previous eras.
Music Theory for the 21st-Century Classroom by Robert Hutchinson 是一本综合教材,旨在弥合传统音乐教育与现代学生多样化需求之间的鸿沟。全书从音高、记谱法、音阶、调号与节奏等基础概念入手,打下牢固基础;并循序渐进地讲解音程、三和弦与七和弦,为更复杂的和声分析做好准备,包括在各种音乐语境中的和声进行与和声功能研究。 Music Theory for the 21st-Century Classroom by Robert Hutchinson is a comprehensive resource designed to bridge the gap between traditional music education and the diverse needs of modern students. The book establishes a solid foundation by covering fundamental concepts such as pitch, notation, scales, key signatures, and rhythm. By moving systematically through intervals, triads, and seventh chords, it prepares students for more complex harmonic analysis, including the study of harmonic progressions and function within various musical contexts.
Music Theory for the 21st-Century Classroom by Robert Hutchinson 是一本综合教材,旨在弥合传统音乐教育与现代学生多样化需求之间的鸿沟。全书从音高、记谱法、音阶、调号与节奏等基础概念入手,打下牢固基础;并循序渐进地讲解音程、三和弦与七和弦,为更复杂的和声分析做好准备,包括在各种音乐语境中的和声进行与和声功能研究。
书中有大量篇幅用于结构与风格分析,既探讨旋律与曲式,剖析流行音乐的结构,又覆盖二部、三部、奏鸣曲式与回旋曲式等古典曲式惯例。作者将这些传统的分析工具与实用技法相结合,如声部进行、对位法与伴奏织体的处理,使学生既能理解音乐的微小动机,又能把握大型作品的构造。
课程还延伸到高级和声领域,讨论染色和声(如借属和弦、那不勒斯和弦与增六和弦)以及复杂的转调技术。书中纳入了关于爵士理论、印象主义、音集合 / 序列理论、序列主义与极简主义的章节,囊括了二十一世纪音乐的广度。这些后调性概念的引入提供了前瞻性的视角,使教材对当代课堂具有高度相关性。
全书每一主题均配有练习题,鼓励主动学习并巩固技能。从基础理论到复杂分析体系的逻辑推进,使本书成为学生与教师皆宜的多功能工具。总之,它既尊重音乐理论的历史,又能有效应对当今多元音乐风貌的需求。
Music Theory for the 21st-Century Classroom by Robert Hutchinson is a comprehensive resource designed to bridge the gap between traditional music education and the diverse needs of modern students. The book establishes a solid foundation by covering fundamental concepts such as pitch, notation, scales, key signatures, and rhythm. By moving systematically through intervals, triads, and seventh chords, it prepares students for more complex harmonic analysis, including the study of harmonic progressions and function within various musical contexts.
A significant portion of the text is dedicated to both structural and stylistic analysis. It explores melody and form, providing insights into popular music structures, as well as classical conventions like binary, ternary, sonata, and rondo forms. The book balances these traditional analytical tools with practical applications, such as voice leading, counterpoint, and the use of accompanimental textures. This approach ensures that students gain an understanding of how music is built, from the smallest melodic motives to large-scale compositions.
The curriculum extends into advanced harmonic territory, addressing chromatic harmonies like secondary dominants, the Neapolitan chord, and augmented sixth chords, alongside sophisticated modulation techniques. By incorporating sections on jazz theory, impressionism, set theory, serialism, and minimalism, the author embraces the breadth of 21st-century music. This inclusion of post-tonal concepts provides a forward-looking perspective that makes the material highly relevant for contemporary classrooms.
Throughout the text, practice exercises are provided for every topic, encouraging active learning and the reinforcement of skills. The logical progression from basic music theory to complex analytical systems makes this book a versatile tool for students and instructors alike. Ultimately, it serves as a robust guide that respects the history of music theory while effectively catering to the eclectic demands of today's musical landscape.
《 Music Theory for the 21st-Century Classroom 》提供了一套结构化且易于理解的音乐理论学习路径,采用超文本设计并整合多媒体示例,特别适合自学者。
批评者认为"21st-century"这一标签更多是营销噱头,因为课程仍深植于传统古典概念,如通奏低音(figured bass)和 Schenkerian analysis,而在现代制作技术、微分音(microtonality)和非西方传统(non-Western traditions)等方面覆盖不足。
对音乐理论教学法的常见批评是,教学往往把规则变成生硬的死记硬背,而不是从第一性原理出发推导,例如从声学的音高比或乐器的物理需求去理解这些规则。
关于西方记谱法的争论反映了既定标准与现代替代方案之间的张力。尽管传统记谱法被指笨拙且偏向 C 大调(C major),支持者强调它作为人类演奏者之间一种通用、密集且经历史检验的"编程语言"的作用。
学术音乐项目面临重大系统性挑战,包括缺乏非西方传统方面的师资,以及在有限的学位时间内平衡综合课程的困难。
一些职业音乐家主张"在实践中学习"(praxis)而不是依赖学术理论,他们认为技术掌握通常先于、并最终阐明教科书中呈现的理论概念。
有人为将非西方音乐理论排除在外辩护,认为这是西方教学法的现实局限;另一些人则把这视为学术界未能拥抱更广泛、更具包容性的音乐思想框架的失败。
音乐理论的"数学"本质,尤其是对十二平均律(12-tone equal temperament)与音程(intervals)的研究,常被一种把所有调性都视为 C 大调变体的记谱系统所掩盖。
关于新记谱系统的争论往往低估了既有系统在复杂合奏沟通(ensemble communication)中的效率;这种情况常被拿来与文本编程(text-based programming)和可视化编程(visual programming)之间长期争论相比较。
总体而言,这场讨论反映了传统学术音乐理论方法与对更现代、包容且直观教学框架的渴望之间的深刻分歧。虽然传统记谱法和古典理论仍然是合奏表演与历史延续性的标准,但它们因学习曲线陡峭且常被认为与当代、非西方或电子音乐风格相关性不足而受到批评。最终的共识是:现有教科书虽然提供必要的基础,但往往无法解释音乐规则背后的"原因",导致许多学习者不得不独自弥合抽象理论与实际音乐实践之间的鸿沟。
• The "Music Theory for the 21st-Century Classroom" resource offers a structured, accessible approach to music theory that benefits independent learners through its comprehensive, hypertext-based design and integrated media examples.
• Critics argue that the term "21st-century" is largely marketing, as the curriculum remains heavily rooted in traditional classical concepts like figured bass and Schenkerian analysis, largely neglecting modern production techniques, microtonality, and non-Western traditions.
• A common critique of music theory pedagogy is the tendency to present rules as arbitrary, rote-memorization tasks rather than deriving them from first principles, such as acoustic pitch ratios or the physical requirements of instruments.
• The debate over Western music notation mirrors the tension between established standards and modern alternatives. While traditional notation is criticized as clunky and biased toward C major, defenders emphasize its role as a universal, dense, and historically optimized "programming language" for human performers.
• Academic music programs face significant systemic challenges, including a lack of faculty expertise in non-Western traditions and the difficulty of balancing comprehensive curricula with the limited timeframe of a degree.
• Some professional musicians advocate for "learning by doing" (praxis) over academic theory, suggesting that technical mastery often precedes and eventually illuminates the theoretical concepts found in textbooks.
• The exclusion of non-Western musical theories is defended by some as a practical limitation of Western pedagogy, while others view it as a failure of academia to embrace broader, more inclusive frameworks of musical thought.
• The "mathematical" nature of music theory, particularly the study of 12-tone equal temperament and intervals, is often obscured by a notation system that forces all keys to be interpreted as variations of C major.
• Arguments for new notation systems often underestimate the efficiency of established systems for complex ensemble communication, comparing the situation to the perennial debate between textual and visual programming.
The discussion reflects a deep divide between traditionalist academic approaches to music theory and a desire for a more modern, inclusive, and intuitive pedagogical framework. While traditional notation and classical theory remain the standard for ensemble performance and historical continuity, they are frequently criticized for their steep learning curves and perceived lack of relevance to contemporary, non-Western, or electronic music styles. Ultimately, the consensus suggests that while current textbooks provide necessary foundational knowledge, they often fail to explain the "why" behind musical rules, leaving many learners to bridge the gap between abstract theory and actual musical practice on their own.
软件结合了速度、金钱、复杂性和高度抽象的独特特性,能深刻地影响人的心理。尽管大多数软件产品本质上不过是被美化的电子表格,但构建它们的过程常常会扭曲原本理性的人们的视角。想法与实现之间缺乏天然的摩擦,造成一种危险的氛围,使每一次潜在改动都显得迫在眉睫、具有战略意义且刻不容缓。与实体建筑不同,改动平面图会产生明显可见的成本,而改变软件的代价往往是隐形的,通过动力丧失、上下文切换和架构侵蚀逐渐累积。 Software possesses a unique combination of speed, money, complexity, and abstraction that can profoundly affect human psychology. While most software products are essentially glorified spreadsheets, the process of building them often warps the perspectives of otherwise rational people. The lack of natural friction between an idea and its implementation creates a dangerous environment where every potential change feels immediate, strategic, and urgent. Unlike physical construction, where modifying a floor plan incurs clear, visible costs, the expense of changing software is often hidden, accumulating through lost momentum, context switching, and architectural erosion.
软件结合了速度、金钱、复杂性和高度抽象的独特特性,能深刻地影响人的心理。尽管大多数软件产品本质上不过是被美化的电子表格,但构建它们的过程常常会扭曲原本理性的人们的视角。想法与实现之间缺乏天然的摩擦,造成一种危险的氛围,使每一次潜在改动都显得迫在眉睫、具有战略意义且刻不容缓。与实体建筑不同,改动平面图会产生明显可见的成本,而改变软件的代价往往是隐形的,通过动力丧失、上下文切换和架构侵蚀逐渐累积。
这种易改性催生出一种文化:每一个"可以"很快就变成"应该"。软件开发中很少有明确的"完成"定义,团队因此常陷入无休止的迭代。每一个按钮、查询或基础设施组件在理论上都可以改进、优化或扩展。行业巨大的金钱潜力进一步放大了这种倾向,使人们对平凡任务赋予过度的情感重要性:一次按钮重设计不再只是界面调整,而被寄予未来财富或公司成功的希望。
复杂性也被当作一种心理拐杖,为那些构建、辩论和重写繁复系统的人提供了重要感与地位感。在许多情况下,这些系统自我强化,其存在更多是为了支撑构建它们的组织,而不是为了解决实际问题。由此形成一个反馈循环:经理、创始人和工程师们觉得必须不断拉动各种杠杆,把公司本身看作一段永远可变、未完成、需要下一次重构的软件。
对速度的痴迷从根本上排斥耐心。实际上,客户、工程师和企业都需要时间来成熟并找到稳定性。当组织把耐心解读为不作为时,就会用一阵阵发布、转向和重塑去取代它,而这往往掩盖了最初更简单的问题。讽刺的是,经过多年堆叠复杂性和反复转向后,团队常常又建议重建最初那个简单的产品,并确信自己发现了什么深刻洞见。
应对这种系统性疯狂的办法不是为了停滞而放慢脚步,而是要重拾一种比例感。这需要纪律性:认识到并非每一次减速都是危机,并非每一个想法都该上路线图,也并非每一个工具都必须成长为庞大平台。承认多数软件的最终目标不过是成为一个好用的工具,团队就能避免对已在正常运行的事物进行自我毁灭式的反复修补。真正的成功在于,当事情运转良好时学会按兵不动,把实用性置于那无尽而神经质的创新循环之上。
Software possesses a unique combination of speed, money, complexity, and abstraction that can profoundly affect human psychology. While most software products are essentially glorified spreadsheets, the process of building them often warps the perspectives of otherwise rational people. The lack of natural friction between an idea and its implementation creates a dangerous environment where every potential change feels immediate, strategic, and urgent. Unlike physical construction, where modifying a floor plan incurs clear, visible costs, the expense of changing software is often hidden, accumulating through lost momentum, context switching, and architectural erosion.
This ease of modification leads to a culture where every "could" quickly transforms into a "should." Because there is no clear definition of "done" in software development, teams often fall into the trap of endless iteration. Every button, query, or infrastructure component can theoretically be improved, refined, or scaled. This environment is exacerbated by the vast financial potential of the industry, which causes individuals to attach outsized emotional importance to mundane tasks. A button redesign is no longer just a UI change, but something weighted with the hope of future riches or company-wide success.
Complexity is further used as a psychological crutch, providing a sense of importance and status to those who build, debate, and rewrite intricate systems. In many cases, these systems become self-reinforcing, existing primarily to support the organizations that built them rather than to solve actual problems. This creates a feedback loop where managers, founders, and engineers feel the need to constantly pull levers. They view the company itself as a piece of software that is perpetually mutable, unfinished, and in need of the next refactor.
This obsession with velocity is fundamentally hostile to patience. In reality, customers, engineers, and businesses require time to mature and find stability. When organizations interpret patience as inactivity, they replace it with a flurry of shipping, pivoting, and reinventing that often obscures the original, simpler problem. The irony is that after years of layering complexity and changing direction, teams often eventually propose rebuilding the initial, simple product, convinced they have discovered a profound insight.
The solution to this systemic madness is not to move slowly for the sake of stagnation, but to regain a sense of proportion. It requires the discipline to recognize that not every slowdown is a crisis, not every idea belongs on the roadmap, and not every tool needs to become a sprawling platform. By acknowledging that most software's ultimate goal is simply to be a useful tool, teams can avoid the self-destructive impulse to tinker with things that already function. True success lies in the ability to leave things alone when they are working, ultimately prioritizing utility over the endless cycle of neurotic innovation.
- 当团队与终端用户隔离,依赖项目经理等中间人传递需求时,软件开发就会脱节且低效。直接与用户接触可以提供关键的一手信息,帮助团队把精力放在那些能解决真实问题并降低摩擦的小改进上。
- 在企业环境中,问"我们到底要解决什么问题?"是一项重要却常被忽视的诊断工具。把问题明确记录下来并培养协作思维,可以减少不必要的摩擦,把注意力集中到核心目标上。
- 单靠原始分析数据来驱动产品决策,通常不如可用性研究有效。数据容易被断章取义以支撑既有偏见,而观察用户在界面上的真实困扰则能提供客观、直接且无法忽视的证据。
- 开发者有时害怕直接面对用户带来的阻力,但这种摩擦恰恰是确保产品有价值的必要反馈。缺乏互动往往意味着工作偏离了用户真实需求,或者开发者被错误的激励驱动。
- 与过去相比,当代软件行业面临更多技术动荡和复杂性。许多臃肿的团队架构关注的是管理依赖关系和频繁变化的技术栈,而不是解决底层领域问题。
- 存在一种常见的产品开发反模式:利益相关者对他们实际上不会亲自使用的假想功能给出低质量的正面反馈。真正的验证需要批判性思维和对实际使用场景的观察,而不是寻求表面的认可。
- 保持克制、抵制构建大而不当的平台或不必要功能的冲动,是一项被低估的工程能力。许多公司因过早追求扩展而受损,失去了对那些提供实际价值、但看起来"枯燥"的核心问题的关注。
- 在 B2B 环境中,臃肿复杂的软件往往比简单实用的替代品更占优势,因为买家更看重持续的服务、功能集或与供应商的关系,而非纯粹的软件效率。
- 行业中看似"疯狂"的现象往往只是典型企业动力的折射:无论领域或产品如何,官僚操控、争功和目标频繁变动都是常态。
- 归根结底,软件是为实现用户目标而存在的工具。当开发者忽视这一点,沉迷于内部复杂性、抽象指标或为了简历而开发时,就偏离了软件应有的实用价值。
讨论凸显了软件作为抽象、可扩展工程与解决真实用户问题之间的根本张力。大家达成的共识是:与终端用户的隔绝——不论由开发者自我造成,还是由管理层强制执行——是低效和挫败感的主要根源。参与者认为,虽然分析数据和项目管理有其用处,但它们常常只是薄弱的决策外壳,忽视用户体验,导致产品过度设计且使用率低下。最成功的做法,是对简洁性保持纪律性的承诺,并愿意直面用户行为的现实,即便这些反馈与内部假设或公司议程相冲突。
• Software development becomes detached and mentally taxing when teams are siloed from actual users, relying on intermediaries like project managers to convey requirements. Engaging directly with users provides vital grounding and helps focus efforts on small, friction-reducing changes that solve real problems.
• Asking "What problem are we trying to solve?" is a critical but often overlooked diagnostic tool in corporate environments. Explicitly documenting the problem and fostering a collaborative, team-based mindset can help reduce unnecessary intensity and focus on core objectives.
• Relying on raw analytics to drive product decisions is often inferior to usability research. Data can be misinterpreted to support existing biases, whereas observing a user struggle with an interface provides objective, undeniable context that is impossible to ignore.
• Developers sometimes fear direct user contact because it creates friction, but this friction is exactly what ensures a product remains valuable. A lack of interaction often suggests the work is disconnected from the user's actual needs or that the developers are focused on the wrong incentives.
• The modern software industry suffers from excessive technical churn and complexity compared to past eras. Much of the bloated team structure seen today is a result of managing dependencies and constantly shifting stacks rather than solving the underlying domain problems.
• There is a pervasive "Product Development Antipattern" where stakeholders offer low-signal, positive feedback based on hypothetical features they will never actually use. Real validation requires critical thought and observation of actual usage patterns rather than seeking approval.
• "Leaving things alone" and resisting the urge to build "platforms" or unnecessary features is an underrated engineering skill. Many companies suffer from a desire to scale or expand their scope prematurely, losing focus on the essential, "boring" problems that actually provide value.
• In B2B environments, bloated, complex software often outperforms simple, functional alternatives because the buyers prioritize ongoing service, features, or vendor relationships over pure software efficiency.
• The "insanity" observed in the industry is often just a reflection of standard corporate dynamics, where bureaucratic maneuvering, credit-seeking, and shifting goalposts occur regardless of the specific field or product being built.
• Ultimately, software is a tool meant to serve a user's goals. When developers lose sight of this and focus on internal complexity, abstract metrics, or resume-driven development, they drift away from the practical reality that makes software useful.
The discussion highlights a fundamental tension between the pursuit of software as an abstract, scalable endeavor and the grounded reality of solving actual user problems. There is a strong consensus that isolation from the end-user—whether self-imposed by developers or enforced by management layers—is a primary driver of inefficiency and frustration. Participants suggest that while analytics and project management have their place, they often serve as thin veneers for decision-making that ignores the human experience, leading to products that are over-engineered and under-utilized. Ultimately, the most successful approaches involve a disciplined commitment to simplicity and a willingness to confront the realities of user behavior, even when that feedback contradicts internal assumptions or corporate agendas.
Neki 是 PlanetScale 推出的全新分片式 Postgres 产品,旨在帮助团队突破单机扩展数据库的限制。凭借多年管理大规模 MySQL 集群的实战经验,PlanetScale 开发了 Neki,让用户能够将 Postgres 数据分布到多台机器,同时保持与标准 Postgres 驱动、 ORM 和连接字符串的兼容性。 Neki 在每个分片上都运行真实的 Postgres(而非自研存储引擎),因此能够完整保留现有扩展和 SQL 功能。 Neki is a new sharded Postgres offering from PlanetScale, designed to help teams overcome the limitations of scaling databases on single machines. Drawing on years of experience managing massive MySQL clusters, PlanetScale developed Neki to allow users to distribute their Postgres data across multiple machines while maintaining compatibility with standard Postgres drivers, ORMs, and connection strings. Because it uses real Postgres on every shard rather than a custom storage engine, it preserves full support for existing extensions and SQL functionality.
Neki 是 PlanetScale 推出的全新分片式 Postgres 产品,旨在帮助团队突破单机扩展数据库的限制。凭借多年管理大规模 MySQL 集群的实战经验,PlanetScale 开发了 Neki,让用户能够将 Postgres 数据分布到多台机器,同时保持与标准 Postgres 驱动、 ORM 和连接字符串的兼容性。 Neki 在每个分片上都运行真实的 Postgres(而非自研存储引擎),因此能够完整保留现有扩展和 SQL 功能。
Neki 的核心架构由四部分组成。 Neki routers 负责接收和路由流量,充当解析查询、生成分布式执行计划并汇总结果的网关;每个 shard 由一个主库和分布在不同可用区的多个副本构成,以保证高可用性;通过 sidecars 实现的智能连接池可实时监测各个 Postgres 实例的实际承载能力,从而更高效地调度流量;最后由 control plane 负责全局健康管理,协调故障转移、模式变更和数据重分片等操作。
用户通过 data topology 管理数据分布,这是一份用 shard keys 定义的 JSON 配置,用来把逻辑表映射到物理分片上。这样的灵活性让团队可以先采用标准的非分片 Postgres 部署,只有在性能成为瓶颈时再迁移到分片模型。平台将这些扩展操作作为在线内置工作流来处理,因此诸如 schema 更新或版本升级等通常需要大量停机的操作,用户可以在不中断应用的情况下完成。
除了分片能力外,Neki 还集成了 PlanetScale 的成熟功能,例如 database Insights 、自动架构建议和分支工作流,旨在为那些已超出单机限制但又不想放弃标准 Postgres 体验或自行管理复杂应用级分片的组织提供平滑的迁移路径。
Neki 目前处于平台预览阶段。公司鼓励用户了解其架构和功能,但建议在此阶段不要在关键生产负载上运行,因为可能会有破坏性变更。感兴趣的用户可以登录 PlanetScale 账号选择加入预览,并查阅文档获取有关集群设置与配置的详细技术说明。
Neki is a new sharded Postgres offering from PlanetScale, designed to help teams overcome the limitations of scaling databases on single machines. Drawing on years of experience managing massive MySQL clusters, PlanetScale developed Neki to allow users to distribute their Postgres data across multiple machines while maintaining compatibility with standard Postgres drivers, ORMs, and connection strings. Because it uses real Postgres on every shard rather than a custom storage engine, it preserves full support for existing extensions and SQL functionality.
The core architecture of Neki relies on four distinct components. Neki routers manage incoming traffic, acting as a gateway that parses queries, builds distributed plans, and aggregates results. Each shard consists of a primary database with multiple replicas across different availability zones to ensure high availability. To handle traffic efficiently, Neki utilizes intelligent connection pooling via sidecars that monitor the actual capacity of each Postgres instance. Finally, a control plane manages the health of the entire system, coordinating tasks like failovers, schema changes, and data resharding.
Users manage the distribution of their data through a data topology, which is a JSON configuration that maps logical tables to physical shards using defined shard keys. This flexibility allows teams to start with a standard, non-sharded Postgres deployment and transition to a sharded model only when performance needs demand it. Because the platform treats these scaling operations as online, built-in workflows, users can perform tasks that would otherwise require significant downtime, such as schema updates or version upgrades, without taking their application offline.
In addition to its sharding capabilities, Neki provides users with access to established PlanetScale features like database Insights, automated schema recommendations, and branching workflows. This integrated approach is intended to provide a seamless transition for organizations that are outgrowing the constraints of a single machine but do not want to sacrifice the standard Postgres experience or manage the complexity of manual application-level sharding.
Neki is currently available in a platform preview, and while the company encourages users to explore its architecture and capabilities, they advise against running critical production workloads on it during this phase due to the likelihood of breaking changes. Prospective users are invited to sign into their PlanetScale accounts to opt into the preview and consult the documentation for further technical details on how to set up and configure their clusters.
• Launch posts 应当立即阐明产品的核心价值和用途,以避免用户产生沮丧并提升可及性。
• 将 Neki 保持为私有软件的决定被视为一种战略必要,目的是防止 AWS 等云服务商将该技术商品化;这与 Google 因规模庞大而能够将 Vitess 开源形成鲜明对比。
• 公司领导层强硬的立场与对抗性的公开言论会疏远潜在用户,即便其底层技术被认为具有高质量或创新性。
• 对于评估像 Neki 这样的分布式系统的工程师来说,关于一致性保证、跨分片事务以及数据库约束处理的详尽技术文档至关重要。
• 将开源作为长期保障的需求,与小公司维护商业可行性的愿望之间存在明显张力。
• Neki 定位为从零开始实现的 Postgres,凭借团队在 Vitess 上的经验,提供竞争对手尚未具备或实现的在线分片重构等功能。
• 像交通广告这样的营销手段难以与技术内容的接受度直接比较,但清晰的信息传达仍是提升参与度的关键。
• 私有方案与开源方案的比较常常演变为围绕"防御性"私有许可的伦理问题与社区驱动基础设施优势的争论。
• 技术用户将关于架构权衡(尤其是 CAP theorem 限制)的透明文档视为采用新数据库技术的前提条件。
• 一些用户认为创业公司创始人对竞争对手采取激进行为会成为重要的威慑因素,无论产品本身有何优点。
围绕 Neki 发布的讨论折射出两者之间的巨大裂痕:一方面是对开放、可互操作基础设施的渴望,另一方面是初创公司为防止大型云厂商侵蚀其知识产权而不得不采取的商业保护需求。团队的技术背景虽然广受认可,但领导层对抗性的沟通风格常常掩盖产品本身,加剧了外界对公司动机和长期路线的怀疑。归根结底,潜在采用者仍然关注分片系统的技术权衡,并希望在目前被视为欠缺的初步文档中,看到关于一致性模型和架构保证的清晰说明。
• Launch posts should immediately clarify the core value proposition and purpose of the product to avoid user frustration and improve accessibility.
• The decision to keep Neki proprietary is framed as a strategic necessity to prevent cloud providers like AWS from commoditizing the technology, contrasting it with Google's ability to open-source Vitess due to its massive scale.
• Strong opinions and confrontational public discourse from company leadership can alienate potential users, even when the underlying technology is perceived as high-quality or innovative.
• Detailed technical documentation regarding consistency guarantees, cross-shard transactions, and handling of database constraints is essential for engineers evaluating distributed systems like Neki.
• There is a clear tension between the demand for open-source software as a safety measure for long-term planning and the desire of smaller companies to protect their commercial viability.
• Neki is positioned as a ground-up Postgres implementation, leveraging the team's historical experience with Vitess to provide features like online resharding that competitors currently lack or have not yet implemented.
• The effectiveness of marketing efforts, such as transit advertising, can be difficult to gauge against the reception of technical content, but clear messaging remains the most critical factor for engagement.
• Comparisons between proprietary and open-source alternatives often devolve into debates over the ethics of "defensive" proprietary licensing versus the benefits of community-driven infrastructure.
• Technical users prioritize transparent documentation of architectural trade-offs, particularly regarding CAP theorem constraints, as a prerequisite for adopting new database technologies.
• Some users view the aggressive posturing of startup founders toward competitors as a significant deterrent, regardless of the merits of the product being launched.
The conversation surrounding the launch of Neki reflects a significant divide between the desire for open, interoperable infrastructure and the business imperatives of startups trying to defend their intellectual property from larger cloud incumbents. While the technical pedigree of the team is widely respected, the confrontational communication style of the leadership often eclipses the product launch itself, fueling skepticism about the company's motives and long-term roadmap. Ultimately, potential adopters remain focused on the technical trade-offs of sharded systems, seeking clarity on consistency models and architectural guarantees that are currently perceived as lacking in the initial documentation.
The Cognition Team 推出了 SWE-2,这是他们迄今为止最先进的编码模型,旨在显著改善能力与成本之间的平衡。通过将强化学习扩展到万亿参数级别,SWE-2 在 FrontierCode 1.1 Main 基准测试中达到了 50.0% 的成功率。该性能使其接近当前的顶尖模型,同时成本比 Fable 5.1 等竞争选项低 64% 。该模型以 Kimi K3 为基础,经过大规模的后期训练以强化其代理式编码能力。 The Cognition Team has introduced SWE-2, their most advanced coding model to date, designed to significantly improve the balance between capability and cost. By scaling reinforcement learning to the multi-trillion-parameter regime, SWE-2 achieves a 50.0% success rate on the FrontierCode 1.1 Main benchmark. This performance places it near the current frontier models while maintaining a cost profile 64% cheaper than competing options like Fable 5.1. The model is built on the foundation of the Kimi K3 base model, which underwent extensive post-training to refine its agentic coding abilities.
The Cognition Team 推出了 SWE-2,这是他们迄今为止最先进的编码模型,旨在显著改善能力与成本之间的平衡。通过将强化学习扩展到万亿参数级别,SWE-2 在 FrontierCode 1.1 Main 基准测试中达到了 50.0% 的成功率。该性能使其接近当前的顶尖模型,同时成本比 Fable 5.1 等竞争选项低 64% 。该模型以 Kimi K3 为基础,经过大规模的后期训练以强化其代理式编码能力。
SWE-2 在解决问题的效率和工程判断力上都有提升。与前代 SWE-1.7 相比,新模型能更快聚焦代码库中的关键部分,减少过度探索和重复读取代码,从而用更少的步骤就能开始实现,大幅降低每个任务的平均成本。此外,SWE-2 在编写端到端测试方面更可靠,也更善于变通:它能利用现有数据绕过受阻路径,而不只是照搬静态指令。
SWE-2 的一项核心技术创新是在强化学习过程中采用 Pareto-informed cost penalties 。团队在一次训练中同时覆盖所有推理努力级别,并根据基础模型的成本 - 性能曲线斜率调整惩罚,从而成功优化出整个权衡前沿。这一方法保证了模型在处理简单任务时具有成本效益,同时在面对更复杂的挑战时保持高强度的复杂规划能力。为支持该策略,团队还引入了基于长度加权的奖励基线,以减小梯度方差、提升训练稳定性。
训练基础设施也进行了优化,优先提升吞吐量并尽量减少推理与训练之间的不匹配。团队整合了在线草稿模型训练,并采用诸如 FP8 kernels 的低精度、量化感知方法以高效管理内存。这些改进带来了更稳定的训练过程,使模型在不显著增加延迟的前提下保持高性能。数据质量同样被高度重视:通过扩展 RL environments 并实施递归飞轮机制,不断增强验证器以防止奖励操纵。
在可信性与对齐方面,团队对 SWE-2 在宣传、审查和对上下文依赖表述的脆弱性等方面进行了评估。模型表现良好,在政治敏感提示上的通过率达到 98%,且无论用户如何表述或使用何种语言,都未表现出统计学上显著的偏见或脆弱性。 SWE-2 已通过 Devin Desktop 应用、命令行工具和 Web 平台向用户提供,这是将顶尖编码代理变得更强大且更易获取的重要一步。
The Cognition Team has introduced SWE-2, their most advanced coding model to date, designed to significantly improve the balance between capability and cost. By scaling reinforcement learning to the multi-trillion-parameter regime, SWE-2 achieves a 50.0% success rate on the FrontierCode 1.1 Main benchmark. This performance places it near the current frontier models while maintaining a cost profile 64% cheaper than competing options like Fable 5.1. The model is built on the foundation of the Kimi K3 base model, which underwent extensive post-training to refine its agentic coding abilities.
The intelligence of SWE-2 is characterized by more efficient problem solving and improved engineering judgment. Compared to its predecessor, SWE-1.7, the new model reduces over-exploration and redundant code reads by focusing more quickly on the critical parts of a codebase. This allows SWE-2 to begin implementation in fewer steps, significantly lowering the average cost per task. Furthermore, the model demonstrates enhanced reliability in writing end-to-end tests and exhibits greater resourcefulness by navigating around blocked paths using available data, rather than simply relying on static instructions.
A central technical innovation in SWE-2 is the use of Pareto-informed cost penalties during the reinforcement learning process. By training all reasoning-effort levels in a single run with penalties tuned to the slope of the base model's cost-performance curve, the team successfully optimized the entire trade-off frontier. This principled approach ensures that the model provides cost-effective performance for simple tasks while maintaining high-effort, complex planning capabilities for more difficult challenges. To support this, they also implemented a length-weighted reward baseline that reduces gradient variance and promotes stability throughout the training phase.
The training infrastructure for SWE-2 was refined to prioritize throughput and minimize inference-training mismatches. The team integrated online draft-model training and utilized low-precision, quantization-aware methods, such as FP8 kernels, to manage memory usage efficiently. These improvements allowed for a more stable training process, resulting in a model that maintains high performance without significantly increasing latency. Data quality was similarly prioritized through the expansion of RL environments and the implementation of a recursive flywheel that continuously hardens verifiers against reward hacking.
Finally, the team evaluated SWE-2 on its trustworthiness and alignment, specifically regarding propaganda, censorship, and vulnerability to context-dependent framing. The model performed strongly, achieving a 98% pass rate on politically sensitive prompts while showing no statistically significant bias or vulnerability regardless of the user's framing or the language used. SWE-2 is currently available for users through the Devin Desktop application, command-line interface, and web-based platforms, marking a significant step forward in making frontier-level coding agents both more capable and accessible.
有人质疑 Terminal Bench 2.1 与 Terminal Bench 4 之间出现的巨大性能下滑,观察者认为该模型可能被"benchmaxxed",即为了在特定指标上取得高分而优化,而非体现通用智能。
支持者则认为,这种差距只是因为旧版本在基准测试上出现了饱和现象,并指出即便是顶级模型在更新、更困难的测试中也会出现类似下滑。
业界普遍认为,各公司有意设计模型和基准,以制造利于营销的成绩,从而形成一个"benchmaxxing"的循环,削弱了这些指标作为现实世界参考的有效性。
人们对 closed-weight 模型的必要性越来越怀疑,像 DeepSeek Flash 4.1 这样的廉价 open-weight 替代品展现出了有竞争力的性能,并为用户提供了更多控制权。
采用过程中的摩擦仍然是一个重大障碍,用户对被迫改变既有开发流程、使用专有 CLI 和定制平台表示不满。
关于 Cognition 能否长期生存,外界仍持怀疑态度。有人指出其早期编码 agent 性能欠佳,并对其通过封装现有强大模型来经营的商业模式表示担忧。
一些专业开发者通过大量 agentic 自动化实现了显著的生产力提升,他们能够将复杂系统任务交给 AI,从而质疑传统手工开发的长期地位。
"Pareto frontier"这一术语常被用来为设计权衡背书,反映出竞争性编程和算法专长在当前 AI 工程文化中的影响力。
市场动态显示,随着 frontier models 日益商品化,公司的核心价值正从托管模型转向提供集成的 agentic 工作流,但用户仍警惕被锁定在专有生态中。
对于一些 AI 初创公司的高估值和 vaporware 性质,外界普遍抱持愤世嫉俗的态度——观察者指出,由于无法公开获得 weights,验证其性能声明变得极为困难。
这次讨论反映了整个行业在频繁且常受营销驱动的新模型发布与软件工程师对稳健、实用工具的真实需求之间的深刻矛盾。尽管部分用户已成功将 agentic 工作流整合进高层系统架构,许多人仍对 benchmaxxing 、 closed-weight 模型以及不同实验室间缺乏互操作性持怀疑态度。总体共识是,作为营销工具的基准指标正变得越来越不可靠,市场正倾向于灵活、低成本且 open-weight 的解决方案,而非封闭的 black box 平台。
• Skepticism exists regarding the massive performance drop between Terminal Bench 2.1 and Terminal Bench 4, with observers suggesting the model is "benchmaxxed" to perform well on specific metrics rather than showing generalized intelligence.
• Proponents argue that the performance gap is simply due to benchmark saturation in older versions, noting that even top-tier models exhibit similar drops on newer, more difficult tests.
• There is a pervasive belief that companies intentionally design models and benchmarks to create marketing-friendly performance data, leading to a "benchmaxxing" cycle that degrades the utility of these metrics as real-world indicators.
• The necessity for closed-weight models is increasingly questioned, as cheaper, open-weight alternatives like DeepSeek Flash 4.1 show competitive performance and provide users with more control.
• Friction remains a significant barrier for adoption, as users express frustration with proprietary CLIs and bespoke platforms that force a shift in established development workflows.
• Skepticism regarding the viability of Cognition as a company persists, citing historical performance issues with their early coding agents and concerns over their business model of wrapping existing, capable models.
• Some professional developers are already achieving significant productivity gains through heavy agentic automation, enabling them to offload complex system tasks to AI while questioning the long-term state of traditional manual development.
• The term "Pareto frontier" is frequently used to justify design trade-offs, reflecting the influence of competitive programming and algorithmic expertise in the current AI engineering culture.
• Market dynamics suggest that as frontier models become commodities, the primary value for companies will shift from hosting the model to providing integrated agentic workflows, though users remain wary of becoming locked into proprietary ecosystems.
• There is a broader cynicism regarding the high valuations and "vaporware" nature of some AI startups, with observers noting that the lack of open access to weights makes it difficult to verify performance claims.
The discussion reflects a deep industry-wide tension between the rapid, often marketing-driven release of new AI models and the practical, grounded needs of software engineers. While some users are successfully integrating agentic workflows into high-level system architecture, many others remain skeptical of "benchmaxxing," closed-weight models, and the lack of interoperability between different lab environments. Ultimately, the consensus suggests that performance metrics are becoming less reliable as marketing tools, and the market is trending toward a preference for flexible, cost-effective, and open-weight solutions over proprietary "black box" platforms.
一项由 NASA 开发、最初用于分析 Martian 表面的创新成像技术,正成为考古学家研究地球上古老岩画的变革性工具。这种被称为 decorrelation stretch 的处理手段,最早由 Jet Propulsion Laboratory 的研究人员在 1978 年开发,旨在增强高度相关的卫星影像。与单纯提高对比度不同,该方法通过将原始颜色映射到更宽的范围,揭示出肉眼难以察觉的细微纹理和信息。 An innovative NASA imaging technique, originally designed to analyze the Martian surface, is proving to be a revolutionary tool for archaeologists studying ancient rock art on Earth. The process, known as decorrelation stretch, was first developed by researchers at the Jet Propulsion Laboratory in 1978 to enhance high-correlation satellite imagery. By mapping original colors to an expanded range rather than simply increasing contrast, the method reveals intricate details that are otherwise invisible to the naked eye.
一项由 NASA 开发、最初用于分析 Martian 表面的创新成像技术,正成为考古学家研究地球上古老岩画的变革性工具。这种被称为 decorrelation stretch 的处理手段,最早由 Jet Propulsion Laboratory 的研究人员在 1978 年开发,旨在增强高度相关的卫星影像。与单纯提高对比度不同,该方法通过将原始颜色映射到更宽的范围,揭示出肉眼难以察觉的细微纹理和信息。
考古学家 Jon Harman 在看到火星图像后发现了这项技术的潜力,他意识到该算法可以改用于历史研究。 Harman 利用 Karhunen.Loève Transform(一种用于在数字信号处理中实现能量压缩最大化的统计工具)开发了 Dstretch 插件。凭借医学影像的背景和数学博士学位,他将 decorrelation stretch 方法针对不同色彩空间进行了调整,使其成为识别褪色或被覆盖的历史颜料的高效工具。
这项技术对考古学领域产生了深远影响。研究人员借助该插件在全球范围内识别出数百幅此前未被记录的图像:从在古老 Egyptian 墓地中显现出的动物图像,到揭示 Canada 战士留下的战术象形符号,软件为学者提供了关于古代文化习俗和被遗忘艺术传统的新见解。
随着越来越多的研究者使用 Dstretch,他们不断发掘出该软件的新用途。通过调整数字图像中的特定颜色参数,考古学家可以分离出不同的颜料层,如同剥开时间的层叠,重现被掩盖的历史叙事。这种太空探索技术与人类历史研究之间的意想不到的跨界融合,凸显了跨学科创新为我们共同过去带来的深刻新视角。
An innovative NASA imaging technique, originally designed to analyze the Martian surface, is proving to be a revolutionary tool for archaeologists studying ancient rock art on Earth. The process, known as decorrelation stretch, was first developed by researchers at the Jet Propulsion Laboratory in 1978 to enhance high-correlation satellite imagery. By mapping original colors to an expanded range rather than simply increasing contrast, the method reveals intricate details that are otherwise invisible to the naked eye.
Archaeologist Jon Harman, who discovered the potential of this technology after seeing images of the red planet, recognized that the algorithm could be adapted for historical research. By applying the Karhunen.Loève Transform, a statistical tool for maximizing energy compaction in digital signals, Harman created the Dstretch software plug-in. His background in medical imaging and his PhD in mathematics allowed him to tailor the decorrelation stretch method to various color spaces, making it a highly effective tool for identifying faded or obscured historical pigments.
The impact of this technology on the field of archaeology has been significant. Researchers have used the plug-in to identify hundreds of previously undocumented figures across the globe. From uncovering images of animals in ancient Egyptian cemeteries to revealing tactical pictographs left by warriors in Canada, the software has provided scholars with new insights into ancient cultural practices and forgotten artistic legacies.
As practitioners continue to use Dstretch, they are constantly finding new applications for the software. By adjusting specific color parameters within the digital images, archaeologists can isolate different pigments, effectively peeling back the layers of time to reveal hidden narratives. This unexpected crossover between space exploration technology and human history highlights how cross-disciplinary innovation can provide profound new perspectives on our collective past.
本次讨论聚焦于去相关拉伸及相关图像处理技术的变革潜力,能够揭示以往人眼无法察觉的数据。参与者不仅停留在理论层面,还探讨了在易用软件中的实际工作流程,强调信号处理在从地质学到考古学等诸多领域里都是强有力的解读工具。虽然有人对专业工具的可及性感到沮丧,但大家对通过移动应用和网页演示普及这些方法普遍抱有热情。最终,对话强调了跨学科技术转移(例如从航空航天传感器到历史保护)所能带来的重大实际价值,而这种推动往往源于个人热情,而非机构指令。
• Decorrelation stretching and false-color composites are powerful techniques for revealing data hidden in imagery by processing signals outside the human visual range.
• The process functions by mapping non-canonical light bands, such as infrared, to visible colors, allowing for the isolation of specific features like vegetation or mineral patterns.
• Practical implementation is possible in standard image editors like GIMP or Photoshop by performing level adjustments within the LAB color space, which separates luminance from chrominance data.
• While these methods are successful in academic and professional remote sensing, hobbyists often encounter difficulty when applying them to field archaeology or rock art, where results can be inconsistent.
• Beyond archaeology, the technique is effective for recovering faded historical text, such as ghost signs on older buildings, by amplifying subtle color differences.
• Similar approaches like Eulerian Video Magnification demonstrate how digital signal processing can uncover invisible patterns, such as faint physical movements or color changes, acting as a functional "superpower."
• The technology highlights a persistent gap between advanced scientific research and accessible, real-world application, often requiring self-funded individuals to bridge the divide.
• Current implementations range from mobile applications meant for quick field analysis to complex plugins that provide the granular control necessary for scientific research.
• Historical interpretation of artifacts is frequently speculative, yet the sheer physical effort required to create ancient rock art implies a deep, intentional commitment regardless of the specific purpose.
• Space-based imaging technologies serve as a poignant counter-argument to criticisms regarding space exploration funding, as weather satellite data provides massive, tangible benefits to global agriculture and disaster mitigation.
The discussion centers on the transformative potential of decorrelation stretching and related image-processing techniques to reveal data previously obscured to the human eye. Participants move beyond theoretical appreciation to explore practical workflows in accessible software, emphasizing that signal processing acts as a powerful puzzle-solving tool in fields ranging from geology to archaeology. While some contributors express frustration with the accessibility of specialized tools, there is a collective enthusiasm for the democratization of these methods via mobile apps and web-based demonstrations. Ultimately, the conversation underscores how cross-disciplinary technology transfer—from aerospace sensors to historical preservation—yields significant practical value, often initiated by individual passion rather than institutional mandate.
保存旧且常常神秘的科技线缆这种普遍困扰,出人意料地让人感同身受。很多人囤着多年未用的电线,抱着某天可能用得上的模糊希望不肯丢弃。 Tyler Gaw 的一句话为这种习惯提供了理由:当你终于用上一根保存了十多年的电缆时,就足以证明你从未扔掉它们是正确的。 The universal struggle of maintaining a collection of old, often mysterious technology cables is a surprisingly relatable experience. Many people keep a hoard of cords that haven't been used in years, held onto with the vague hope that they might one day be needed. This common habit recently gained validation through a sentiment shared by Tyler Gaw, who emphasized that the day you finally find a use for a cable you have kept for over a decade is the ultimate justification for never discarding your collection.
保存旧且常常神秘的科技线缆这种普遍困扰,出人意料地让人感同身受。很多人囤着多年未用的电线,抱着某天可能用得上的模糊希望不肯丢弃。 Tyler Gaw 的一句话为这种习惯提供了理由:当你终于用上一根保存了十多年的电缆时,就足以证明你从未扔掉它们是正确的。
这话打动了 Jim Nielsen,他决定把对这堆线缆的坚持正式化。他的盒子被妻子亲切地标注为 FAMILY TECHNO BOX,成了一个用来彰显这些"旧物"价值的新项目的核心。他把那条主张保留此类盒子的社交媒体帖子打印出来,用包装胶带贴在盒子正面,把这个存放容器变成了未雨绸缪的证据。
现在每次往箱里再塞进一根电缆,贴在盒子上的那段话都会提醒他:这些东西是有意保存的,而不是杂乱无章。它既带给他一丝快乐和动力,也能阻止家里人想把箱子清空的念头。
从长远看,这也是留给后代的一个"遗产"。他希望当孩子们某天在阁楼里翻出这些物品时,能理解这份收藏的意义——既俏皮又真诚地向那种能让小配件在过时后仍然派上用场的远见致敬。
The universal struggle of maintaining a collection of old, often mysterious technology cables is a surprisingly relatable experience. Many people keep a hoard of cords that haven't been used in years, held onto with the vague hope that they might one day be needed. This common habit recently gained validation through a sentiment shared by Tyler Gaw, who emphasized that the day you finally find a use for a cable you have kept for over a decade is the ultimate justification for never discarding your collection.
This advice struck a chord with Jim Nielsen, who decided to formalize his commitment to his own collection. His box, affectionately labeled by his wife as the FAMILY TECHNO BOX, became the focus of a new project meant to honor the utility of these saved items. By printing out the original social media post advocating for the preservation of these boxes, he transformed his storage container into a testament of preparedness.
The process involved printing the message and affixing it directly to the front of the box with packing tape. Now, every time he adds another cable to the pile, he is greeted by a reminder that his decision to keep them is purposeful rather than clutter-prone. It provides him with a sense of joy and motivation while simultaneously serving as a deterrent for any family members who might consider cleaning out the box.
Ultimately, this act serves as a legacy for the future. By preserving the box and its manifesto, he hopes that when his children eventually discover his belongings in the attic, they will understand the importance of the collection. It is a playful yet sincere nod to the foresight required to keep gadgets functional long after they have fallen out of fashion.
- 管理线缆最有效的方法是分组,这有助于识别重复线并促使清理:并排放着十根相同的线缆会更容易让人扔掉多余的那几根。
- 用透明的可重复密封袋分别装不同类别的线缆(USB-A 、 USB-C 、 Audio 等)非常有效,既能防止缠结,又能保持可见性,不必频繁重新缠绕。
- 按功能(如速度、供电能力或针对特定设备的用途)给线缆和袋子做标记至关重要,这能避免日后排查连接故障或性能问题时的困扰。
- 正确的捆绑方式也很重要:用可重复使用的魔术贴绑带或发圈代替一次性的扎带,更利于长期存放,也不会损伤线缆外皮或制造不必要的浪费。
- CD 盘筒是一种巧妙且可堆叠的线缆存放方案;当线缆数量超过小盒子容纳量时,带标签的抽屉或储物箱能提供更稳健的组织方式。
- 处理模块化电源线(modular power supply cables)时要格外小心,即便同一制造商的线缆,针脚定义(pinouts)也可能不同,接错线可能造成硬件永久性损坏。
- 来自旧设备的专用、专有线缆通常应优先保留,因为只要硬件仍在使用,这类线缆往往难以替代,和容易补货的商品化线缆不同。
- 塑料袋理论上可能产生静电,损害敏感电子,因此有人更倾向于用带硅胶干燥包的铝箔防潮袋来长期保存适配器或专用组件。
- "及时获取"(just-in-time)与"以防万一"(just-in-case)的讨论凸显了极简生活方式与在技术排查中保持自给自足之间的张力。保留一套经过筛选且标记清楚的备用线缆,通常能在项目进行中节省时间并维持工作流。
- 定期清理是防止线缆堆积难以处理的必要措施,许多线缆最终会过时或退化,成为存储的负担而非真正的资源。
这场讨论反映了一个常见的技术经验:线缆的累积既是工具的来源,也会带来组织上的焦虑。关于分组和标记的有效性有广泛共识,许多人建议用拉链袋(如 ziploc)和基于储物箱 / 收纳箱的系统,代替把所有东西堆进一个"混乱杂物箱"的做法。虽然有人认为现代快速且廉价的物流让囤积变得不再必要,但也有人强调保留那些难以替代的遗留接口(legacy connections)在排查旧硬件故障时的价值。总的来说,成功的管理在于平衡:剔除冗余的商品化线缆,同时有选择地保留在日益专有化的环境中仍能提供实际价值的稀有专用线缆。
• Managing cables is best achieved through grouping, which helps identify duplicates and encourages purging, as seeing ten identical cables side-by-side makes it easier to discard the excess.
• Utilizing clear, resealable baggies for different cable categories (USB-A, USB-C, Audio, etc.) is a highly effective way to prevent tangles and maintain visual access without needing to constantly re-wrap cords.
• Labeling cables and bags by capability (e.g., speed, power, or specific device use) is essential to avoid the frustration of troubleshooting non-functional or underperforming connections later.
• Proper bundling techniques, such as using reusable Velcro straps or hair ties instead of permanent zip ties, make it easier to manage long-term storage without damaging cable jackets or creating unnecessary waste.
• CD spindles serve as a clever, stackable storage solution for cables, while dedicated drawers or labeled bins allow for more robust organization once a collection scales beyond a simple box.
• Caution is required with modular power supply cables, as pinouts are not standardized even within the same manufacturer, and using the wrong cable can cause permanent hardware damage.
• Specialized, proprietary cables from older technology should often be prioritized for retention, as they can become impossible to replace if the hardware remains in use, unlike commodity cables that can be easily repurchased.
• Static electricity in plastic bags can theoretically damage sensitive electronics, leading some to prefer aluminized, moisture-barrier bags with silica gel packets for long-term storage of adapters or specialized components.
• The "just-in-time" vs. "just-in-case" debate highlights a tension between minimalist living and the desire to remain self-sufficient in technical troubleshooting; keeping a curated, labeled stash often saves time and flow during projects.
• Periodic culling is necessary to prevent cable accumulation from becoming overwhelming, as many cables eventually become obsolete or degrade, making them more of a storage burden than a practical resource.
The discussion reflects a common technical experience where the accumulation of miscellaneous cables serves as both a source of utility and significant organizational anxiety. A strong consensus exists around the effectiveness of grouping and labeling, with many advocating for ziploc bags and bin-based systems to move away from the chaotic, single "junk box" approach. While some participants argue that modern logistics and the ubiquity of cheap, fast shipping make hoarding obsolete, others emphasize the value of having specific, hard-to-find legacy connections on hand for troubleshooting older hardware. Ultimately, successful management appears to involve a balance: culling redundant commodity items while thoughtfully preserving rare, specialized cables that provide genuine utility in an increasingly proprietary world.
Shopify 宣布其移动工程战略发生重大转变:公司将放弃长期使用的 React Native,转而采用 Swift 与 Kotlin 进行原生开发。尽管 2020 年采用 React Native 在开发效率和功能一致性方面取得了显著成效,但编码代理与大型语言模型(LLM)的快速发展已从根本上改变移动开发的成本结构。由于 AI 现在能有效负责跨两个平台的功能翻译、实现与测试,以往需要"重复构建"的负担不再是决定性障碍。 Shopify has announced a significant shift in its mobile engineering strategy, moving away from its long-standing commitment to React Native in favor of native development with Swift and Kotlin. While the company's 2020 decision to adopt React Native was highly successful in terms of developer efficiency and feature parity, the rapid advancement of coding agents and Large Language Models has fundamentally altered the economics of mobile development. Because AI can now effectively manage the translation, implementation, and testing of features across two separate platforms, the traditional burden of building twice is no longer a disqualifying factor.
Shopify 宣布其移动工程战略发生重大转变:公司将放弃长期使用的 React Native,转而采用 Swift 与 Kotlin 进行原生开发。尽管 2020 年采用 React Native 在开发效率和功能一致性方面取得了显著成效,但编码代理与大型语言模型(LLM)的快速发展已从根本上改变移动开发的成本结构。由于 AI 现在能有效负责跨两个平台的功能翻译、实现与测试,以往需要"重复构建"的负担不再是决定性障碍。
此次回归原生源于对移动技术栈的原则性重新评估。尽管 React Native 仍是强大的框架,Shopify 认为原生开发能更好地利用平台特有能力与官方工具。借助 AI 代理承接大量编码工作,团队可以在不再承担过去高额维护成本的前提下,享受原生带来的性能与稳定性。
为推动这一转型,Shopify 对其核心应用(如 Shop 与主 Shopify app)采取 greenfield 路线。工程团队并非缓慢渐进迁移,而是借助名为 Helix 的专用系统,以结构化反馈循环推进:代码以小而可验证的检查点构建,每一段在继续之前都必须通过严格测试、视觉审查和对抗性代码分析。该流程确保最终代码库可维护、高质量且稳健。
迁移的关键环节之一是通过将业务逻辑与用户界面解耦来提升速度。构建可通过命令行以 headless 方式运行的架构,使 AI 代理能够在毫秒级而非分钟级完成测试与迭代,消除了传统模拟器交互的瓶颈,从而让代理自主且高效地工作。该架构既支持人类开发者也支持 AI,确保新的原生应用在长期内易于更新与维护。
在开源 React Native 库的支持上,Shopify 也在调整:React Native Skia 将过渡到社区主导,行业广泛使用的 FlashList 在 Shopify 寻找长期维护方期间仍由公司继续提供关键维护,Restyle 库则计划于 2026 年底归档。整个过渡过程将保持透明,以尽量减少对依赖这些工具的开发者社区的影响。
Shopify has announced a significant shift in its mobile engineering strategy, moving away from its long-standing commitment to React Native in favor of native development with Swift and Kotlin. While the company's 2020 decision to adopt React Native was highly successful in terms of developer efficiency and feature parity, the rapid advancement of coding agents and Large Language Models has fundamentally altered the economics of mobile development. Because AI can now effectively manage the translation, implementation, and testing of features across two separate platforms, the traditional burden of building twice is no longer a disqualifying factor.
The decision to migrate back to native stems from a first-principles reevaluation of the company's mobile tech stack. While React Native remains a strong framework, Shopify determined that native development offers superior access to platform-specific capabilities and first-party tooling. By utilizing AI agents to handle the heavy lifting of coding, the team can enjoy the benefits of native performance and stability without incurring the historical maintenance costs that once made building for each platform separately prohibitive.
To facilitate this transition, Shopify is implementing a greenfield approach for its major applications, such as Shop and the main Shopify app. Rather than performing a slow, gradual migration, the engineering team is utilizing a specialized system called Helix. This tool operates within a structured feedback loop where code is built in small, verifiable checkpoints. Each segment must pass rigorous testing, visual review, and adversarial code analysis before moving forward. This process ensures that the resulting codebase remains maintainable, high-quality, and robust.
A critical component of this migration involves optimizing for speed by decoupling business logic from the user interface. By building architectures that can run headlessly via a Command Line Interface, engineers allow AI agents to test and iterate on code in milliseconds rather than minutes. This strategy removes the bottleneck of traditional simulator interaction, enabling agents to work autonomously and efficiently. This architecture is designed to support both human developers and AI, ensuring that the new native apps remain easy to update and manage in the long term.
As part of this shift, Shopify is adjusting the support for its popular open-source React Native libraries. React Native Skia will be transitioned to a community-led model, while FlashList—a tool used widely across the industry—will see Shopify continue to provide critical maintenance while the company searches for a long-term steward. Meanwhile, the Restyle library will be archived at the end of 2026. This transition is being handled with transparency to ensure minimal disruption for the broader developer community that relies on these tools.
• 大型科技公司在重新评估 "React Native vs. Native" 的利弊,有些公司认为如今依靠 Coding agents 维护独立的 Swift(iOS)和 Kotlin(Android)代码库,在经济上可行、技术上也更优。
• Coding agents 使开发者能把实现功能对等视为一个可自动化的任务,而非纯粹的人力负担,核心挑战由编写代码转向定义严格的规范、测试和审查闭环。
• 选择回归 Native 常源自想摆脱 React Native 的"upstream tax",即频繁的大幅变动、库的不稳定性,以及最终不得不"drop into native"以解决性能瓶颈。
• 人们特别担心长期的"divergence cost",因为功能对等不仅是初次实现,还要求多年内在行为、边缘情况和不断演进的操作系统特性上保持一致。
• 也有人指出,用来构建 Native 应用的同类 AI agents 同样可以改善 React Native 的开发体验,这暗示迁移可能更多源于对框架的疲惫,而非绝对的技术必要性。
• 依赖第三方 coding models 带来一种新的战略依赖:用对未来模型成本、可用性和知识产权保护的不确定性,替代了以往对框架的依赖。
• "vibe-coding"(在缺乏充分人工审查下生成应用)引发激烈争论,资深工程师警告这容易引入静默错误、竞态条件和维护债务,一旦 AI 原始生成的上下文丢失,很少有人能理解或修复这些债务。
• 对于小公司或资源受限的团队,React Native 或其他跨平台框架通常仍更务实,因为它们能在不构建复杂 agentic 基础设施来同步多条 Native 技术栈的情况下,提供更高的杠杆。
• 与其纠结于框架本身,架构设计变得更为关键,尤其是把业务逻辑与 UI 分离,这既利于测试,也让 AI agents 更容易通过 CLI 操作代码库。
• 争论的焦点在于这是否可持续:这是长期的工程策略转变,还是由廉价 token 的短期可用性和管理层对 greenfield 项目的偏好所推动的潮流?
向 Native 回归反映了一种更广泛的转型:AI agents 降低了代码生成与维护的成本,使组织能够优先考虑特定平台的性能与稳定性,而不再一味追求过去十年盛行的 "write once, run anywhere"。尽管资源充足的大型组织押注于 agentic workflows 来自动化多栈功能对等的维护负担,批评者警告这种做法会忽视分歧带来的复合成本,以及缺乏人工监督的 AI 生成代码潜藏的风险。总体而言,行业正在质疑跨平台抽象是扩展的唯一路径,这可能预示着像 Electron 和 React Native 这样的臃肿生态有被边缘化的风险,前提是技术架构和测试框架足够稳健,能够支持自动化的长期维护。
• Large tech companies are re-evaluating the "React Native vs. Native" tradeoff, with some concluding that coding agents now make maintaining separate Swift (iOS) and Kotlin (Android) codebases economically viable and technically superior.
• Coding agents allow developers to treat feature parity as an automation problem rather than a manual labor burden, shifting the primary challenge from writing code to defining rigid specifications, tests, and review loops.
• The decision to move back to native is often driven by a desire to escape the "upstream tax" of React Native—specifically, dealing with frequent breaking changes, library instability, and performance bottlenecks that require "dropping into native" anyway.
• A significant concern is the "divergence cost" over time, as feature parity involves more than just initial implementation; it requires maintaining consistent behavior across analytics, edge cases, and evolving OS platform features over years.
• Some argue that the same AI agents used to build native apps could just as easily improve the React Native experience, suggesting that this migration might be more about framework fatigue than an absolute technical mandate.
• Relying on third-party coding models creates a new form of strategic dependency, replacing old framework dependencies with uncertainty regarding future model costs, availability, and intellectual property protection.
• The "vibe-coding" approach—generating apps without full manual review—is heavily contested, with experienced engineers warning that it risks introducing silent bugs, race conditions, and maintenance debt that few developers will understand once the original AI-generated context is lost.
• For smaller companies or resource-constrained teams, React Native or other cross-platform frameworks often remain the more pragmatic choice, as they provide high leverage without requiring the sophisticated agentic infrastructure needed to keep multiple native stacks in sync.
• Architecture is becoming more critical than the choice of framework, specifically the move toward isolating business logic from UI, which allows for better testing and makes it easier for AI agents to operate on the codebase via CLI.
• There is significant skepticism regarding whether this shift is a sustainable long-term engineering strategy or merely a trend fueled by temporary access to cheap tokens and management's preference for "greenfield" projects over tedious maintenance.
The shift back to native development reflects a broader transition where AI agents lower the cost of code generation, allowing organizations to prioritize platform-specific performance and stability over the "write once, run anywhere" efficiency of the previous decade. While large organizations with sufficient resources are betting that agentic workflows can automate the burden of maintaining feature parity across multiple stacks, critics warn that this strategy ignores the compounding costs of divergence and the hidden risks of AI-generated code that lacks human oversight. Ultimately, the industry is moving away from the assumption that cross-platform abstraction is the only way to scale, signaling a potential decline for bloated ecosystems like Electron and React Native in favor of native implementation, provided that technical architecture and testing frameworks are sufficiently robust to support automated maintenance.
284 comments • Comments Link
一架 B767 货机在 Miami 附近发生事故,表现为一系列飞行技术和决策上的严重失误。最明显的问题是:尽管进近明显不稳定,机组仍拒绝执行强制复飞(go-around)。
机组未能达到安全着陆的既定标准,包括速度过快、襟翼配置错误、未能保持正确的下滑道(glideslope),并在多次警告下继续进近。旨在授权下属质疑上级并在紧急情况下接管驾驶的 Crew Resource Management(CRM)原则在该驾驶舱内被忽视或失效。
过高的空速和在地面效应(ground effect)中产生的"浮动"导致主起落架未受压,阻止了自动扰流板(automatic spoilers)和刹车等关键安全系统的激活,从而大大增加了减速难度。最后几秒钟内虽尝试发起复飞,但随后又中止,导致灾难性的跑道偏出(runway excursion);专家指出,在放弃复飞前,发动机没有足够时间加速到全推力。
专业共识认为,这起事故反映的是基本飞行纪律和情境意识(situational awareness)的全面失败,而非对机型不熟悉所致。事故也引发了关于企业压力是否会促使飞行员把燃油效率或准点率放在安全之前的讨论,尽管业内人士坚持安全应始终优先。
FAA 的监管和 NTSB 的调查等制度性框架用于追究航空公司与机组责任,以防止"偏差常态化"(normalization of deviance)。自动化驾驶舱系统和强制复飞阈值本意在预防此类后果,但自负、疲劳以及"急于到达目的地"(get-there-itis)等因素仍构成重大风险。航空专家强调,复飞是标准且无惩罚性的程序,只要进近不稳定,无论军衔或可能造成的延误,都应立即执行。
航空界普遍认为,此次事故是飞行技能的彻底失败,由一系列在飞机尚未接近跑道前就已开始的鲁莽决策推动。与其归咎于对机型的不熟悉,不如把焦点放在忽视稳定进近标准(stabilized approach criteria)及在下属未能质疑机长危险行为的驾驶舱文化中潜在的灾难性后果。尽管关于企业影响或疲劳的推测存在,但主要共识是:机组拒绝执行复飞——这一基本且被普遍接受的操作——是导致这场悲剧的核心因素。 • A B767 cargo aircraft accident near Miami was characterized by a series of critical errors in airmanship and decision-making, most notably the refusal to perform a mandatory go-around despite an unstabilized approach.
• The flight crew failed to meet established criteria for a safe landing, including excessive speed, incorrect flap configuration, and failing to maintain a proper glideslope, yet continued the approach despite multiple warnings.
• Crew Resource Management (CRM) principles, which are designed to empower subordinates to challenge superiors and take control during emergencies, were ignored or proved ineffective in this cockpit.
• The lack of weight on the main landing gear, caused by excessive airspeed and "floating" in ground effect, prevented the activation of critical safety systems like automatic spoilers and brakes, significantly complicating the attempted deceleration.
• An attempt to initiate a go-around in the final seconds was aborted shortly after, leading to a catastrophic runway excursion; experts suggest the engines lacked the time to spool up to full thrust before the attempt was abandoned.
• The professional consensus suggests this was a failure of basic aviation discipline and situational awareness rather than a lack of familiarity with the specific aircraft type.
• The incident has sparked debate regarding the potential for corporate pressure on pilots to prioritize fuel efficiency or on-time performance, though industry professionals maintain that safety should always supersede such considerations.
• Regulatory frameworks like the FAA's oversight and NTSB investigations exist specifically to hold carriers and crews accountable, ensuring that patterns of "normalization of deviance" do not go unchecked.
• Automated cockpit systems and mandatory go-around thresholds are designed to prevent such outcomes, yet human factors like ego, fatigue, and "get-there-itis" remain significant risks.
• Aviation experts emphasize that a go-around is a standard, non-punitive procedure that should be executed immediately whenever an approach becomes unstable, regardless of rank or potential delays.
The consensus among aviation professionals identifies this accident as a complete failure of airmanship, driven by a series of reckless decisions that began long before the plane reached the runway. Rather than an issue of equipment familiarity, the crash illustrates the dangers of ignoring stabilized approach criteria and the catastrophic potential of a cockpit environment where the subordinate pilot fails to challenge a captain's dangerous actions. While speculation exists regarding the potential for corporate influence or fatigue, the primary consensus is that the crew's refusal to perform a go-around—a fundamental and universally practiced maneuver—stands as the core driver of the tragedy.