[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"report-2026-05-31":3,"oJL6iA3e9T":605,"QD0X0cR2s8":620,"cNokqZz71t":630,"lnzVJcyVVh":640,"yRZGZPvhoI":650,"Wq2LeAicfx":770,"zaBD8FqzHP":781,"Mm3IAl1ymF":792,"9ah3S96wpd":823,"FpGS5zPMtV":849,"EYoRRHsxu2":943,"mzDVgVrYjw":1067,"TlQOA0miJY":1096,"34FpA8wfPs":1121,"6Y2vFOUmbO":1142,"EHzxY7zjyu":1152,"NBdwUCdc7J":1162,"q1rLQ8Vwq7":1172,"NQzuKu5ap8":1182,"y371S7YZcp":1192,"PhBXJ23RRl":1202,"UdHQea3axi":1212,"l7dTsqfiUI":1395,"4gcOzVZxlL":1432,"UOVjoa1pQS":1469,"ji6Nqrp3ep":1505,"CnzHssA1n1":1565,"6SYNCrujao":1616,"1Urxa0AG6i":1626,"BLik5Y5evb":1636,"xbq8paawgC":1646,"rZQZlwnVbf":1656,"MKRQh2ohI4":1666,"aNyVQA1Nd3":1676,"bRJ3JR8DYP":1814,"HAf1sODPmu":1835,"OFdgg6QsV5":1856,"kNMItW09C6":1877,"OENMQX7ADS":1951,"G9HLnSsGo1":2004,"zjMa9AI9NE":2014,"p9uPI71puY":2024,"E90ZSqxey3":2034,"LL6gld32gp":2044,"uRaPEyP0iW":2054,"nxQygMQWf0":2064,"mk4nZGKcYZ":2074,"9tT9TAIllJ":2226,"Vjhy2DJC0o":2237,"clPXz9SWZn":2273,"ziY8rbQMp3":2289,"kUKO0Z1B5U":2320,"2plcWIsWuB":2440,"trKL7Jmjvg":2580,"tVqpyBYiqG":2601,"wGCA8iEgKp":2622,"5AznqZNCft":2632,"KOhq0acVwm":2642,"JEKRxBh2QO":2652,"nmv2nRTV5F":2729,"rDzaKrUKTY":2739,"tnBzPlBpIo":2749,"ra2ErYcDV6":2839,"U71w7dLt0q":2886,"mLDShPi6jf":2902,"BST6Fpqi9j":2949,"WmqnFLgvoY":2983,"tXNRDrD8bu":3017,"E2JklWylTv":3064,"ffCofYmldr":3080,"DqayivDqhF":3096,"DTyOGBXABQ":3152,"HlFI1aBi2N":3168,"zw1InojVjC":3184,"zJnQnFI1M2":3210,"HDDLiDUr0B":3226,"vEQaGOsarx":3242,"pY571n8yNI":3313,"5NojJION2c":3329,"tzCRsREcFr":3345,"QE1uOFc0Pk":3382,"6nUF0CjP3w":3471,"mMlAdQdPEq":3496,"12k0pBZrY9":3512,"drcJhCFEi4":3555,"1b53bmho52":3565,"jQzTNlI9AP":3575,"oe3b5OcKsb":3666,"yKuvkTMBNw":3692},{"report":4,"adjacent":602},{"version":5,"date":6,"title":7,"sources":8,"hook":15,"deepDives":16,"quickBites":304,"communityOverview":584,"dailyActions":585,"outro":601},"20260216.0","2026-05-31","AI 趨勢日報：2026-05-31",[9,10,11,12,13,14],"academic","alibaba","community","github","meta","microsoft","當 Qwen 3.6 在雙 4060 Ti 跑出 125 tok/s、GitHub Copilot 帳單揭露 agentic 使用的真實成本，社群正在學習區分「可用」與「划算」的邊界。",[17,92,159,228],{"category":18,"source":11,"title":19,"subtitle":20,"publishDate":6,"tier1Source":21,"supplementSources":24,"tldr":29,"context":41,"mechanics":42,"benchmark":43,"useCases":44,"engineerLens":54,"businessLens":55,"devilsAdvocate":56,"community":60,"hypeScore":79,"hypeMax":80,"adoptionAdvice":81,"actionItems":82},"ecosystem","SQLite 就是你需要的持久工作流引擎：社群熱議的架構抉擇","Obelisk 專案以「嵌入式資料庫 + 非同步備份」挑戰 Temporal、Postgres 的工作流主導地位",{"name":22,"url":23},"Obelisk Blog","https://obeli.sk/blog/sqlite-is-all-you-need-for-durable-workflows/",[25],{"name":26,"url":27,"detail":28},"Hacker News 討論：SQLite for Durable Workflows","https://news.ycombinator.com/item?id=48326802","覆蓋 hn-48326802 ref，包含停機容忍度、並行限制、與 Temporal 對比的多面向社群辯論",{"tagline":30,"points":31},"「無聊才是真性感」——SQLite 正悄悄成為 AI 代理工作流的預設儲存引擎",[32,35,38],{"label":33,"text":34},"技術","SQLite + Litestream 架構透過每個 worker 本地資料庫消除網路跳轉，適合 AI 代理、突發性或實驗性工作流，但非同步複寫帶來資料遺失風險。",{"label":36,"text":37},"成本","相較 Temporal 或 Cassandra 等複雜系統，運維負擔大幅降低；唯一持續成本是 S3 物件儲存費用，遠低於管理式工作流服務的訂閱費。",{"label":39,"text":40},"落地","停機容忍度是關鍵篩選器——可接受計畫維護視窗的場景優先考慮；高可用或多節點共享狀態需求仍應選 PostgreSQL。","#### 什麼是持久工作流與 SQLite 方案\n\n持久執行 (Durable Execution) 是一種架構模式，工作流進度被持續記錄在執行日誌中，即使程序崩潰也能從斷點重播。關鍵洞見在於「持久的是工作流狀態，計算本身可以是廉價且可拋棄的」——Obelisk 專案以此為基礎，提出了以 SQLite 取代外部資料庫的完整方案。\n\n> **名詞解釋**\n> **持久執行 (Durable Execution)**：一種工作流執行模型，將每個活動的執行歷史記錄在持久儲存中；系統重啟後可從上次中斷處重播，活動可自動重試，無需開發者手動實作斷點續傳邏輯。\n\nSQLite 方案延伸自 DBOS 的「Postgres is all you need」前提，更進一步主張：對於 AI 代理、突發性工作負載與實驗性系統，本地嵌入式資料庫足以承擔持久化任務，連 Postgres 都可以省去。核心設計目標是消除額外的網路跳轉、獨立控制平面與運維介面。\n\n#### 架構設計：單機 SQLite vs 外部資料庫\n\nObelisk 的架構由三個核心元件組成：與 worker 共置的本地 SQLite 資料庫、Litestream 非同步備份至 S3 相容物件儲存，以及可拉取資料庫進行檢查的 Observer 元件。這個設計徹底消除了對獨立資料庫服務的依賴。\n\n相較外部資料庫方案，SQLite 在多租戶場景帶來更好的故障隔離：每個 worker 擁有獨立資料庫，一個 worker 的問題不會波及其他 worker。但 Litestream 的非同步複寫是有意接受的取捨——硬體故障時，尚未複寫的最新狀態存在遺失風險，這是架構設計必須正視的邊界條件。\n\n> **白話比喻**\n> 傳統工作流系統是一棟共用廚房的公寓大樓——所有住戶共用一個廚房，廚房壞了所有人都不能開伙。SQLite 方案則像每戶都有自己的迷你廚房，附帶一個每隔幾分鐘備份食材到倉庫的服務——某一戶廚房壞了，其他人照常做飯；只是最後幾分鐘的食材若沒來得及備份，就可能遺失。\n\n#### 社群論戰：停機容忍度與複雜度取捨\n\nHN 討論最尖銳的分歧在於停機容忍度。cortesoft 從 CDN 從業背景提出質疑：「你沒辦法在 SQLite 下做那些事又不停機——在我職涯大部分時間，任何停機都是完全不可接受的。」franga2000 直接反駁：「就……不在意？在非工作時間做維護，快速修復問題，好好向客戶解釋。」\n\n這個對話揭示了架構決策的核心篩選器：停機容忍度不是技術問題，而是業務價值觀問題。CDN、金融交易、醫療系統這類場景，停機容忍度接近零；而大量的 AI 代理、內部工具、實驗性系統則可接受計畫維護視窗。\n\n複雜度辯論同樣分裂。fcarraldo 批評 Temporal/Cassandra：「Temporal 規模化後複雜度爆炸，Cassandra 也不好管——所有在上面建立真正生產系統的人都討厭它。」inglor 則從直接經驗反駁：「我們在 Temporal 上建立了一家十億美元的公司，再開心不過了。」\n\n這說明架構選擇高度依賴團隊背景，沒有普適答案。utopiah 的元觀察捕捉了整個討論的精髓：工程師從複雜工具的挫折中成熟，最終重新發現更簡單的工具。stingraycharles 更直白：「無聊才是新的性感。」\n\n#### 實戰建議與替代方案比較\n\n選擇 SQLite + Litestream 的適合情境是：工作負載具突發性或實驗性質、需要每個 worker 獨立故障隔離、業務可接受計畫維護視窗，且建立完整網路資料庫基礎設施成本過高。AI 代理工作流是目前社群最看好的場景，因代理任務本質上短暫且可重試。\n\nPostgreSQL 仍是高可用需求的正確選擇：當多個 worker 需共享狀態、團隊已有 Postgres 運維經驗，或業務要求零停機時。LangGraph v0.2 已明確區分兩條路徑——本地工作流用 SQLite checkpointer，生產環境用最佳化的 Postgres checkpointer，這種雙軌策略值得借鑒。","持久工作流的核心是「用日誌換可靠性」：每個活動執行後立即寫入執行歷史，系統崩潰後可從日誌重播回正確狀態。SQLite 版本的創新在於，這個日誌不再需要放在遠端——放在 worker 旁邊的本地檔案就夠了。\n\n#### 機制 1：本地 SQLite 執行日誌\n\n每個 worker 維護一個本地 SQLite 資料庫作為工作流歷史日誌。當工作流需要重播時，系統從這個本地日誌讀取已完成的活動記錄，只重新執行尚未完成的步驟，避免重複處理。本地讀寫消除了網路延遲，對執行頻率高但每次執行輕量的 AI 代理任務而言效能優勢明顯。\n\n#### 機制 2：Litestream 非同步複寫\n\nLitestream 持續將 SQLite 的 WAL(Write-Ahead Log) 變更串流至 S3 相容的物件儲存。這個設計讓持久化不阻塞工作流主路徑，代價是非同步特性帶來的「最終一致」複寫語意——硬體突然崩潰時，可能遺失尚未串流出去的最新幾秒狀態。\n\n> **名詞解釋**\n> **WAL(Write-Ahead Log)**：SQLite 的一種日誌模式，允許讀取與寫入並行進行，讀取不阻塞寫入。相較預設的 DELETE journal 模式，在高並行讀寫場景下效能顯著提升。\n\n#### 機制 3：Observer 與本地除錯\n\nObserver 元件可拉取任意 worker 的 SQLite 資料庫副本，讓工程師在本機重播工作流歷史進行除錯。這種「把工作流歷史拉下來跑」的能力，是傳統外部資料庫架構難以輕易提供的開發體驗優勢——Replay 能力讓故障重現從「線上追查」變成「本機回放」。\n\n> **白話比喻**\n> 把持久工作流想像成一本記事本。傳統架構把記事本放在公司共用文件室（外部資料庫）——所有人都要跑去那裡查閱；SQLite 架構則讓每個工程師隨身攜帶記事本，同時每隔幾分鐘自動拍照上傳備份。查閱快、備份自動，但若記事本不小心落水，最後幾頁可能沒來得及備份。","#### SQLite WAL 模式效能上限\n\n社群討論中引用的基準測試顯示，在啟用 WAL 模式並適當最佳化的條件下，SQLite 可達每秒 10 萬次事務 (100,000 TPS) ，測試資料集超過 10 億行。這個數字對工作流狀態持久化場景已綽綽有餘——工作流日誌的寫入頻率遠低於 OLTP 場景。\n\n真正的瓶頸在於**單寫入者限制**：SQLite 不支援多個 writer 並行寫入同一個資料庫檔案。這也是 Obelisk 採用「每個 worker 一個獨立 SQLite」設計的原因——用水平分片換取對單寫入者限制的規避，而非強行讓多個 worker 競爭同一個 SQLite 實例。",{"recommended":45,"avoid":50},[46,47,48,49],"AI 代理工作流：任務短暫、突發、可重試，不需跨多個 worker 共享狀態","邊緣部署與單機應用：運維資源有限，不想引入獨立資料庫服務","實驗性系統與內部工具：可接受計畫維護視窗，開發體驗比高可用更重要","本地開發環境：透過 Observer 本機重播工作流歷史，大幅降低除錯成本",[51,52,53],"零停機要求的關鍵業務系統（CDN、金融交易、醫療記錄）","高並行寫入場景：多個 worker 需同時寫入同一工作流狀態","多節點協調需求：工作流狀態需跨節點共享或一致性要求極高","#### 環境需求\n\nSQLite 3.35+（支援 WAL 模式與 RETURNING 語法），Litestream 0.3+，以及 S3 相容物件儲存（AWS S3、MinIO、Cloudflare R2 均可）。Obelisk 本體以 Rust 實作，worker 執行環境無需額外語言執行期依賴。若使用 LangGraph，直接升級至 v0.2 即可取得原生 SQLite checkpointer 支援。\n\n#### 遷移／整合步驟\n\n1. 將現有工作流狀態儲存層替換為本地 SQLite（修改 checkpointer 設定，LangGraph 用戶只需更換 checkpointer 實例）\n2. 部署 Litestream 作為 sidecar，設定 S3 備份目標與複寫間隔（建議 1 秒以內）\n3. 整合 Observer 元件，設定可存取 worker SQLite 的讀取路徑\n4. 在 CI 環境中驗證本地重播功能：從 S3 備份還原後重跑測試工作流，確認重播一致性\n\n#### 常見陷阱\n\n- 誤以為 Litestream 提供同步複寫保證——實際上是非同步，SLA 中必須明確聲明資料遺失容忍度 (RPO > 0)\n- 在高並行寫入場景強行使用 SQLite——單寫入者特性在此場景會成為瓶頸，應拆分為多個獨立 SQLite 實例\n- 忘記啟用 WAL 模式——未啟用 WAL 的 SQLite 在高讀寫負載下效能顯著下降，且不支援並行讀取\n\n#### 上線檢核清單\n\n- 觀測：Litestream 複寫延遲監控、worker SQLite 檔案大小趨勢、工作流重播成功率\n- 成本：S3 PUT 請求費用（WAL 串流頻率）、Observer 拉取頻率與網路傳輸費用\n- 風險：定期演練從 S3 備份完整還原並重播工作流（不要只備份不演練，否則發現不了備份損壞）","#### 競爭版圖\n\n- **直接競品**：Temporal（工作流編排領域主流選擇，有 Temporal Cloud 管理服務）、Conductor（Netflix 開源，適合大規模微服務編排）、Prefect 與 Airflow（資料管道導向）\n- **間接競品**：自建 Redis + Bull 佇列、AWS Step Functions（雲原生，lock-in 風險）、Azure Durable Functions（.NET 生態）\n\n#### 護城河類型\n\n- **工程護城河**：零外部依賴的嵌入式設計讓邊緣部署、本地開發環境、單機 AI 代理場景具有天然優勢，競品難以在不犧牲架構簡潔性的前提下複製\n- **生態護城河**：LangGraph v0.2 已原生支援 SQLite checkpointer，Obelisk 推動社群標準化，形成正向循環\n\n#### 定價策略\n\nSQLite + Litestream 方案本身為開源免費，唯一持續成本是 S3 物件儲存費用（通常每 GB 月費不到 $0.03）。對比 Temporal Cloud 的按任務計費模式，突發性 AI 代理工作流的成本節省相當顯著——峰值時段費用不會因工作流數量線性成長。\n\n#### 企業導入阻力\n\n- 非同步複寫的資料遺失風險難以向企業安全與合規團隊解釋，需明確界定 RPO 邊界\n- SQLite 單寫入者限制讓架構師對多節點水平擴展方案持懷疑態度\n- 缺乏如 Temporal 般完整的可觀測性生態（可視化 Dashboard、分散式追蹤工具整合）\n\n#### 第二序影響\n\n- AI 代理工作流普及可能推動「per-agent SQLite」成為開源框架預設設計模式，進而影響雲端工作流服務的定價競爭\n- 邊緣運算場景中 SQLite 持久工作流可能取代輕量級訊息佇列，重塑邊緣 AI 基礎設施選型\n\n#### 判決先觀望（技術有效但生態尚不成熟）\n\nSQLite 持久工作流在正確場景下是清晰有效的架構選擇，技術論點站得住腳。但完整工具鏈（可觀測性、除錯工具、多框架標準化支援）仍在建構中，生產案例積累不足。對已有 Temporal 或 Postgres 基礎設施的團隊，遷移收益有限；新 AI 代理專案則值得認真評估。",[57,58,59],"Litestream 非同步複寫在硬體突然故障時必然遺失部分工作流狀態，對金融交易、醫療記錄等高可靠性場景是根本性的架構缺陷，不是「謹慎使用」就能解決的問題。","隨著 AI 代理工作流規模化，單寫入者架構的並行限制會逐漸顯現——「每個 worker 一個 SQLite」的設計在 worker 數量爆炸後，反而帶來資料分散和跨 worker 查詢困難的新問題。","HN 社群的激烈辯論本身說明這個方案並非普適共識——levkk 等具備分散式系統背景的工程師對 SQLite 並行能力的批評並非無的放矢，而是指向真實的工程邊界。",[61,65,68,72,76],{"platform":62,"user":63,"quote":64},"Hacker News","cortesoft","那前兩個選項反而比直接用外部資料庫更複雜。我想我就是不習慣停機被接受這件事。在我職涯大部分時間都服務於 CDN，任何形式的停機都是完全不可接受的，我現在也戒不掉這種思維。",{"platform":62,"user":66,"quote":67},"jusonchan81","同意這個觀點，這正是我們工作流編排平台 unmeshed.io 的底層架構。",{"platform":69,"user":70,"quote":71},"Bluesky","foursignalsdev.bsky.social(Gene Conroy-Jones)","持久工作流不需要 PostgreSQL。SQLite 搭配 WAL 模式足以應對單節點或邊緣部署——更低延遲、更少運維、同樣的 ACID 保證。",{"platform":73,"user":74,"quote":75},"X","@LangChainAI（LangGraph 框架創建者）","我們已發布 LangGraph v0.2，透過新的 checkpointer 函式庫提供更高度客製化。這讓你能輕鬆建立 SQLite checkpointer 用於本地工作流，或建立最佳化的 Postgres checkpointer 將應用推向生產環境。",{"platform":73,"user":77,"quote":78},"@schickling（Prisma 創始人，開發者工具創業者）","對 TanStack DB 非常興奮。它不是『完整的資料庫』（如 SQLite），但以實用方式解決了許多相關的客戶端工作流問題。它使用 IVM 實現快速響應式查詢——優秀的專案！",3,5,"先觀望",[83,86,89],{"type":84,"text":85},"Try","在本地 AI 代理專案中用 LangGraph v0.2 的 SQLite checkpointer 取代現有狀態儲存，觀察開發體驗與除錯便利性差異。",{"type":87,"text":88},"Build","建立工作流歷史重播測試套件：定期從 Litestream 備份還原，驗證工作流重播正確性，確保備份在真正需要時可用。",{"type":90,"text":91},"Watch","追蹤 Obelisk 與 LangGraph 的生產案例積累，以及社群對 SQLite 並行限制的解法演進——共識走向將決定此架構的長期採用率。",{"category":93,"source":11,"title":94,"subtitle":95,"publishDate":6,"tier1Source":96,"supplementSources":99,"tldr":104,"context":116,"devilsAdvocate":117,"community":120,"hypeScore":136,"hypeMax":80,"adoptionAdvice":137,"actionItems":138,"perspectives":145,"practicalImplications":157,"socialDimension":158},"discourse","MCP 已死？社群激辯 AI 工具協議的未來與存廢","一份工程師的棄用報告，引爆協議設計哲學的根本之爭",{"name":97,"url":98},"Quandri Engineering Blog：MCP is Dead","https://www.quandri.io/engineering-blog/mcp-is-dead",[100],{"name":101,"url":102,"detail":103},"Hacker News：MCP is Dead 討論串","https://news.ycombinator.com/item?id=48330436","涵蓋 OpenAI MCP 負責人回應、反對方技術論點及企業端支持者觀點，為本篇爭議的主要社群討論來源",{"tagline":105,"points":106},"MCP 不是死了，而是被誤用了：協議本身沒錯，工具鏈思維才是關鍵",[107,110,113],{"label":108,"text":109},"爭議","Quandri 實測四個 MCP server 吃掉 10.5% context window，大多數工具從未被呼叫，引爆 HN 社群激辯。",{"label":111,"text":112},"實務","CLI-First 策略在開發者主導場景更輕量；MCP 在無 CLI 介面、企業憑證隔離場景仍有不可替代的位置。",{"label":114,"text":115},"趨勢","MCP 16 個月達到月均 9,700 萬次 SDK 下載，生態系慣性已成；動態工具載入可能是下一步演進方向。","#### MCP 的定位與現狀\n\nMCP(Model Context Protocol) 由 Anthropic 推出，旨在讓 AI agent 透過標準化協議連接外部服務與工具。\n\nQuandri 後端工程師 Chloe Kim 在《MCP is Dead》一文中，記錄了團隊將四個 MCP server 全數替換為 CLI + Skills 方案的實戰歷程，引發 Hacker News 社群大規模論戰。\n\n根據 Quandri 的測試，四個 MCP server 的工具定義共佔用了 200K context window 的 10.5%，單是 Linear server 就消耗約 12,800 tokens（含 42 個工具定義），但實際被呼叫到的只有兩個函式。\n\n替換後釋出約 21K tokens，回應穩定性與 terminal 除錯流程也顯著改善。這份數據讓許多曾遇到類似問題的開發者感同身受，批評聲浪一夕浮出水面。\n\n#### 反對方：REST + JSON + OAuth 就夠了\n\n反對 MCP 的核心論點在於：協議本身所解決的問題，既有技術棧早已有成熟解法。\n\nQuandri 歸納出 MCP 的三大痛點：\n\n- context window 爆滿（tool schema 隨 server 數量線性膨脹）\n- 可靠性問題（首次呼叫慢 9.4 倍、mid-session crash、權限不透明）\n- 功能與現有 CLI/API 高度重疊\n\nHN 討論中，多位開發者直指：OpenAPI spec、OAuth 及 sandbox 早已處理了這些問題。\n\n批評者認為 MCP 不過是把 REST + JSON + OAuth 重新包裝了一層——讓開發者多了學習成本，卻未帶來本質突破。\n\n> **名詞解釋**\n> OpenAPI spec：一種描述 RESTful API 結構的標準規格，讓開發者與工具能自動理解 API 的端點、參數與回應格式，無需手動閱讀文件。\n\n#### 支持方：標準化協議的不可替代價值\n\n支持方最有力的論點，來自 OpenAI 負責 MCP 的成員：MCP 的真正價值在於讓「原本沒有 API 的服務」得以暴露出來，讓 AI agent 取得原本無法獲得的存取權，而非協議本身的技術細節。\n\n企業端支持者則強調合規場景的優勢：憑證分離（LLM 只看 request，不碰 token）以及跨組織的集中式 policy 執行，讓合規管控遠比管理零散 CLI 工具容易。\n\nQuandri 也承認 MCP 在三種場景仍有其位置：\n\n- 沒有 CLI 介面的服務\n- 非開發者用戶需要無縫存取的場景\n- 生產資料庫需要憑證保護與安全護欄的情境\n\n這三種情境，恰好是 CLI-First 策略無法覆蓋的邊界地帶。\n\n#### 開發者該如何選擇工具整合方案\n\nQuandri 的替代方案「CLI-First + Skills Pattern」並非普世解法，而是針對開發者工具鏈高度重疊時的務實選擇。\n\nSkills Pattern 的核心邏輯是「只在需要時載入工具說明」，有效避免 context window 被大量未使用的工具定義佔滿。\n\n選擇的關鍵在於對使用場景的清醒認識：\n\n- 服務已有完善 CLI 或 REST API，且使用者以開發者為主 → CLI-First 策略更輕量\n- 需跨組織統一憑證管理、服務尚無 API，或用戶群為非技術人員 → MCP 展現差異化價值\n\n> **白話比喻**\n> 就像「計程車 vs. 大眾運輸」的選擇：計程車 (CLI) 靈活、直達、速度快；公車系統 (MCP) 標準化、路線固定、適合大規模跨組織人流。沒有誰更好，只有哪個更適合你的情境。",[118,119],"MCP 生態系慣性已不可逆：每月 9,700 萬次 SDK 下載意味著大量工具與服務已圍繞 MCP 構建整合，棄用成本可能遠高於修補現有痛點。","Quandri 的案例高度特化於開發者工具鏈完整的場景，無法代表所有使用者——對非技術用戶或無 CLI 介面的服務而言，MCP 仍可能是最省力的選擇。",[121,124,127,130,133],{"platform":62,"user":122,"quote":123},"ok_dad(HN)","你的答案，本質上就是在打造一個類似 MCP 的東西。標準化 JSON 約定？很好，接著去標準化 auth 吧。OAuth 不錯吧？那就是 MCP 了。MCP 就是用 JSON 加上 OAuth 的 RESTful API。你一邊批評 MCP，卻提不出任何本質上不同的替代方案。",{"platform":62,"user":125,"quote":126},"geysersam(HN)","所有 agent 本來就有一些基本工具能力——我指的是用 curl 或 python 等工具直接存取 API，就跟人類操作的方式一樣，這原本就夠用了。",{"platform":62,"user":128,"quote":129},"CBarkleyU(HN)","如果想讓『教學』內容來自 server 端，用 OpenAPI spec 就好；如果想在本地靜態使用，man page 就夠了——為什麼不這樣問呢？",{"platform":73,"user":131,"quote":132},"@milvusio（Milvus 向量資料庫專案）","別太快否定 MCP。協議本身沒問題，問題在於團隊的使用方式。MCP 的真正痛點其實很具體：把 50 個工具定義塞進 context，agent 就很難選對工具；context window 在真正的工作開始之前就已經被塞滿了。",{"platform":69,"user":134,"quote":135},"torcdotdev.bsky.social(3 upvotes)","MCP 在 16 個月內從小眾協議成長到每月 9,700 萬次 SDK 下載。如果你還在摸索 Model Context Protocol 究竟是什麼、未來方向在哪，我們做了一場完整的圓桌討論。",4,"追整體趨勢",[139,141,143],{"type":84,"text":140},"在下個 side project 中試用 Skills Pattern 替代部分 MCP server，記錄 context window 使用量變化，比較 agent 推理品質差異。",{"type":87,"text":142},"為現有 MCP server 建立工具使用率統計（記錄哪些工具定義實際被呼叫），識別低頻工具並評估 CLI 替代方案。",{"type":90,"text":144},"追蹤 MCP 官方路線圖，觀察是否有「動態工具載入」或 context 最佳化的改進計劃；同時關注 OpenAPI spec 生態系與 MCP 的整合動向。",[146,150,154],{"label":147,"color":148,"markdown":149},"正方立場","green","#### 讓無 API 服務可被 AI 存取\n\nMCP 的核心價值不在技術細節，而在讓「原本沒有 API 的服務」得以暴露，讓 AI agent 取得原本無法獲得的存取權。\n\n這是 CLI 方案無法覆蓋的場景——若服務本身沒有 CLI 或 REST 介面，MCP 就是唯一的標準化橋接選項。\n\n#### 企業合規的結構性優勢\n\n憑證分離（LLM 只看 request，不接觸 token）搭配跨組織集中式 policy 執行，讓合規管控遠比管理零散 CLI 工具容易。\n\n對有嚴格資安要求的企業而言，這種結構性護欄難以用臨時性的 CLI 腳本替代，MCP 的標準化在此展現了真正的差異化。",{"label":151,"color":152,"markdown":153},"反方立場","red","#### context window 的結構性浪費\n\nQuandri 實測顯示四個 MCP server 吃掉 200K context window 的 10.5%，Linear server 單獨消耗 12,800 tokens，實際用到的卻只有兩個函式。\n\n這種浪費隨 server 數量線性膨脹，對依賴大型 context 的工作流程是不可接受的結構性缺陷。\n\n#### 技術上毫無新意\n\nOpenAPI spec、OAuth 與 sandbox 早已解決 MCP 試圖解決的問題，MCP 不過是把 REST + JSON + OAuth 重新包裝，徒增學習成本而無本質突破。\n\n可靠性問題（首次呼叫慢 9.4 倍、mid-session crash、權限不透明）更讓這個「新協議」難以在生產環境信任使用。",{"label":155,"markdown":156},"中立／務實觀點","#### 協議本身不是問題\n\nMCP 作為協議並沒有根本性缺陷，問題在於團隊的使用方式——把所有 server 的工具定義全部塞入 context，等於把問題製造出來再怪工具本身。\n\n#### 場景決定選擇\n\n開發者工具鏈完整的團隊，CLI-First + Skills Pattern 是更輕量的選擇；跨組織管理、非技術用戶或服務尚無 API 的場景，MCP 標準化仍有其位置。\n\n#### 生態系慣性不容忽視\n\nMCP 在 16 個月內達到每月 9,700 萬次 SDK 下載，標準化帶來的互通性往往比純技術優劣更具決定性，生態系的慣性讓棄用成本遠高於修補。","#### 對開發者的影響\n\n使用 MCP 前，應先盤點實際需要的工具數量，避免把所有 server 全部載入 context。\n\nSkills Pattern 的「按需載入」策略能有效控制 context window 使用量，改善 agent 的推理品質與回應穩定性。\n\n#### 對團隊／組織的影響\n\n若團隊以開發者為主且工具鏈完整，CLI-First 策略往往更輕量且易於除錯。\n\n若需跨組織統一憑證管理，或服務用戶為非技術人員，MCP 的標準化協議才能展現差異化價值，值得投資建置成本。\n\n#### 短期行動建議\n\n- 現有 MCP 環境：審查 server 清單，移除低使用率工具定義，或改用 Skills Pattern 按需載入\n- 新專案評估：先確認服務是否已有 CLI 或 REST API，有則優先 CLI-First，無則考慮 MCP\n- 企業合規場景：評估憑證分離與集中式 policy 需求，有明確需求再導入 MCP","#### 產業結構變化\n\nMCP 在 16 個月內達到每月 9,700 萬次 SDK 下載，顯示生態系已形成相當慣性。\n\n即便存在設計瑕疵，標準化協議帶來的互通性——讓任意 AI agent 可接入任意 MCP server——往往比純技術優劣更具決定性，產業難以輕易放棄。\n\n#### 倫理邊界\n\n此次爭議的深層問題，在於 AI 工具鏈的「標準化 vs. 客製化」之爭。\n\n過度依賴標準化協議，可能導致 context window 被通用工具定義大量佔用，壓縮 AI 真正執行任務的空間；放棄標準化，則可能讓每個團隊各自為政，提高整個生態系的整合成本。\n\n#### 長期趨勢預測\n\n短期內，MCP 與 CLI-First 將並存於不同場景，不存在「一個協議取代一切」的局面。\n\n中長期看，協議可能朝「動態工具載入」演進——只在 agent 需要時才將工具定義注入 context，從根本解決 context window 浪費問題。",{"category":93,"source":11,"title":160,"subtitle":161,"publishDate":6,"tier1Source":162,"supplementSources":165,"tldr":182,"context":191,"devilsAdvocate":192,"community":196,"hypeScore":79,"hypeMax":80,"adoptionAdvice":137,"actionItems":212,"perspectives":219,"practicalImplications":226,"socialDimension":227},"AI 輔助開發正在重演前端的「失落十年」嗎？","去技能化陷阱、技術債數據，與開發者如何在 AI 時代維持專業價值",{"name":163,"url":164},"Mastro Blog","https://mastrojs.github.io/blog/2026-05-23-is-AI-causing-a-repeat-of-frontends-lost-decade/",[166,170,174,178],{"name":167,"url":168,"detail":169},"Hacker News 討論：AI 是否重演前端失落十年","https://news.ycombinator.com/item?id=48321631","HN 社群針對 Mastro 部落格文章展開的討論串，涵蓋多種立場的工程師觀點",{"name":171,"url":172,"detail":173},"arXiv 2603.28592：AI 生成程式碼技術債大規模實證研究","https://arxiv.org/html/2603.28592v1","分析 6,275 個 GitHub repo、304,362 筆 AI 提交，量化 AI 引入的問題類型與比例",{"name":175,"url":176,"detail":177},"Pixelmojo：2026-2027 AI 程式碼技術債危機預測","https://www.pixelmojo.io/blogs/vibe-coding-technical-debt-crisis-2026-2027","彙整 Forrester 與 Gartner 對 AI 技術債的市場預測數據",{"name":179,"url":180,"detail":181},"LeadDev：AI 生成程式碼如何加速技術債累積","https://leaddev.com/technical-direction/how-ai-generated-code-accelerates-technical-debt","工程領導力視角分析 AI 對開發者生產力與程式碼品質的雙面影響",{"tagline":183,"points":184},"PR 產出量增加 20%，線上事故率上升 23.5%——AI 讓你跑得更快，也讓你跌得更重",[185,187,189],{"label":108,"text":186},"Mastro 部落格引發 HN 熱議：AI 輔助開發與前端「失落十年」有相同的去技能化邏輯，開發者正在失去對語意 HTML、無障礙設計與底層效能的掌握能力。",{"label":111,"text":188},"arXiv 研究分析 30 萬筆 AI 提交，每款工具超過 15% 的 commit 引入至少一個問題，24.2% 的 AI 技術債在最新版本仍未被修復，AI 引入的 bug 數量多於修復的。",{"label":114,"text":190},"Gartner 預測「prompt-to-app」方式將在 2028 年前讓軟體缺陷增加 2,500%；若不主動管理，AI 技術債的維護成本將在第二年達到傳統開發的 4 倍。","#### 前端「失落十年」的歷史回顧\n\n2010 年代，React、Angular、Vue 等 JavaScript 框架浪潮崛起，將瀏覽器視為應用程式的編譯目標，而非文件呈現環境。開發者開始透過元件庫封裝底層 HTML 邏輯，逐漸失去對語意化標籤、瀏覽器差異、無障礙設計 (accessibility) 與漸進增強的深層理解。\n\n這套能力被業界稱為「front of the frontend」——包含符合 WCAG 標準的 HTML 撰寫、跨裝置效能最佳化、以及完整的鍵盤導航支援。以 shadcn 的 radio button 元件為例：一行程式碼背後包裹著 ARIA 屬性與鍵盤互動的複雜度，讓開發者徹底失去理解機會。十年後，整個產業才意識到這段時期留下了多深的能力缺口。\n\n> **名詞解釋**\n> WCAG(Web Content Accessibility Guidelines) ：W3C 制定的網頁內容無障礙設計指引，規範文字對比度、鍵盤可操作性、螢幕閱讀器相容性等標準，是無障礙設計的國際基準。\n\n#### AI 生成程式碼的品質與技術債隱憂\n\n2026 年，全球新增程式碼中 41% 為 AI 生成，但大多數未經有效審查便直接上線。Mastro 部落格的核心論點指出：AI 程式碼生成是「漏洞抽象 (leaky abstraction) 」，與確定性編譯器根本不同——微小的輸入差異或模型版本變更就會產生截然不同的輸出，行為更像不穩定的初級工程師，而非可靠工具。\n\n> **名詞解釋**\n> 漏洞抽象 (leaky abstraction) ：指抽象層無法完全隱藏底層細節的現象，使用者終究需要理解底層才能除錯。由 Joel Spolsky 在 2002 年提出，常被用來描述「方便但遮蔽複雜度的工具」的固有風險。\n\narXiv 大規模實證研究 (2603.28592) 分析了跨 6,275 個 GitHub repo 的 304,362 筆 AI 提交，揭示了一個不對稱能力問題：AI 工具擅長修正表層的程式碼壞味道，但引入的 bug 與安全問題數量多於修復的。在所發現的 484,606 個問題中，程式碼壞味道佔 89.1%、執行時 bug 佔 5.8%、安全漏洞佔 5.1%，且 24.2% 的 AI 技術債在最新版本仍未被修復。\n\n從生產力指標來看，AI 導入後每位開發者的 PR 數量增加 20%，但每個 PR 的線上事故率同步上升 23.5%。\n\nForrester 預測 75% 的技術決策者將在 2026 年前面臨中度至嚴重的技術債；Gartner 則預測「prompt-to-app」方式將在 2028 年前讓軟體缺陷增加 2,500%。若不主動管理，AI 生成技術債的維護成本將在第二年達到傳統開發的 4 倍。\n\n#### 社群分歧：效率提升還是劣幣驅逐良幣\n\nHN 討論串呈現了鮮明的立場分歧。批評方認為 AI 加速了去技能化——knuckleheads 指出這不過是「軟體從工藝轉向工業化流程」的 20 年趨勢在 AI 時代的加速版本，對行業長期健康有深遠危害。\n\n支持方則提出反例：hombre_fatal 認為 LLMs 對 ARIA 無障礙屬性的掌握可能超過 90% 以上的前端開發者，AI 反而有機會在過去無人投資的角落推廣最佳實踐。d0liver 則直白指出，AI 出現之前軟體品質就已問題重重——把劣化責任全歸咎於 AI 工具，是一種不誠實的歷史敘事。\n\nbayarearefugee 提出了一個更深遠的結構性隱憂：開源生態系的貢獻長期依賴有穩定工作的開發者在業餘時間投入，若 AI 擾亂就業市場，這個生態基礎也將動搖——這是超越個別工具品質之外更難以修復的損傷。\n\n#### 開發者如何在 AI 時代保持專業價值\n\nesalman 在 HN 討論串中道出了核心洞見：「用 Rust 其實是這道問題最無趣的部分，沒有一定程度的領域知識，幾乎不可能解決它。」語言選擇或工具選擇從來不是真正的門檻——領域知識的深度才是。\n\n能辨識 AI 輸出是否邏輯一致、安全可靠、符合業務需求的工程師，在 AI 時代反而更有價值。具體策略包括：\n\n- 主動學習 AI 工具的弱項（語意 HTML、安全邊界、作用域管理），在 code review 中重點稽核這些環節\n- 建立「AI 輔助但人工審查」的工作流程，而非「AI 生成直接上線」的習慣\n- 持續培養對底層機制的理解，確保在抽象層洩漏時有能力下探除錯\n\n文章作者的警示仍然有效：「在某個時間點，抽象終究會洩漏，而到時候必須有人投入時間解決。」那個人，最好是你。",[193,194,195],"AI 引入的技術債問題本質上是審查文化問題而非工具問題——有嚴格 code review 機制的團隊，AI 只是更高效的初稿工具，問題在組織紀律而非 AI 本身。","24.2% 的 AI 技術債未被修復聽起來嚴重，但研究缺乏傳統人工程式碼的對照組數據——在沒有基準比較的情況下，無法得出「AI 更差」的結論。","前端失落十年的根本原因是元件化文化與缺乏 web 素養，早在 AI 出現之前就已存在；把當前的技術債危機主要歸咎於 AI 是在轉移焦點，分散了解決真正問題的注意力。",[197,200,203,206,209],{"platform":62,"user":198,"quote":199},"esalman","使用 Rust 其實是這個問題中最無趣的部分。對於沒有一定程度領域知識的人來說，幾乎不可能解決這道問題。",{"platform":62,"user":201,"quote":202},"d0liver","AI 出現之前軟體就已經是一團糟，所以你的二分法根本不成立。給 LLM 1000 小時處理問題，它會持續吐出平庸的變體；給我 1000 小時，我的產品會持續提升 1%。",{"platform":62,"user":204,"quote":205},"skydhash","網頁平台原本就是為文件而生的，當我們試圖把它扭曲成應用程式，裂縫就開始出現了。這根本就是用錯了工具。",{"platform":62,"user":207,"quote":208},"overgard","我不反對任何人創作，但如果你要請陌生人評價你的作品，有個最低標準要求是合理的。現在太多品質不佳的東西把真正好的東西淹沒了。",{"platform":62,"user":210,"quote":211},"HDThoreaun","和以前一樣——持續嘗試，直到找到與你偏好相符的評論者。只要對方的判斷標準一致，我不在乎他是不是 AI。",[213,215,217],{"type":84,"text":214},"在下一個 sprint 對所有 AI-assisted PR 加入靜態分析閘門（如 SonarQube），比較導入前後的線上事故率，取得自己團隊的 AI 程式碼品質基準數據。",{"type":87,"text":216},"在 code review checklist 中新增 AI 程式碼專屬審查項目：語意化 HTML 使用、ARIA 屬性正確性、作用域邊界清晰度、安全性輸入驗證等底層技能點。",{"type":90,"text":218},"持續追蹤 arXiv 2603.28592 後續研究更新、Gartner 2028 年缺陷增加 2,500% 預測是否兌現，以及各大企業如何在 AI 加速開發的同時調整 QA 流程。",[220,222,224],{"label":147,"color":148,"markdown":221},"AI 輔助開發提高了開發可及性，讓原本無法實作 ARIA 標準的開發者也能產出符合無障礙設計的程式碼。\n\nLLMs 對最佳實踐的掌握往往超過一般開發者，理論上能填補長期被忽視的品質缺口——尤其在語意化 HTML 與無障礙設計這類「沒人願意投資」的領域。\n\n20% 的 PR 產出率提升是真實的生產力增益。技術債問題可透過更嚴格的審查流程管理，而非拒絕工具本身——工具無罪，流程紀律才是關鍵。",{"label":151,"color":152,"markdown":223},"AI 輔助開發加速了去技能化：當開發者習慣讓 AI 生成邏輯，對底層機制的理解逐漸退化，形成正向回饋迴圈——技能越低，越依賴 AI，越失去鑑別 AI 錯誤的能力。\n\narXiv 研究顯示 AI 引入的 bug 多於修復的，超過 15% 的 commit 帶有問題，24.2% 的技術債未被修復。\n\nPR 產出量增加 20% 但事故率增加 23.5%，精準呈現「速度換穩定性」的代價。這不只是管理問題，而是工具本身行為像不穩定初級工程師的結構性問題。",{"label":155,"markdown":225},"問題的核心不是 AI 工具本身，而是開發文化能否維持有意義的品質審查。\n\n把 AI 當成免責工具（「AI 生成的，我不負責」）會放大所有問題；把它當成需要指導與審查的初級協作者，多數問題都可管理。\n\n真正的差異在於工程師能否保持對底層技術的理解——當漏洞抽象洩漏時，必須有人有能力下探除錯。這種能力不能外包給 AI，也不能靠抽象工具維持。","#### 對開發者的影響\n\nAI 工具讓程式碼產出速度大幅提升，但同時要求開發者具備更強的審查能力，而非更弱。能識別 AI 生成程式碼中的邏輯錯誤、安全漏洞、語意問題的工程師，在 AI 時代反而更有價值。\n\n具體行為變化包括：\n\n- 在接受 AI 建議前先理解其底層邏輯，而非直接複製貼上\n- 在熟悉的領域使用 AI 提速，在不熟悉的領域保持手動實作以維持學習路徑\n- 主動補強 AI 的弱項：語意化 HTML、無障礙設計、安全邊界\n\n#### 對團隊／組織的影響\n\n組織需要在「AI 提速」與「品質維護」之間建立顯式的平衡機制。僅追蹤 PR 數量而不追蹤事故率，等同於以隱性方式接受「更多缺陷換取更快速度」的決策。\n\n招募策略也需要調整：能審查 AI 程式碼的資深工程師比純粹的 AI 輸出者更稀缺，薪資溢價將逐漸集中在具備底層技術深度的工程師身上。\n\n#### 短期行動建議\n\n- 為 AI 輔助開發建立明確的 code review 標準，而非沿用傳統人工撰寫程式碼的審查慣例\n- 每季追蹤一次 AI-assisted PR 的事故率與技術債累積速度，作為工具使用健康度的量化指標\n- 定期安排「無 AI 練習」時段，確保開發者的底層技能不會因過度依賴工具而退化","#### 產業結構變化\n\n去技能化的長期影響會重塑就業市場的結構。入門級工程師職位可能萎縮——原本由初級工程師處理的程式碼生成工作正被 AI 替代，但這也切斷了讓新人累積技能的成長路徑。\n\nbayarearefugee 提出的開源生態隱憂值得重視：開源社群的活力長期依賴有穩定收入的工程師投入業餘時間貢獻，若 AI 持續壓縮初中階職位，開源生態的人才補給管道也將隨之萎縮。\n\n#### 倫理邊界\n\n核心倫理問題不是「AI 是否應該用於寫程式」，而是「誰為 AI 生成的有缺陷程式碼負責」。\n\n當 41% 的新增程式碼為 AI 生成且大多數未經有效審查，現行的程式碼品質問責機制已不足以應對這個規模。公共系統、醫療軟體、金融基礎設施若採用未充分審查的 AI 程式碼，後果不只是技術債，而是真實世界的安全風險。\n\n#### 長期趨勢預測\n\n短期內（1-2 年），技術債問題將持續累積，直到幾個高知名度的線上事故迫使產業建立更嚴格的 AI 程式碼審查標準。\n\n中期（3-5 年），能夠自動審查 AI 生成程式碼的工具 (AI-on-AI auditing) 將成為新興市場，靜態分析與形式驗證工具將迎來需求爆發。\n\n長期來看，「前端失落十年」的歷史教訓顯示：在技術能力被抽象化後，重建底層知識比預防失去更昂貴。現在投資工程師底層技能培訓的成本，遠低於未來除錯無人能理解的 AI 生成程式碼的代價。",{"category":229,"source":10,"title":230,"subtitle":231,"publishDate":6,"tier1Source":232,"supplementSources":235,"tldr":252,"context":261,"mechanics":262,"benchmark":263,"useCases":264,"engineerLens":273,"businessLens":274,"devilsAdvocate":275,"community":279,"hypeScore":136,"hypeMax":80,"adoptionAdvice":296,"actionItems":297},"tech","Qwen 3.6 在雙 4060 Ti 上跑出 125 tok/s：消費級 GPU 的推論性價比革命","MoE 架構加上 Q4_K_XL 量化，讓 35B 模型首次在千元級雙卡方案上達到實用推論速度",{"name":233,"url":234},"Reddit r/LocalLLaMA — 125 tok/s for Qwen3.6 q4xl on 2x 4060ti","https://www.reddit.com/r/LocalLLaMA/comments/1tryp2q/125_toks_for_qwen36_q4xl_on_2x_4060ti_is_insane/",[236,240,244,248],{"name":237,"url":238,"detail":239},"Qwen3.6-35B-A3B — Hugging Face","https://huggingface.co/Qwen/Qwen3.6-35B-A3B","模型架構說明、Apache 2.0 授權與量化版本下載",{"name":241,"url":242,"detail":243},"FP4 Just Landed in llama.cpp: NVFP4 vs MXFP4 Explained — InsiderLLM","https://insiderllm.com/guides/fp4-inference-llamacpp-nvfp4-mxfp4/","NVFP4 量化格式技術分析與品質對比",{"name":245,"url":246,"detail":247},"The Definitive GPU Ranking for LLMs — hardware-corner.net","https://www.hardware-corner.net/gpu-ranking-local-llm/","消費級 GPU 本地推論性價比排行",{"name":249,"url":250,"detail":251},"llama.cpp NVFP4 native support on Blackwell — NVIDIA Developer Forums","https://forums.developer.nvidia.com/t/llama-cpp-nvfp4-native-support-on-blackwell/368430","Blackwell sm_120 NVFP4 原生支援的官方開發者討論",{"tagline":253,"points":254},"花 4090 六成的錢，跑完整 35B 模型達 125 tok/s，消費級本地推論新里程碑",[255,257,259],{"label":33,"text":256},"Qwen3.6-35B-A3B 採用 Gated DeltaNet 線性注意力加 Sparse MoE(256 expert) ，推論活躍參數僅 3B；Q4_K_XL 量化後在雙 4060 Ti 上實現每秒 125 個 token 的生成速度。",{"label":36,"text":258},"兩張 RTX 4060 Ti 16GB 合計 32GB VRAM，市場總價約為單張 RTX 4090 的 60–70%，且 4090 的 24GB 在此模型規格下可能面臨 VRAM 不足的限制。",{"label":39,"text":260},"NVFP4 量化在 Ada Lovelace 架構 (sm_89) 無速度提升，記憶體頻寬 (288 vs 1,008 GB/s) 仍是本地推論核心瓶頸，現階段 Q4_K_XL 是更穩妥的格式選擇。","#### Qwen 3.6 q4xl 消費級硬體實測數據\n\n2026 年 5 月，一篇 r/LocalLLaMA 貼文在社群引發轟動：一位玩家用兩張 RTX 4060 Ti（共 32GB VRAM），搭配 Q4_K_XL 量化版本，成功讓 Qwen3.6-35B-A3B 跑出 **125 tok/s** 的生成速度。\n\nQwen3.6-35B-A3B 於 2026-04-15 由阿里巴巴發布，採用全新 Gated DeltaNet 線性注意力架構與 Sparse MoE 設計（256 個 expert，每次路由 8 個加 1 個共享），原生支援多模態輸入與最長 262K 的 context 視窗。\n\n> **名詞解釋**\n> **Sparse MoE(Sparse Mixture of Experts)**：一種將模型分成多個「專家」子網路的架構，每次推論只啟動少數專家，讓模型參數總量很大但實際運算量相對精簡。Qwen3.6-35B-A3B 雖有 35B 參數，每次推論僅用約 3B 活躍參數。\n\n這個成績之所以讓社群稱為「insane perf/dollar」，關鍵在於 Q4_K_XL 量化讓整個模型塞進雙卡 32GB VRAM，而兩張 4060 Ti 的市場總價遠低於單張 RTX 4090，實測速度卻仍具競爭力。\n\n#### nvfp4 量化的爭議與 sm_120 支援現況\n\nllama.cpp 於 2026-04-29(build b8967) 正式為 Blackwell 架構 (sm_120) 啟用 NVFP4 tensor core 原生路徑，prefill 速度據稱提升 43–68%。然而這對 4060 Ti 用戶幾乎沒有意義——Ada Lovelace 架構 (sm_89) 不具備 FP4 tensor core，NVFP4 在此只能獲得記憶體節省效益，無任何速度加成。\n\n> **名詞解釋**\n> **NVFP4**：NVIDIA 專有的 4-bit 浮點數格式，需要硬體 tensor core 原生支援才能獲得速度提升。Blackwell（RTX 50 系列）才有此硬體；Ada Lovelace（RTX 40 系列）只能透過模擬執行，僅省記憶體不加速。\n\n社群對 NVFP4 的評價出現明顯分歧。u/jtjstock 直接批評「NVFP4 在 llama 上目前很爛」，而 u/Xp_12 更細緻地指出，問題根源在於量化配方品質（KLD 偏差）與 sm_120 加速支援尚未完整，並非格式本身有根本缺陷——w4a16 相對穩定，w4a4 的高品質配方難覓，但 vllm 的 b12x 支援正在推進。\n\nInsiderLLM 的分析也印證，NVFP4 與 Q4_K_M 的品質對比尚無定論，現階段在非 Blackwell 硬體上選用 K-quant 格式仍是更穩定的選擇。\n\n#### 性價比分析：為何 4060 Ti 成為本地推論新寵\n\n記憶體頻寬是本地 LLM 推論最關鍵的瓶頸。RTX 4060 Ti 的 128-bit 匯流排僅提供 288 GB/s，而 RTX 4090 的 384-bit 匯流排可達 1,008 GB/s——後者是前者的 3.5 倍。\n\n然而，雙卡 4060 Ti 方案的邏輯不在於頻寬碾壓，而在於 VRAM 容量解鎖：兩張 4060 Ti 16GB 合計 32GB，足以完整載入 Qwen3.6-35B-A3B Q4_K_XL，而單張 4090 的 24GB 在此規格下恐面臨 VRAM 不足的限制。\n\n> **白話比喻**\n> 把模型想成一本超厚字典，4060 Ti 是普通書架，4090 是寬版書架但只有一個。兩個普通書架合在一起放得下這本超厚字典；一個寬版書架因為長度不夠反而塞不進去——這就是 32GB vs 24GB 的本質差異。\n\nhardware-corner.net 的 GPU 排行榜也印證，對需要大 VRAM 的模型而言，雙卡低階方案的性價比往往優於高階單卡，兩張 4060 Ti 總價約為單張 4090 的 60–70%。\n\n#### 本地 LLM 推論的未來展望\n\n此次 Qwen3.6 實測的意義，不只是一個跑分紀錄，而是一個更廣泛的訊號：消費級硬體組合正在趕上主流 35B 級模型的實用門檻，生成速度已足以支撐真實的本地 agentic 工作流程。\n\nMike Masnick 在 Bluesky 分享，他花了整個週末將 agentic 設定切換到以本地模型為主（Gemma 4 31B 與 Qwen3.6-35B-A3B），結論是「本地模型現在真的很厲害」，印證了社群信心正在快速上升。\n\n從架構角度看，MoE 設計（活躍參數 3B）讓大參數模型在有限算力下實現高速生成，這個趨勢將持續推動「低預算跑大模型」的可能性邊界。當 sm_120 的 NVFP4 路徑成熟後，下一代消費級 GPU 的推論速度可望再有明顯躍升。","Qwen3.6-35B-A3B 的高速本地推論是三個技術決策協同作用的結果：線性注意力降低長序列計算量、稀疏專家路由壓縮活躍算力、量化策略在精度與速度間取得平衡。\n\n#### 機制 1：Gated DeltaNet 線性注意力\n\n傳統 Transformer 的注意力計算複雜度是 O(n²) ，隨 context 長度呈平方增長。Gated DeltaNet 引入線性注意力近似，將複雜度降至 O(n) ，使 262K context 視窗在有限記憶體下成為可能。\n\n「Gated」機制加入可學習的閘控層，改善了原版線性注意力在局部模式學習上的弱點，在長序列推論中提供更穩定的梯度流，讓模型長文本理解品質更接近標準注意力。\n\n> **名詞解釋**\n> **DeltaNet**：一種將注意力機制轉化為遞迴形式的線性注意力架構，透過差分更新 (delta) 計算注意力，避免全序列的二次複雜度。Gated 版本加入閘控機制後，在局部模式學習與長程依賴之間取得更好的平衡。\n\n#### 機制 2：Sparse MoE(256 experts)\n\n模型擁有 256 個 expert 子網路，每次 token 生成只啟動 8 個路由 expert 加 1 個共享 expert，實際活躍參數約 3B。這讓「35B 模型」的推論計算成本接近 3B 模型，而知識容量卻來自完整 256 個 expert 的訓練積累。\n\n對消費級硬體而言，這意味著每次生成的計算量大幅減少，算力瓶頸顯著降低，Q4_K_XL 量化的速度損耗在實際體驗中更能被接受。\n\n#### 機制 3：Q4_K_XL 量化策略\n\nQ4_K_XL 是 K-quant 家族的 extra-large 變體，相比廣泛使用的 Q4_K_M（HuggingFace 上逾 13.5 萬個模型採用），它在 4-bit 記憶體佔用的基礎上採用更高混合精度配置，在關鍵層保留更高精度，輸出品質更接近全精度模型。\n\n對 4060 Ti 這類頻寬受限的架構，Q4_K_XL 比 NVFP4 更合適——前者有成熟的量化配方與廣泛的社群驗證，後者在 Ada Lovelace 上無速度提升，且 w4a4 高品質配方難覓。\n\n> **白話比喻**\n> 把量化想成把高清影片壓縮成較小的檔案：Q4_K_XL 是智慧壓縮，在重要場景自動保留高畫質；NVFP4 是下一代壓縮格式，在支援它的新型播放器 (Blackwell GPU) 上極快，但在舊播放器 (4060 Ti) 上只省空間、播放速度不變。","#### 主要實測數據\n\n- **平台**：雙 RTX 4060 Ti 16GB（共 32GB VRAM），PCIe 分散推論\n- **模型**：Qwen3.6-35B-A3B Q4_K_XL\n- **生成速度**：125 tok/s\n- **成本比較**：雙 4060 Ti 約為單張 4090 的 60–70% 市場價\n\n#### 架構加速參考（llama.cpp build b8967，僅適用 Blackwell sm_120）\n\n- **prefill 提升**：43–68%（Blackwell 架構，FP4 tensor core 原生路徑）\n- **Ada Lovelace(sm_89) 提升**：0%（無 FP4 tensor core，僅記憶體節省）\n\n#### 記憶體頻寬對比\n\n- **RTX 4060 Ti**：128-bit 匯流排，288 GB/s\n- **RTX 4090**：384-bit 匯流排，1,008 GB/s（約為 4060 Ti 的 3.5 倍）\n\n#### SWE-Bench Verified 參考對比\n\n- **Opus 4.7**：87.6%（模型約 5T 參數）\n- **Qwen3.6-35B-A3B**：73.4%（推論活躍參數 3B，本地免費執行，無速率限制）",{"recommended":265,"avoid":269},[266,267,268],"本地創意寫作與程式碼生成：125 tok/s 的速度足以支撐流暢的互動式對話體驗","長文摘要與 RAG 應用：262K context 視窗大幅減少分批處理需求","隱私敏感場景的本地 agentic 工作流程：資料不離本地，有效替代雲端 API",[270,271,272],"需要 FP4 tensor core 加速的批次推論：4060 Ti(sm_89) 無此硬體，NVFP4 無速度提升","超低延遲即時服務 (TTFT \u003C 50ms) ：4060 Ti 頻寬限制導致 prefill 速度遜於 4090","單卡部署：Q4_K_XL 版本需至少 22–24 GB VRAM，單張 4060 Ti 16GB 無法完整載入","#### 環境需求\n\n- 兩張 RTX 4060 Ti 16GB（VRAM 合計 32GB）\n- llama.cpp build b8967+（推薦最新穩定版）\n- CUDA 12.4+（Ada Lovelace sm_89 支援）\n- 磁碟空間：Q4_K_XL 量化版本約 22–24 GB\n- 主機板需有兩個 PCIe 插槽（建議 x16 + x8 以上，避免 x4 頻寬限制）\n\n#### 最小 PoC\n\n```bash\n# 1. 下載模型\nhuggingface-cli download Qwen/Qwen3.6-35B-A3B-GGUF \\\n  --include \"qwen3.6-35b-a3b-q4_k_xl.gguf\" \\\n  --local-dir ./models\n\n# 2. 執行（雙 GPU tensor split）\n./llama-cli \\\n  -m ./models/qwen3.6-35b-a3b-q4_k_xl.gguf \\\n  -ngl 99 \\\n  --tensor-split 1,1 \\\n  --ctx-size 8192 \\\n  -p \"請介紹 Qwen3.6 的架構特色\" \\\n  -n 256\n```\n\n#### 驗測規劃\n\n首次執行後，觀察終端輸出的 `eval time` 欄位，確認 token/s 在 100 以上（受記憶體頻寬限制，實際值因 prompt 長度與 context 大小可能浮動 ±20%）。\n\n同時用 `nvidia-smi dmon` 監控雙卡 VRAM 使用量，確認模型分攤至兩卡，無單卡溢出 (OOM) 現象。\n\n#### 常見陷阱\n\n- **--tensor-split 比例不當**：兩卡規格相同時設為 `1,1`，規格不同時需依 VRAM 比例調整，否則負載不均導致其中一卡 OOM\n- **ctx-size 過大**：262K context 需要大量額外 KV cache 記憶體，建議從 8K–16K 開始測試\n- **NVFP4 誤用**：在 Ada Lovelace 硬體上載入 NVFP4 版本，速度不會提升，可能因格式相容性出現品質下降\n- **主機板 PCIe 頻寬**：若第二插槽為 x4，跨卡傳輸受限，實際速度可能低於 125 tok/s 實測值\n\n#### 上線檢核清單\n\n- 觀測：`eval time` (token/s) 、雙卡 VRAM 使用率 (nvidia-smi) 、GPU 溫度（防止降頻）\n- 成本：兩張 4060 Ti TDP 各約 165W，峰值合計 ~330W，需確認電源供應器容量\n- 風險：PCIe 插槽頻寬限制、跨卡無 NVLink（4060 Ti 不支援 NVLink，依賴 PCIe 分散，延遲高於 NVLink 方案）","#### 競爭版圖\n\n- **直接競品**：Meta Llama 4 Scout（同為 MoE 架構，活躍參數接近）、Google Gemma 4 31B（本地推論玩家常見替代，與 Qwen3.6 並列測試）、Mistral 22B（參數較小，能力有差距）\n- **間接競品**：商業 API 服務（Claude Haiku、GPT-4o mini）——不在乎隱私的場景替代\n\n#### 護城河類型\n\n- **工程護城河**：Gated DeltaNet + Sparse MoE 的架構研發與大規模訓練資源投入，非開源社群短期可複製\n- **生態護城河**：Qwen 系列在 GGUF 社群已累積大量量化版本與社群實測，llama.cpp 對 Qwen 的支援成熟度名列前茅\n\n#### 定價策略\n\nQwen3.6-35B-A3B 以 Apache 2.0 授權開源，本地部署零授權費。阿里巴巴同步提供 Qwen API 雲端服務（按 token 計費），形成「本地試用—雲端生產」的雙軌路徑，降低開發者評估門檻。\n\n#### 企業導入阻力\n\n- 雙 GPU 機器的硬體採購與維護成本對中小企業仍有一定門檻\n- 量化格式選擇 (Q4_K_XL vs NVFP4) 需要具備評估能力的技術人力\n- 無 NVLink 的雙 4060 Ti 方案在企業 IT 標準採購流程中屬非典型配置\n\n#### 第二序影響\n\n- 消費級多卡方案普及，可能推動 llama.cpp tensor split 效能進一步最佳化\n- 本地推論速度提升削弱商業 API 在延遲和成本上的差異化優勢，影響定價談判籌碼\n- Sparse MoE 在本地推論的成功，將加速其他廠商在開源 MoE 模型上的競爭投入\n\n#### 判決：值得部署（高性價比、生態成熟、Apache 2.0）\n\nQwen3.6-35B-A3B Q4_K_XL 在雙 4060 Ti 上的表現，已達到實用本地推論的速度門檻，且成本低於高階單卡方案。對有本地部署需求、注重性價比的開發者，這是目前 35B 級開源模型中最具競爭力的組合之一。",[276,277,278],"125 tok/s 的成績是在特定 context 長度下測得，實際 agentic 多輪對話因 KV cache 累積，速度可能顯著下滑，不代表真實工作流程的平均吞吐量。","雙 4060 Ti 的性價比邏輯建立在 4090「24GB 不夠用」的前提上，若未來高 VRAM 消費卡（如 RTX 5080 24GB+）價格進一步下探，雙卡方案的 PCIe 傳輸延遲劣勢將更加明顯。","Sparse MoE 的實際能力仍落後閉源旗艦 (SWE-Bench 73.4% vs Opus 87.6%) ，對精度要求高的企業任務，性價比論述在品質差距縮小前有其侷限。",[280,284,287,290,293],{"platform":281,"user":282,"quote":283},"Reddit r/LocalLLaMA","u/jtjstock","NVFP4 在 llama 上目前很爛",{"platform":281,"user":285,"quote":286},"u/see_spot_ruminate","幹得好！記憶體頻寬原教旨主義者馬上就會湧入了。",{"platform":281,"user":288,"quote":289},"u/Xp_12","NVFP4 本身還好，主要問題是量化配方影響 KLD，加上 sm_120 的加速支援尚未完整。w4a4 的好配方很難找，w4a16 勉強可用。不過支援仍在推進，vllm 的 b12x 初步支援也快來了。",{"platform":69,"user":291,"quote":292},"masnick.com（Mike Masnick，60 likes）","花了週五晚上和整個週六，把我的 agentic 設定切換到大部分使用本地模型（Gemma 4 31B 和 Qwen3.6-35B-A3B）……只是測試階段，但……本地模型現在真的很厲害。",{"platform":73,"user":294,"quote":295},"@Hesamation","Opus 4.7 約有 5T 參數，Qwen3.6 推論時僅用 3B 參數。SWE-Bench Verified 分數：Opus 4.7 為 87.6%，Qwen3.6-35B-A3B 為 73.4%。沒有速率限制，免費本地執行。差距確實存在，但這個性價比真的令人印象深刻。","值得一試",[298,300,302],{"type":84,"text":299},"用 llama.cpp 的 --tensor-split 1,1 在雙 4060 Ti 上跑 Qwen3.6-35B-A3B Q4_K_XL，基準測試生成速度是否達到 100 tok/s 以上，並用 nvidia-smi 確認雙卡 VRAM 均衡分配",{"type":87,"text":301},"基於 262K context 視窗，嘗試建構本地 RAG 或長文摘要 pipeline，測試在真實多輪任務中的吞吐量與品質，與雲端 API 進行成本效益比較",{"type":90,"text":303},"追蹤 llama.cpp 對 Blackwell sm_120 的 NVFP4 成熟度進展與 vllm b12x 支援——當配方品質穩定後，下一代消費卡（RTX 50 系列）的推論速度可望有明顯躍升",[305,332,363,399,429,463,497,527,556],{"category":306,"source":11,"title":307,"publishDate":6,"tier1Source":308,"supplementSources":311,"coreInfo":318,"engineerView":319,"businessView":320,"viewALabel":321,"viewBLabel":322,"bench":323,"communityQuotes":324,"verdict":137,"impact":331},"funding","SoftBank 宣布投資 750 億歐元在法國建設 AI 資料中心",{"name":309,"url":310},"TechCrunch","https://techcrunch.com/2026/05/30/softbank-says-it-will-invest-up-to-e75-billion-to-build-french-data-centers/",[312,315],{"name":313,"url":314},"SoftBank Group 官方新聞稿","https://group.softbank/en/news/press/20260531_0",{"name":316,"url":317},"Fortune","https://fortune.com/2026/05/30/softbank-75-billion-investment-french-ai-data-centers-masayoshi-son-emmanuel-macron/","#### 投資規模與時程\n\nSoftBank 於 2026 年 5 月 30 日在法國「選擇法國」峰會宣布，將投資最高 **750 億歐元**（約 870 億美元）在法國建設 AI 資料中心，稱為「歐洲最大 AI 基礎設施投資」。第一階段承諾投入 **450 億歐元**，目標建置 **3.1 吉瓦 (GW)** 容量，預計 2031 年完成；首座 2028 年啟用，最終目標 **5 吉瓦**。\n\n> **名詞解釋**\n> 吉瓦 (GW) ：10 億瓦特，此處指資料中心總電力容量；3.1 GW 約相當於一座大型核電廠的輸出規模。\n\n#### 選址優勢：清潔能源牌\n\n三個選址均位於法國北部大區 (Hauts-de-France) ：敦克爾克 (Loon-Plage) 、Bosquel 及 Bouchain。SoftBank 特別強調法國 **95% 去碳化電力**的優勢，與其美國俄亥俄州計畫依賴天然氣電廠的現況形成對比，顯示清潔能源供給已成 AI 基礎設施跨國選址的關鍵籌碼。","法國 95% 無碳電力直接降低 PUE（電源使用效率）成本與碳排合規壓力。3.1 GW 是單一國家罕見的巨量承諾，散熱工程、電力合約結構與網路互連設計都將面臨新規模挑戰。若 SoftBank-OpenAI 訓練叢集確實落地，歐洲區 AI 基礎建設工程師的職缺需求將顯著成長。","此筆投資顯示 AI 基礎設施競賽已擴展至歐洲主權市場——法國以稅務優惠與電力保障換取資本流入，為其他歐洲國家提供可複製的招商框架。惟 SoftBank 同時身兼 OpenAI 股東與客戶，資金循環性問題 (circularity) 已引起市場關注，投資決策的獨立性值得持續追蹤。","技術基礎設施評估","市場與投資觀點","",[325,328],{"platform":73,"user":326,"quote":327},"@ShanuMathew93","OpenAI 與 SoftBank 各自投資 5 億美元於 SB Energy，用於德州資料中心開發，是進行中 5,000 億美元 Stargate 計畫的一部分。SoftBank 現持有 SB Energy 大量股份，同時另行承諾 410 億美元投資 OpenAI。此交易加深了外界對資金循環性的疑慮。",{"platform":73,"user":329,"quote":330},"@Jukanlosreve","摩根大通指出：SoftBank 自身的 AI 算力需求，未來幾年可能為博通 (Broadcom) 帶來 100 萬顆 XPU 叢集的矽晶片市場機會（潛在營收 300 億美元）——尤其是在 SoftBank 宣布 Stargate 等 5,000 億美元 AI 投資計畫之後。","SoftBank 750 億歐元押注歐洲 AI 基礎設施，加速清潔能源資料中心競賽，重塑歐洲 AI 算力版圖。",{"category":333,"source":11,"title":334,"publishDate":6,"tier1Source":335,"supplementSources":338,"coreInfo":350,"engineerView":351,"businessView":352,"viewALabel":353,"viewBLabel":354,"bench":323,"communityQuotes":355,"verdict":137,"impact":362},"policy","攻擊者利用 ChatGPT 與 Claude 分享對話功能散布惡意程式",{"name":336,"url":337},"The Decoder","https://the-decoder.com/attackers-abuse-shared-chatgpt-and-claude-chats-to-spread-malware/",[339,343,346],{"name":340,"url":341,"detail":342},"BleepingComputer","https://www.bleepingcomputer.com/news/security/hackers-abuse-google-ads-claudeai-chats-to-push-mac-malware/","駭客濫用 Google 廣告與 Claude.ai 對話推送 Mac 惡意程式",{"name":340,"url":344,"detail":345},"https://www.bleepingcomputer.com/news/security/chatgpt-share-links-abused-to-host-fake-outage-pages-to-deliver-malware/","ChatGPT 分享連結被濫用架設假服務中斷頁面散布惡意程式",{"name":347,"url":348,"detail":349},"Help Net Security","https://www.helpnetsecurity.com/2026/05/27/deno-rat-malware-fake-chatgpt-claude-installers/","GitHub 上假冒 ChatGPT 與 Claude 安裝程式散布 Deno RAT 惡意程式","#### 攻擊手法：LLMShare\n\n資安機構 Push Security 將此類手法命名為「LLMShare」——攻擊者利用 ChatGPT(`chatgpt.com/s/`) 與 Claude(`claude.ai/share/`) 的正式分享連結散布惡意程式。由於連結托管於 OpenAI 與 Anthropic 的正式域名，安全過濾工具難以識別，用戶信任度也明顯較高，攻擊模式已擴展至 Grok，並有搭配 Google 廣告的版本。\n\n#### 兩條主要攻擊路徑\n\n- **ChatGPT 路徑**：偽造「服務中斷」頁面，誘導用戶前往惡意域名 `openew[.]app` 下載受感染安裝包，且該站點對掃描工具顯示無害內容 (cloaking) 。\n- **Claude 路徑**：惡意對話偽裝為「Apple Support」安裝指南，要求用戶開啟 Terminal 並貼上 base64 編碼命令，以 polymorphic delivery 技術在記憶體中執行，規避簽名偵測，最終植入 MacSync 竊取程式，竊取瀏覽器憑證、Cookies 及 macOS Keychain 內容。\n\n> **名詞解釋**\n> Polymorphic delivery：每次執行時自動變形程式碼，使特徵值不斷改變，讓傳統防毒軟體難以依靠固定特徵識別。\n\nGitHub 上另有假安裝程式搭載 Deno RAT，鎖定 50+ 種加密貨幣錢包擴充套件，透過 Chrome DevTools Protocol 竊取螢幕影像，相關推廣影片累積觀看逾 5 萬次。","惡意流量來自受信任的 AI 服務正式域名，傳統 URL 過濾與域名黑名單已完全失效。工程師應更新端點防護規則：\n\n- 加入 base64 命令執行的行為偵測規則\n- 監控從 AI 分享頁面觸發的 Terminal 指令\n- 封鎖已知 IoC：`openew[.]app`、SHA256 `de8c50e8...ec2dde78`\n\nmacOS Keychain 與瀏覽器憑證為主要目標，應列入安全稽核優先項目；同時需重新評估企業 AI 工具存取政策。","攻擊刻意鎖定非技術用戶——對 AI 感到好奇的員工也可能點入偽裝成官方安裝指南的惡意對話。由於連結域名合法，傳統資安意識培訓（「不點陌生連結」）幾乎失去效果。\n\n企業應評估是否禁止員工透過個人裝置存取 AI 共享連結、是否要求 AI 工具安裝走 IT 核准流程。MacSync 竊取程式可竊取企業 SSO Cookies，一旦成功可能引發更廣泛的帳號接管事件。","合規實作影響","企業風險與成本",[356,359],{"platform":73,"user":357,"quote":358},"@wiz_io（Wiz 雲端資安公司）","🤖 我們正在目睹前所未有的 AI 代理現象：惡意程式直接在受害者機器上即時呼叫 ChatGPT、Claude 等大型語言模型來撰寫攻擊程式碼。@0xdabbad00 指出了一個攻擊者從惡意酬載中直接調用 AI 的新興趨勢。",{"platform":73,"user":360,"quote":361},"@TheHackersNews（The Hacker News 資安媒體）","⚠️ 警告——一個惡意 npm 套件遭發現竊取 Claude AI 用戶 `/mnt/user-data` 目錄中的檔案，並上傳至攻擊者控制的 GitHub 儲存庫。請檢查你安裝的套件。該套件名為「mouse5212-super-formatter」，使用了...","LLMShare 手法利用正規 AI 服務域名繞過安全過濾，攻擊面涵蓋所有對 AI 工具感到好奇的非技術用戶，企業端點防護與資安培訓策略需全面調整應對。",{"category":93,"source":14,"title":364,"publishDate":6,"tier1Source":365,"supplementSources":367,"coreInfo":376,"engineerView":377,"businessView":378,"viewALabel":379,"viewBLabel":380,"bench":323,"communityQuotes":381,"verdict":397,"impact":398},"GitHub Copilot 改 Token 計費引發開發者群情激憤",{"name":309,"url":366},"https://techcrunch.com/2026/05/30/what-a-joke-github-copilots-new-token-based-billing-spurs-consternation-among-devs/",[368,372],{"name":369,"url":370,"detail":371},"GitHub Blog","https://github.blog/news-insights/company-news/github-copilot-is-moving-to-usage-based-billing/","官方公告",{"name":373,"url":374,"detail":375},"GitHub Community Discussion #192948","https://github.com/orgs/community/discussions/192948","超過 400 則社群留言","#### 計費模式大翻轉\n\n2026 年 6 月 1 日起，GitHub Copilot 從「固定月費 + 進階請求次數」切換為「Token 用量計費」。訂閱費用本身不變（Pro $10／月、Business $19／用戶／月、Enterprise $39／用戶／月），但每月額度改為等值 GitHub AI Credits，input、output 與 cached tokens 皆依各模型 API 定價扣抵。\n\n> **名詞解釋**\n> GitHub AI Credits 是 Copilot 的新計量單位，每筆對話依實際 token 消耗量計費，類似電話帳單從「包月通話」改為「依分鐘計費」。\n\n#### 問題核心：Agentic Session 成本爆炸\n\n關鍵矛盾在於 agentic coding session——Copilot 自主規劃、研究並執行多步驟任務時，單次 session 可消耗 $30–$40 的 Credits。\n\nBusiness 方案每月僅提供 $30 額度（促銷至 2026 年 8 月），意味著一次 agentic session 就可能耗光整月配額。社群截圖顯示帳單從每月 $29 飆至 $750，乃至 $39 方案用量換算後達 $5,851.77。官方公告帖在短時間內累積逾 400 則留言、近 900 個倒讚。","Token 計費等同每次 prompt 後面掛了一張帳單，agentic workflow 用量難以預測。建議：\n\n1. 嚴格限制 autonomous coding session，改用明確指令的單步提問\n2. 縮小 context window，避免重複傳遞大型 codebase\n3. 評估替代方案（Claude Code API、OpenAI Codex）的 token 成本透明度\n\n短期最直接的應對是計算自己的典型 session 消耗，再對比新方案額度。","多家企業已估算成本將增加 4 倍以上，而 Enterprise 每月僅 $70 Credits 遠不敷重度 agentic 使用。\n\nMicrosoft 改版背後是補貼時代的終結——舊定額方案長期虧損。企業現在需要評估：\n\n1. 是否繼續採購 Copilot，或轉向按需計費更透明的工具\n2. 限制 agentic session 使用範圍，避免帳單失控\n3. 觀察 Microsoft 是否在社群壓力下調整額度，再作長期決策","實務觀點","產業結構影響",[382,385,388,391,394],{"platform":69,"user":383,"quote":384},"carnage4life.bsky.social（Dare Obasanjo，126 likes）","如果你想知道 AI 廠商對 token 補貼了多少，看看 GitHub Copilot 用戶在下個月用量計費模式上線後，按現有用量會被收多少費就清楚了。",{"platform":69,"user":386,"quote":387},"jcmanke.bsky.social（Joe Manke，8 likes）","公司剛發了通知：「由於 GitHub Copilot 改為用量計費，我們預估成本將增加 4 倍。」我會繼續完全不使用它，為公司節省開支盡一份力。",{"platform":62,"user":389,"quote":390},"simonw(Hacker News)","我找到了一個案例——Reddit 上有人訂閱費 $39，若換算為用量計費則需 $5,851.77。",{"platform":62,"user":392,"quote":393},"vmbm(Hacker News)","用戶在固定費率方案上確實走得太遠了。很多人在 $10–$200／月的方案下玩 agentic workflow，然後在企業帳號正式部署，沒意識到按 API 計費的成本可能達到 10–100 倍。用啤酒錢跑幾百個 agent 很爽，但換成遊艇錢就不好玩了。",{"platform":73,"user":395,"quote":396},"@hkarthik（X 用戶）","我預測 GitHub 到 2026 年底將對所有版本控制操作改為用量計費。Copilot 只是他們在試驗計費基礎設施和市場反應。","觀望","Copilot agentic 使用者帳單可能暴增 10–100 倍，企業應立即審視用量並評估是否轉向其他 AI coding 工具。",{"category":93,"source":9,"title":400,"publishDate":6,"tier1Source":401,"supplementSources":404,"coreInfo":412,"engineerView":413,"businessView":414,"viewALabel":379,"viewBLabel":380,"bench":323,"communityQuotes":415,"verdict":137,"impact":428},"Terence Tao：AI 將首次為數學研究帶來分工合作",{"name":402,"url":403},"Terry Tao's Blog（arXiv 預印本）","https://terrytao.wordpress.com/2026/03/29/mathematical-methods-and-human-thought-in-the-age-of-ai/",[405,408],{"name":336,"url":406,"detail":407},"https://the-decoder.com/terence-tao-argues-ai-could-bring-division-of-labor-to-math-for-the-first-time-in-history/","事件報導與背景分析",{"name":409,"url":410,"detail":411},"OpenAI Academy","https://academy.openai.com/public/blogs/terence-tao-ai-is-ready-for-primetime-in-math-and-theoretical-physics-2026-03-06","IPAM 研討會發言摘要","此報導源自 2026 年 3 月的 IPAM 研討會及同月 arXiv 預印本，近期因學術社群廣泛引用而重新引發熱議。\n\n#### AI 打破數學研究的孤島結構\n\n菲爾茲獎得主陶哲軒 (Terence Tao) 宣告，AI 已「準備好進入黃金時代」。他指出，數學研究史上從未有分工——從問題定義到論文發表，向來由同一人獨力完成。AI 有潛力打破此孤島，催生「工業數學」：大型 AI 輔助團隊同步追求更廣泛議題，縮減個別深度、擴大整體覆蓋。\n\n#### 驗證才是成敗關鍵\n\n陶哲軒警告，有效運用 AI 的程度與驗證嚴謹度成正比，否則只會堆積未測試的想法。他提出「數學嗅覺」概念——資深數學家能在逐行驗證前直覺判斷證明可信度。形式驗證工具（如 Lean）是防止邏輯脆弱論證偷渡的關鍵防線。\n\n> **名詞解釋**\n> 形式驗證：以數學方式逐步確認每個推理步驟正確；Lean 是數學社群主流的形式驗證語言。","Tao 的框架為工具選用提供清晰指引：形式驗證能力比單純生成流暢度更具長期價值。\n\n目前實際可用的場景：文獻搜尋（數週壓縮至數分鐘）、候選程式碼生成、可行性探索。但「選對問題」與驗證結果仍是人類不可外包的核心任務。若所在機構有嚴謹的驗證流程，現在是整合 AI 輔助工具的合適時機。","陶哲軒的「工業數學」願景預示研究機構架構轉變：從明星研究員單打獨鬥，轉向以 AI 為中介的大型協作團隊。\n\n對 AI 工具廠商而言，學術市場將更重視嚴謹驗證能力，而非流暢生成；能整合形式驗證的平台將獲得競爭優勢。菲爾茲獎得主公開背書，亦將加速其他學術機構跟進採用。",[416,419,422,425],{"platform":73,"user":417,"quote":418},"@DrJimFan（NVIDIA 資深研究科學家）","所有人都應該閱讀陶哲軒關於 LLM 的部落格。他預測，結合搜尋與符號數學工具後，AI 將在 2026 年成為數學研究中可信賴的共同作者。我相信數學將是第一個見證突破的科學領域。",{"platform":73,"user":420,"quote":421},"@dwarkesh_sp（科技播客主持人）","陶哲軒認為，AI 已非常擅長應用現有、充分理解的數學技術解決問題。關鍵問題是：有多少數學難題能以這種方式解決，而無需發展任何新想法？",{"platform":62,"user":423,"quote":424},"the13（HN 用戶）","AI 現在比幾個月前更強大、更精準。相較於原文作者情感真摯但已顯過時的論點，陶哲軒對我而言更具可信度。",{"platform":69,"user":426,"quote":427},"StartupHub AI（Bluesky，1 like）","評分 8.7 分——陶哲軒解釋 AI 如何透過降低認知摩擦、自動化複雜任務，快速改變數學研究格局。","陶哲軒背書加速學術界採用 AI 輔助研究，形式驗證工具與 AI 整合成為下一波競爭焦點。",{"category":229,"source":13,"title":430,"publishDate":6,"tier1Source":431,"supplementSources":433,"coreInfo":441,"engineerView":442,"businessView":443,"viewALabel":444,"viewBLabel":445,"bench":323,"communityQuotes":446,"verdict":137,"impact":462},"Meta 秘密開發 AI 吊墜，穿戴式 AI 硬體戰線再擴大",{"name":309,"url":432},"https://techcrunch.com/2026/05/30/meta-is-reportedly-developing-an-ai-pendant/",[434,437],{"name":336,"url":435,"detail":436},"https://the-decoder.com/metas-leaked-memo-reveals-ai-pendant-supersensing-glasses-and-enterprise-wearables-strategy/","洩露備忘錄全文分析",{"name":438,"url":439,"detail":440},"The Next Web","https://thenextweb.com/news/meta-ai-pendant-limitless-wearables-for-work","Limitless 收購細節與企業訂閱方案","#### 吊墜計畫與三大策略支柱\n\nMeta 正秘密開發一款可夾附衣物或掛頸佩戴的 AI 吊墜，由穿戴式裝置副總裁 Alex Himel 的內部備忘錄確認。\n\n吊墜技術來自 Meta 2025 年底收購的新創 Limitless，後者原售 99 美元錄音穿戴裝置，背後投資人包含 Sam Altman 與 a16z。收購後 Limitless 停售原有產品，技術直接納入 Meta 路線圖。\n\n備忘錄同時揭露另外兩大策略支柱：搭載持續攝影機的超感知眼鏡，以及企業訂閱服務「Wearables for Work」。\n\n> **名詞解釋**\n> 超感知眼鏡 (supersensing glasses) ：配備持續運作攝影機與多元感測器的智慧眼鏡，可即時追蹤日常活動並提供情境提醒。\n\n#### 技術規格與商業目標\n\n所有裝置由 Meta 最新 AI 模型 Muse Spark 驅動，並整合尚未發布的 AI agent「Hatch」。訂閱制分兩層：Meta One Plus（$7.99／月）與 Meta One Premium（$19.99／月）。\n\n內部狗糧測試預計 2027 年春季啟動；2026 年下半年整體穿戴裝置銷售目標為 1,000 萬台。","Muse Spark 與 Hatch agent 的整合架構尚未公開，但持續錄音穿戴裝置對推論效能與隱私架構提出雙重挑戰。\n\n邊緣運算能力將決定是否需要持續上傳音訊串流——若採雲端處理，隱私保護架構須在設計初期鎖定。Limitless 已有成熟的對話錄製與摘要管線，Meta 需決定是沿用或全面整合進自家 AI 堆疊。開發者平台開放後，第三方穿戴式 AI 應用將成為新興整合場景。","Reality Labs 2026 年 Q1 虧損達 40 億美元，此次硬體多元佈局是降低財務壓力的關鍵賭注。\n\nMeta 透過收購 Limitless 直接取得已驗證的市場需求與用戶基礎，比從零開發更節省試錯成本。企業訂閱制若能轉換現有 700 萬眼鏡用戶，將為 Reality Labs 創造穩定的經常性收入。此舉同時對 Humane、Rabbit 等 AI 穿戴新創造成直接競爭壓力。","工程師視角","商業視角",[447,450,453,456,459],{"platform":69,"user":448,"quote":449},"Bluesky 用戶 (46 upvotes)","我預測企業執行長將強制員工配戴這類內建其 AI 分身的裝置，儘管我並不樂見這個結果。",{"platform":73,"user":451,"quote":452},"aakashg0(Product growth writer and investor)","Meta 花錢扼殺了一款 99 美元的 AI 吊墜，卻沒人追問原因。Limitless 獲 Sam Altman 和 a16z 投資 3,300 萬美元，開發出可錄製真實對話的穿戴裝置，並建立一批每月付 19 美元的永久記憶用戶基礎。Meta 週五完成收購，隨即……",{"platform":73,"user":454,"quote":455},"EvanKirstel(B2B tech influencer)","Meta 收購了 Limitless——一家獲 Sam Altman 投資、專為錄製與轉錄真實對話所設計的 AI 吊墜新創。Limitless 將停止銷售其 99 美元的 AI 吊墜並關閉 Rewind 桌面軟體，但現有用戶仍可繼續使用。",{"platform":69,"user":457,"quote":458},"Reuters(9 upvotes)","Meta 計畫推出 AI 吊墜及企業穿戴裝置方案以強化硬體佈局，The Information 報導。",{"platform":69,"user":460,"quote":461},"Bluesky 用戶 (2 upvotes)","Meta 據報正在開發 AI 吊墜，相關獨家報導已出爐。","Meta 以收購加自研雙軌策略快速切入 AI 穿戴市場，企業訂閱制若成型將重塑職場感知裝置競爭格局，持續錄音功能也將引發監管與隱私辯論。",{"category":306,"source":11,"title":464,"publishDate":6,"tier1Source":465,"supplementSources":468,"coreInfo":476,"engineerView":477,"businessView":478,"viewALabel":479,"viewBLabel":322,"bench":323,"communityQuotes":480,"verdict":397,"impact":496},"OpenRouter B 輪融資 1.13 億美元，LLM 路由市場升溫",{"name":466,"url":467},"OpenRouter Series B 官方公告","https://openrouter.ai/announcements/series-b",[469,472],{"name":309,"url":470,"detail":471},"https://techcrunch.com/2026/05/26/openrouter-more-than-doubles-valuation-to-1-3b-in-a-year/","估值翻倍報導",{"name":473,"url":474,"detail":475},"Hacker News 討論串","https://news.ycombinator.com/item?id=48338660","社群評論","#### 融資概況與投資陣容\n\nOpenRouter 於 2026 年 5 月 28 日完成 1.13 億美元 B 輪融資，估值達 13 億美元，較 11 個月前 A 輪（5.47 億美元）翻逾一倍。本輪由 CapitalG（Alphabet 旗下獨立成長基金）領投，戰略投資方涵蓋 NVentures（NVIDIA 創投）、Snowflake Ventures、Databricks Ventures 及 MongoDB Ventures；原有股東 a16z 與 Menlo Ventures 跟投。\n\n#### 規模與核心能力\n\nOpenRouter 連結 800 萬以上開發者與 400 個以上模型，過去六個月週處理量從 5 兆 tokens 成長至 25 兆 tokens（5 倍成長），全年預計突破千兆 (1 quadrillion)tokens。平台核心定位為「intelligent routing」——提供 provider failover、延遲最佳化、guardrails 及零資料保留 (zero-data-retention) 政策，協助企業從單一模型 pilot 過渡至多模型生產環境。","OpenRouter 路由層解決多模型環境三個痛點：provider failover 降低單點故障、延遲最佳化讓模型選擇動態化、guardrails 提供合規管控。\n\n然而社群指出關鍵問題：開源模型可能被路由至未明確標示量化程度的供應商，讓工程師誤以為使用完整模型，實際跑的卻是 4B 或 8B 量化縮減版。生產環境引入前，應確認供應商透明度或指定路由至可信供應商。","CapitalG、NVentures 與 Snowflake、Databricks 同時入股，暗示 LLM 路由正成為 AI 基礎設施標準層。年度收入超過 5,000 萬美元，商業模式已初步驗證。\n\n長期護城河仍存疑：若 LLM 市場整合至少數主流模型，路由溢價難以持續說服大客戶；各大雲端平台的原生路由服務是潛在競爭威脅。","技術實力評估",[481,484,487,490,493],{"platform":62,"user":482,"quote":483},"svnt","他們這樣做是因為做得到，因為這能作為社會認同，說服客戶他們正在做更深層有價值的事。而現實中，他們會利用這個管道，將你的客戶（及其託付的資料）作為未來的產品。",{"platform":62,"user":485,"quote":486},"aussieguy1234","OpenRouter 有個眾所皆知的問題：它會路由至品質低劣、對模型進行量化的供應商。你以為自己在用完整的 Kimi k2.6，背後卻是 4B 或 8B 的量化版本。因此對於開源模型，我已開始改用供應商自己的服務。",{"platform":62,"user":488,"quote":489},"sarjann","還有一個優點是：當某個雲端效能下降時，可以自動切換 (fallback) 。",{"platform":73,"user":491,"quote":492},"@steph_palazzolo（The Information 記者）","OpenRouter 透過單一 API 讓開發者存取 300 個以上的模型，正以 13 億美元估值募集 1.2 億美元，由 CapitalG 領投。這將使其估值較上一輪翻逾一倍，年度經常性收入也已超過 5,000 萬美元。",{"platform":62,"user":494,"quote":495},"bbg2401","我使用 OpenRouter 的情境僅限於隨興的程式碼代理實驗，以及在聊天介面快速探索新模型。這篇評論只是在表達對帳號遭無預警制裁、缺乏透明度及幾乎不存在的支援團隊的長期積怨。","LLM 路由層商業化提速，但模型量化透明度與長期護城河問題仍待觀察，生產採用前需評估供應商品質控管能力。",{"category":18,"source":11,"title":498,"publishDate":6,"tier1Source":499,"supplementSources":502,"coreInfo":510,"engineerView":511,"businessView":512,"viewALabel":513,"viewBLabel":514,"bench":515,"communityQuotes":516,"verdict":137,"impact":526},"Salesforce 聲稱 AI Agent 將 231 人天遷移壓縮至 13 日曆天",{"name":500,"url":501},"Salesforce 工程官方部落格","https://www.salesforce.com/news/stories/how-engineering-became-agentic/",[503,506],{"name":336,"url":504,"detail":505},"https://the-decoder.com/salesforce-claims-ai-agents-cut-a-231-day-migration-to-13-days-with-fewer-incidents/","第三方報導與分析 (2026-05-30)",{"name":507,"url":508,"detail":509},"Anthropic × Salesforce 擴大合作公告","https://www.anthropic.com/news/salesforce-anthropic-expanded-partnership","合作背景 (2025-10-14)","#### 231 人天 → 13 日曆天\n\nSalesforce 工程負責人 Srinivas Tallapragada 於 2026 年 5 月 30 日發表文章，披露一個遷移案例：將 33 個 API endpoint 遷移至雲原生架構，原估 231 人天，以 Agentic workflow 只花 13 個日曆天完成——快了約 18 倍。\n\n> **名詞解釋**\n> 231「人天」是多人協作的總工作量估算，與日曆天不同；13 天是實際掛鐘時間。此數據來自 Salesforce 官方，尚未經第三方獨立驗證。\n\n#### 全公司量化績效（2026 年 4 月 vs 2025 年 4 月）\n\nSalesforce 已將整個工程組織切換至 Anthropic Claude Code，取消 token 限制，並自建「Claude Code skills」模組封裝團隊 context 與工作流程：\n\n- 每位開發者合併 PR 數：+79%\n- 每位開發者完成工作項目：+50.8%\n- ML-based Effective Output Score：+151.3%\n- 系統事故數：-5%\n\n公司預計 2026 年在 Anthropic token 上花費約 3 億美元。工程師角色從手動編碼轉為「Agentic system 架構師」，負責設計問題結構與可複用模式。","Salesforce 的 Agentic 架構核心是 Claude Code + 自建「skills」模組，將團隊 context 封裝成可複用工件。角色轉型重點：從「寫程式」變成「設計委派策略與可複用 patterns」。\n\n官方坦承的挑戰同樣值得關注：長時間 session 的 context 管理難題、CLAUDE.md 輸出品質不穩定、Agent 自主執行的安全邊界——大規模部署時皆非小事。","Salesforce 與 Anthropic 深度綁定（預計年付 3 億美元 token 費用），是目前企業採用 AI coding 工具最具規模的公開案例。\n\n+79% PRs、+151% 效能指標的量化展示，將加速企業主管對 AI coding 工具的採購壓力。但數據為廠商自報，整合複雜度與安全顧慮仍是中小型企業觀望的主因。","開發者角色轉型","生態影響與採購訊號","#### 工程生產力指標（2026 年 4 月 vs 2025 年 4 月）\n\n- 每位開發者合併 PR 數：+79%\n- 每位開發者完成工作項目數：+50.8%\n- ML-based Effective Output Score：+151.3%\n- 系統事故數：-5%\n- 遷移案例：231 人天 → 13 日曆天（約 18 倍提速）",[517,520,523],{"platform":73,"user":518,"quote":519},"@i_am_dy","《2026 年銷售現況》報告明確指出：AI 與 AI agent 不再是可選配置，而是 2026 年的首要成長策略。主要訊號：AI 在客戶開發、預測和內容創作方面已廣泛應用。",{"platform":62,"user":521,"quote":522},"firefoxd","就我的理解，他們是靠「氛圍式寫碼 (vibe coding) 」搞出了個方案，目前對他們有效。我在客服自動化領域工作過，深知不同平台之間的相容性有多頭痛。這暫時看起來是場勝利，但 72 小時後會怎樣誰也不知道。我完全支持對抗 Zendesk，但我對每個想自建方案的人都說同樣的話：你想清楚整合問題了嗎？",{"platform":73,"user":524,"quote":525},"@Benioff(Salesforce CEO)","Salesforce 現在是所有 AI Agent 互相通話的管道，也是所有資料的入口與出口。當你部署第一個 AI agent 時，感覺很神奇——它能預約會議、發送郵件、評估潛在客戶、摘要通話記錄。魔法。","大型企業 Agentic coding 工作流首度公開量化績效，但數據為廠商自報，整合挑戰與初階工程師職涯衝擊仍是待觀察的關鍵變數。",{"category":18,"source":12,"title":528,"publishDate":6,"tier1Source":529,"supplementSources":532,"coreInfo":533,"engineerView":534,"businessView":535,"viewALabel":536,"viewBLabel":537,"bench":323,"communityQuotes":538,"verdict":554,"impact":555},"從零訓練 LLM 完整教學：開源專案登上 GitHub Trending",{"name":530,"url":531},"FareedKhan-dev/train-llm-from-scratch — GitHub","https://github.com/FareedKhan-dev/train-llm-from-scratch",[],"#### 專案概覽\n\n開源專案 [train-llm-from-scratch](https://github.com/FareedKhan-dev/train-llm-from-scratch) 以完整的「從零到生成文字」工作流程登上 GitHub Trending，截至 2026-05-31 已累積 **2,300 顆星、371 個 Fork**，MIT 授權。\n\n80% 內容以 Jupyter Notebook 撰寫，支援從 **1,300 萬到 20 億以上參數**的模型規模，即使資源有限的開發者也能彈性調整 batch size、context length 等超參數進行實驗。\n\n#### 訓練架構\n\n專案實作《Attention is All You Need》論文的 Transformer 架構，包含多頭注意力、MLP、位置嵌入與 Layer Norm。訓練資料集採用 **The Pile**（825 GB 多元語料），Tokenizer 使用 OpenAI `r50k_base`(tiktoken) ，與 GPT-3 相容。\n\n> **名詞解釋**\n> **The Pile** 是 EleutherAI 發布的 825 GB 開源大規模語料庫，涵蓋網頁、書籍、學術論文等多元來源，是訓練開源 LLM 的常見基準資料集。","工作流程明確：`clone repo → install requirements → 下載資料 → 前處理 → 設定超參數 → 訓練 → 生成文字`，所有步驟在 Notebook 中逐步示範，降低環境設定障礙。\n\n13M 參數小模型即可產生語法連貫的文字，適合本機驗證流程；更大規模模型在長序列一致性上明顯提升。整體架構緊貼原版論文，適合想深入理解 LLM 訓練機制的工程師作為學習起點或修改基礎。","「可執行教學資源」登上 Trending，反映業界對 LLM 自主研發能力的高需求——企業不再滿足於只呼叫 API，而是希望掌握底層訓練流程。\n\nMIT 授權加上 Notebook 格式降低入門門檻，有助於加速工程師從「LLM 使用者」轉型為「LLM 訓練者」，間接降低對外部模型提供商的依賴。對於尋求建立內部 AI 能力的企業，此專案提供了從教學到 PoC 的踏板。","開發者上手難度","生態影響",[539,542,545,548,551],{"platform":73,"user":540,"quote":541},"Andriy Burkov（AI/ML 研究者與作者）","為什麼 LLM 無論規模多大都無法理解世界？你走在街上看著路人的臉，我問你快樂與不快樂面孔的比例，你能大概回答。LLM 也和你一起觀察這些路人，然後你訓練……",{"platform":62,"user":543,"quote":544},"gspr（HN 用戶）","真的嗎？能分享你的技術嗎？受 cursed_browser 啟發，我有個小型藝術專案，讓虛擬機的 CPU 完全由 LLM 驅動。但即使指令集架構在訓練資料中早有記錄，我幾乎無法讓它連續正確解碼哪怕幾條指令——可能連續對 10 條，然後就突然失去能力。",{"platform":73,"user":546,"quote":547},"UnslothAI（AI 訓練最佳化工具）","我們與 NVIDIA 合作，教你如何讓 LLM 訓練速度提升約 25%！了解 3 項最佳化如何幫助家用 GPU 更快訓練模型：1. Packed-sequence 元資料快取；2. 雙緩衝檢查點重載；3. 更快的 MoE 路由。",{"platform":62,"user":549,"quote":550},"SV_BubbleTime（HN 用戶）","我反對在任何重要事項上採用「氛圍式」方法，但這種推論的根本缺陷在於未知的未知確實存在。我無法針對知識範圍外的事情引用「從零開始」，但 LLM 訓練或輔助搜尋是我會選擇的方向。",{"platform":62,"user":552,"quote":553},"astrange（HN 用戶）","爬取網路資料不構成版權侵犯。將其用於 LLM 訓練比 Google 和 Internet Archive 更具轉化性，而那些都是合法的。","追","提供可執行的 LLM 訓練完整教學，降低工程師掌握底層訓練流程的門檻，有助於企業建立自主 AI 能力。",{"category":18,"source":14,"title":557,"publishDate":6,"tier1Source":558,"supplementSources":560,"coreInfo":567,"engineerView":568,"businessView":569,"viewALabel":570,"viewBLabel":571,"bench":323,"communityQuotes":572,"verdict":397,"impact":583},"Microsoft 與 Nvidia 聯手打造 AI PC，用真正的 Agent 取代 Copilot",{"name":336,"url":559},"https://the-decoder.com/microsoft-and-nvidia-reportedly-team-up-on-ai-pcs-that-run-actual-agents-instead-of-copilot/",[561,564],{"name":562,"url":563},"Tom's Hardware","https://www.tomshardware.com/laptops/nvidia-and-microsoft-tease-a-new-era-of-pc-ahead-of-computex-2026-coordinated-social-media-posts-could-indicate-that-rumored-n1x-laptops-will-be-windows-on-arm-systems",{"name":565,"url":566},"Axios(via Investing.com)","https://www.investing.com/news/stock-market-news/nvidia-to-unveil-first-windows-pcs-powered-by-its-chips-next-week--axios-4717764","#### 從 Copilot 噱頭到真正的 Agent 工作流程\n\nMicrosoft 與 Nvidia 聯手宣布「PC 新時代」，核心轉折是放棄依賴雲端的 Copilot 模式，改以 Windows 本地端執行的 AI Agent 框架取代。Copilot+ PC 計畫被媒體直接形容為「基本上失敗了」，此次轉向以 OpenClaw 框架為核心，讓 Agent 可在 PC 本機直接執行工作流程，減少對雲端運算的依賴。\n\n> **名詞解釋**\n> OpenClaw 是微軟自 2026 年初採用的本地 Agent 執行框架，由工程師 Omar Shahine 主導，預計整合進 Microsoft 365。\n\n#### 硬體側：Nvidia 首款 Windows 主處理器晶片\n\nNvidia 傳聞代號 N1 與 N1X 的 Arm 架構晶片，將 CPU、GPU 與 AI 加速整合成單一封裝，以「主處理器」而非獨立 GPU 的角色進入 PC 市場。Dell 與 Microsoft Surface 系列將率先搭載，預計於 Computex 台北展及 Microsoft Build 大會正式亮相。","OpenClaw 框架讓 Windows 本地端 Agent 整合成為可能，開發者可期待新的 Agent API 與 Microsoft 365 整合介面。然而安全性問題尚未解決——本地執行雖減少雲端依賴，但 Agent 存取本機資源與應用程式的權限邊界仍不清晰。建議等待 Build 大會釋出正式 API 文件與沙箱規範後，再評估整合時機。","Copilot+ PC 的失敗暴露了「AI 功能噱頭化」的市場風險，此次 Microsoft 與 Nvidia 深度合作，目標是重建 AI PC 的市場信任度。若本地 Agent 確實提升 Microsoft 365 用戶工作效率，才有機會帶動企業換機潮。整體仍屬早期，投資決策需待 Computex 後看實際規格與定價策略再定奪。","本地 Agent 框架整合評估","AI PC 生態轉型影響",[573,576,580],{"platform":73,"user":574,"quote":575},"@VDP_94","2026 年 AI Agent 大爆發 📈 ● 微軟將 AI Agent 整合進 Windows ● Meta 在 AI Agent 上投資逾 20 億美元 ● Nvidia AI Agent 叢集 ● 與 Visa 合作推出 AI Agent 支付系統。2026 年的核心敘事就是：AI Agent",{"platform":577,"user":578,"quote":579},"HN","IgorPartola（HN 用戶）","企業領導者開始質疑不斷攀升的 AI 支出是否真的帶來實質回報。這是 AI 熊市的第一幕——AI 因革新工作方式的潛力而蓬勃，但隨著預期與現實出現落差，資本正在重新評估投報率。",{"platform":73,"user":581,"quote":582},"@KobeissiLetter（金融市場分析）","AI Agent 的人氣正在爆炸性成長。從 2025 年到 2030 年，這個市場的年複合成長率預計達 43.3%，年收入將攀升至約 483 億美元。Nvidia 執行長黃仁勳正大力押注這個趨勢。","Microsoft 正式轉向本地 Agent 執行架構，若 Build 大會釋出成熟 API，將影響企業 AI 工作流程的採購與整合決策。","#### 社群熱議排行\n\n本日討論熱度最高的四個主題：MCP 協議存廢之爭、Qwen 3.6 消費級推論突破、GitHub Copilot 帳單暴增，以及 SQLite 工作流架構選型。\n\nGitHub Copilot 計費爭議由 simonw(HN) 引爆——他找到一個 $39 訂閱換算用量計費為 $5,851.77 的實際案例，在社群迅速擴散。\n\nQwen 3.6 本地推論話題由 masnick.com（Bluesky，60 likes）帶起熱度，稱週末實測已將大部分 agentic 設定切換至本地模型。\n\nMCP 已累積每月 9,700 萬次 SDK 下載，torcdotdev.bsky.social（Bluesky，3 upvotes）指出其成長規模，但 HN 多名開發者同步提出根本性質疑。\n\n#### 技術爭議與分歧\n\nMCP 社群內部對立明顯：ok_dad(HN) 反批評者——「你批評 MCP，卻提不出本質上不同的替代方案，OAuth 加 JSON 就是 MCP」。\n\ngeysersam(HN) 主張 curl 或 python 直存 API 已然足夠；@milvusio(X) 則認為協議本身沒問題，真正痛點是把 50 個工具定義塞進 context。\n\n本地推論陣營也有分歧：u/jtjstock(Reddit r/LocalLLaMA) 直批「NVFP4 在 llama 上目前很爛」；u/Xp_12 反駁稱問題在量化配方與 sm_120 加速支援不完整，非協議本身。\n\n#### 實戰經驗\n\nvmbm(HN) 警告最清楚：$10–$200 月費下跑 agentic workflow 的用戶，換用量計費後成本可能暴增 10–100 倍——「用啤酒錢跑幾百個 agent 很爽，但換成遊艇錢就不好玩了」。\n\nmasnick.com（Bluesky，60 likes）實測 Qwen 3.6-35B-A3B 與 Gemma 4 31B 本地部署後得出結論：「本地模型現在真的很厲害。」\n\nSalesforce 內部案例（廠商自報）稱 Agentic coding 工作流將 231 人天遷移壓縮至 13 曆天；firefoxd(HN) 提醒：「整合相容性問題在 72 小時後才是真正考驗。」\n\n#### 未解問題與社群預期\n\naussieguy1234(HN) 點出 OpenRouter 量化透明度缺口：「你以為自己在用完整模型，背後卻是量化版本。」B 輪融資後如何建立供應商品質管控，社群尚無答案。\n\nMCP 路線圖對「動態工具載入」與 context 最佳化的回應時程未明，「限制工具數量」只是繞路，社群期待官方正面回應。\n\nMeta AI 吊墜的持續錄音功能引發隱私疑慮，Bluesky 用戶 (46 upvotes) 預測：「執行長將強制員工配戴，儘管我並不樂見。」監管走向懸而未決。",[586,588,589,590,591,593,594,595,596,598,599,600],{"type":84,"text":587},"用 llama.cpp 的 --tensor-split 1,1 在雙 4060 Ti 上跑 Qwen3.6-35B-A3B Q4_K_XL，基準測試生成速度是否達到 100 tok/s 以上，並用 nvidia-smi 確認雙卡 VRAM 均衡分配。",{"type":84,"text":140},{"type":84,"text":85},{"type":84,"text":214},{"type":87,"text":592},"基於 Qwen 3.6 的 262K context 視窗，嘗試建構本地 RAG 或長文摘要 pipeline，測試真實多輪任務的吞吐量與品質，並與雲端 API 進行成本效益比較。",{"type":87,"text":142},{"type":87,"text":88},{"type":87,"text":216},{"type":90,"text":597},"追蹤 llama.cpp 對 Blackwell sm_120 的 NVFP4 成熟度進展與 vllm b12x 支援——當配方品質穩定後，下一代消費卡（RTX 50 系列）的推論速度可望有明顯躍升。",{"type":90,"text":144},{"type":90,"text":91},{"type":90,"text":218},"2026-05-31 這一天，AI 工具的「真實成本」從抽象概念變成了具體帳單。\n\nGitHub Copilot $5,851 案例、OpenRouter 量化透明度爭議、MCP context 爆滿——三個看似獨立的事件，指向同一個社群共識：帳面功能與實際成本之間的落差，正在被迫攤牌。\n\nQwen 3.6 在消費級 GPU 的突破、SQLite 工作流架構的逐步成熟，則指向另一個方向：本地化、低依賴、可預測成本的 AI 架構，正在獲得越來越多實戰背書。\n\n值得持續關注的是 Microsoft Build 大會的本地 Agent API 進度——若成熟度達標，企業 AI 工作流的採購邏輯將迎來一次結構性重組。",{"prev":603,"next":604},"2026-05-30","2026-06-01",{"data":606,"body":607,"excerpt":-1,"toc":617},{"title":323,"description":30},{"type":608,"children":609},"root",[610],{"type":611,"tag":612,"props":613,"children":614},"element","p",{},[615],{"type":616,"value":30},"text",{"title":323,"searchDepth":618,"depth":618,"links":619},2,[],{"data":621,"body":622,"excerpt":-1,"toc":628},{"title":323,"description":34},{"type":608,"children":623},[624],{"type":611,"tag":612,"props":625,"children":626},{},[627],{"type":616,"value":34},{"title":323,"searchDepth":618,"depth":618,"links":629},[],{"data":631,"body":632,"excerpt":-1,"toc":638},{"title":323,"description":37},{"type":608,"children":633},[634],{"type":611,"tag":612,"props":635,"children":636},{},[637],{"type":616,"value":37},{"title":323,"searchDepth":618,"depth":618,"links":639},[],{"data":641,"body":642,"excerpt":-1,"toc":648},{"title":323,"description":40},{"type":608,"children":643},[644],{"type":611,"tag":612,"props":645,"children":646},{},[647],{"type":616,"value":40},{"title":323,"searchDepth":618,"depth":618,"links":649},[],{"data":651,"body":652,"excerpt":-1,"toc":768},{"title":323,"description":323},{"type":608,"children":653},[654,661,666,690,695,701,706,711,727,733,738,743,748,753,758,763],{"type":611,"tag":655,"props":656,"children":658},"h4",{"id":657},"什麼是持久工作流與-sqlite-方案",[659],{"type":616,"value":660},"什麼是持久工作流與 SQLite 方案",{"type":611,"tag":612,"props":662,"children":663},{},[664],{"type":616,"value":665},"持久執行 (Durable Execution) 是一種架構模式，工作流進度被持續記錄在執行日誌中，即使程序崩潰也能從斷點重播。關鍵洞見在於「持久的是工作流狀態，計算本身可以是廉價且可拋棄的」——Obelisk 專案以此為基礎，提出了以 SQLite 取代外部資料庫的完整方案。",{"type":611,"tag":667,"props":668,"children":669},"blockquote",{},[670],{"type":611,"tag":612,"props":671,"children":672},{},[673,679,683,688],{"type":611,"tag":674,"props":675,"children":676},"strong",{},[677],{"type":616,"value":678},"名詞解釋",{"type":611,"tag":680,"props":681,"children":682},"br",{},[],{"type":611,"tag":674,"props":684,"children":685},{},[686],{"type":616,"value":687},"持久執行 (Durable Execution)",{"type":616,"value":689},"：一種工作流執行模型，將每個活動的執行歷史記錄在持久儲存中；系統重啟後可從上次中斷處重播，活動可自動重試，無需開發者手動實作斷點續傳邏輯。",{"type":611,"tag":612,"props":691,"children":692},{},[693],{"type":616,"value":694},"SQLite 方案延伸自 DBOS 的「Postgres is all you need」前提，更進一步主張：對於 AI 代理、突發性工作負載與實驗性系統，本地嵌入式資料庫足以承擔持久化任務，連 Postgres 都可以省去。核心設計目標是消除額外的網路跳轉、獨立控制平面與運維介面。",{"type":611,"tag":655,"props":696,"children":698},{"id":697},"架構設計單機-sqlite-vs-外部資料庫",[699],{"type":616,"value":700},"架構設計：單機 SQLite vs 外部資料庫",{"type":611,"tag":612,"props":702,"children":703},{},[704],{"type":616,"value":705},"Obelisk 的架構由三個核心元件組成：與 worker 共置的本地 SQLite 資料庫、Litestream 非同步備份至 S3 相容物件儲存，以及可拉取資料庫進行檢查的 Observer 元件。這個設計徹底消除了對獨立資料庫服務的依賴。",{"type":611,"tag":612,"props":707,"children":708},{},[709],{"type":616,"value":710},"相較外部資料庫方案，SQLite 在多租戶場景帶來更好的故障隔離：每個 worker 擁有獨立資料庫，一個 worker 的問題不會波及其他 worker。但 Litestream 的非同步複寫是有意接受的取捨——硬體故障時，尚未複寫的最新狀態存在遺失風險，這是架構設計必須正視的邊界條件。",{"type":611,"tag":667,"props":712,"children":713},{},[714],{"type":611,"tag":612,"props":715,"children":716},{},[717,722,725],{"type":611,"tag":674,"props":718,"children":719},{},[720],{"type":616,"value":721},"白話比喻",{"type":611,"tag":680,"props":723,"children":724},{},[],{"type":616,"value":726},"\n傳統工作流系統是一棟共用廚房的公寓大樓——所有住戶共用一個廚房，廚房壞了所有人都不能開伙。SQLite 方案則像每戶都有自己的迷你廚房，附帶一個每隔幾分鐘備份食材到倉庫的服務——某一戶廚房壞了，其他人照常做飯；只是最後幾分鐘的食材若沒來得及備份，就可能遺失。",{"type":611,"tag":655,"props":728,"children":730},{"id":729},"社群論戰停機容忍度與複雜度取捨",[731],{"type":616,"value":732},"社群論戰：停機容忍度與複雜度取捨",{"type":611,"tag":612,"props":734,"children":735},{},[736],{"type":616,"value":737},"HN 討論最尖銳的分歧在於停機容忍度。cortesoft 從 CDN 從業背景提出質疑：「你沒辦法在 SQLite 下做那些事又不停機——在我職涯大部分時間，任何停機都是完全不可接受的。」franga2000 直接反駁：「就……不在意？在非工作時間做維護，快速修復問題，好好向客戶解釋。」",{"type":611,"tag":612,"props":739,"children":740},{},[741],{"type":616,"value":742},"這個對話揭示了架構決策的核心篩選器：停機容忍度不是技術問題，而是業務價值觀問題。CDN、金融交易、醫療系統這類場景，停機容忍度接近零；而大量的 AI 代理、內部工具、實驗性系統則可接受計畫維護視窗。",{"type":611,"tag":612,"props":744,"children":745},{},[746],{"type":616,"value":747},"複雜度辯論同樣分裂。fcarraldo 批評 Temporal/Cassandra：「Temporal 規模化後複雜度爆炸，Cassandra 也不好管——所有在上面建立真正生產系統的人都討厭它。」inglor 則從直接經驗反駁：「我們在 Temporal 上建立了一家十億美元的公司，再開心不過了。」",{"type":611,"tag":612,"props":749,"children":750},{},[751],{"type":616,"value":752},"這說明架構選擇高度依賴團隊背景，沒有普適答案。utopiah 的元觀察捕捉了整個討論的精髓：工程師從複雜工具的挫折中成熟，最終重新發現更簡單的工具。stingraycharles 更直白：「無聊才是新的性感。」",{"type":611,"tag":655,"props":754,"children":756},{"id":755},"實戰建議與替代方案比較",[757],{"type":616,"value":755},{"type":611,"tag":612,"props":759,"children":760},{},[761],{"type":616,"value":762},"選擇 SQLite + Litestream 的適合情境是：工作負載具突發性或實驗性質、需要每個 worker 獨立故障隔離、業務可接受計畫維護視窗，且建立完整網路資料庫基礎設施成本過高。AI 代理工作流是目前社群最看好的場景，因代理任務本質上短暫且可重試。",{"type":611,"tag":612,"props":764,"children":765},{},[766],{"type":616,"value":767},"PostgreSQL 仍是高可用需求的正確選擇：當多個 worker 需共享狀態、團隊已有 Postgres 運維經驗，或業務要求零停機時。LangGraph v0.2 已明確區分兩條路徑——本地工作流用 SQLite checkpointer，生產環境用最佳化的 Postgres checkpointer，這種雙軌策略值得借鑒。",{"title":323,"searchDepth":618,"depth":618,"links":769},[],{"data":771,"body":773,"excerpt":-1,"toc":779},{"title":323,"description":772},"持久工作流的核心是「用日誌換可靠性」：每個活動執行後立即寫入執行歷史，系統崩潰後可從日誌重播回正確狀態。SQLite 版本的創新在於，這個日誌不再需要放在遠端——放在 worker 旁邊的本地檔案就夠了。",{"type":608,"children":774},[775],{"type":611,"tag":612,"props":776,"children":777},{},[778],{"type":616,"value":772},{"title":323,"searchDepth":618,"depth":618,"links":780},[],{"data":782,"body":784,"excerpt":-1,"toc":790},{"title":323,"description":783},"每個 worker 維護一個本地 SQLite 資料庫作為工作流歷史日誌。當工作流需要重播時，系統從這個本地日誌讀取已完成的活動記錄，只重新執行尚未完成的步驟，避免重複處理。本地讀寫消除了網路延遲，對執行頻率高但每次執行輕量的 AI 代理任務而言效能優勢明顯。",{"type":608,"children":785},[786],{"type":611,"tag":612,"props":787,"children":788},{},[789],{"type":616,"value":783},{"title":323,"searchDepth":618,"depth":618,"links":791},[],{"data":793,"body":795,"excerpt":-1,"toc":821},{"title":323,"description":794},"Litestream 持續將 SQLite 的 WAL(Write-Ahead Log) 變更串流至 S3 相容的物件儲存。這個設計讓持久化不阻塞工作流主路徑，代價是非同步特性帶來的「最終一致」複寫語意——硬體突然崩潰時，可能遺失尚未串流出去的最新幾秒狀態。",{"type":608,"children":796},[797,801],{"type":611,"tag":612,"props":798,"children":799},{},[800],{"type":616,"value":794},{"type":611,"tag":667,"props":802,"children":803},{},[804],{"type":611,"tag":612,"props":805,"children":806},{},[807,811,814,819],{"type":611,"tag":674,"props":808,"children":809},{},[810],{"type":616,"value":678},{"type":611,"tag":680,"props":812,"children":813},{},[],{"type":611,"tag":674,"props":815,"children":816},{},[817],{"type":616,"value":818},"WAL(Write-Ahead Log)",{"type":616,"value":820},"：SQLite 的一種日誌模式，允許讀取與寫入並行進行，讀取不阻塞寫入。相較預設的 DELETE journal 模式，在高並行讀寫場景下效能顯著提升。",{"title":323,"searchDepth":618,"depth":618,"links":822},[],{"data":824,"body":826,"excerpt":-1,"toc":847},{"title":323,"description":825},"Observer 元件可拉取任意 worker 的 SQLite 資料庫副本，讓工程師在本機重播工作流歷史進行除錯。這種「把工作流歷史拉下來跑」的能力，是傳統外部資料庫架構難以輕易提供的開發體驗優勢——Replay 能力讓故障重現從「線上追查」變成「本機回放」。",{"type":608,"children":827},[828,832],{"type":611,"tag":612,"props":829,"children":830},{},[831],{"type":616,"value":825},{"type":611,"tag":667,"props":833,"children":834},{},[835],{"type":611,"tag":612,"props":836,"children":837},{},[838,842,845],{"type":611,"tag":674,"props":839,"children":840},{},[841],{"type":616,"value":721},{"type":611,"tag":680,"props":843,"children":844},{},[],{"type":616,"value":846},"\n把持久工作流想像成一本記事本。傳統架構把記事本放在公司共用文件室（外部資料庫）——所有人都要跑去那裡查閱；SQLite 架構則讓每個工程師隨身攜帶記事本，同時每隔幾分鐘自動拍照上傳備份。查閱快、備份自動，但若記事本不小心落水，最後幾頁可能沒來得及備份。",{"title":323,"searchDepth":618,"depth":618,"links":848},[],{"data":850,"body":851,"excerpt":-1,"toc":941},{"title":323,"description":323},{"type":608,"children":852},[853,858,863,869,894,899,918,923],{"type":611,"tag":655,"props":854,"children":856},{"id":855},"環境需求",[857],{"type":616,"value":855},{"type":611,"tag":612,"props":859,"children":860},{},[861],{"type":616,"value":862},"SQLite 3.35+（支援 WAL 模式與 RETURNING 語法），Litestream 0.3+，以及 S3 相容物件儲存（AWS S3、MinIO、Cloudflare R2 均可）。Obelisk 本體以 Rust 實作，worker 執行環境無需額外語言執行期依賴。若使用 LangGraph，直接升級至 v0.2 即可取得原生 SQLite checkpointer 支援。",{"type":611,"tag":655,"props":864,"children":866},{"id":865},"遷移整合步驟",[867],{"type":616,"value":868},"遷移／整合步驟",{"type":611,"tag":870,"props":871,"children":872},"ol",{},[873,879,884,889],{"type":611,"tag":874,"props":875,"children":876},"li",{},[877],{"type":616,"value":878},"將現有工作流狀態儲存層替換為本地 SQLite（修改 checkpointer 設定，LangGraph 用戶只需更換 checkpointer 實例）",{"type":611,"tag":874,"props":880,"children":881},{},[882],{"type":616,"value":883},"部署 Litestream 作為 sidecar，設定 S3 備份目標與複寫間隔（建議 1 秒以內）",{"type":611,"tag":874,"props":885,"children":886},{},[887],{"type":616,"value":888},"整合 Observer 元件，設定可存取 worker SQLite 的讀取路徑",{"type":611,"tag":874,"props":890,"children":891},{},[892],{"type":616,"value":893},"在 CI 環境中驗證本地重播功能：從 S3 備份還原後重跑測試工作流，確認重播一致性",{"type":611,"tag":655,"props":895,"children":897},{"id":896},"常見陷阱",[898],{"type":616,"value":896},{"type":611,"tag":900,"props":901,"children":902},"ul",{},[903,908,913],{"type":611,"tag":874,"props":904,"children":905},{},[906],{"type":616,"value":907},"誤以為 Litestream 提供同步複寫保證——實際上是非同步，SLA 中必須明確聲明資料遺失容忍度 (RPO > 0)",{"type":611,"tag":874,"props":909,"children":910},{},[911],{"type":616,"value":912},"在高並行寫入場景強行使用 SQLite——單寫入者特性在此場景會成為瓶頸，應拆分為多個獨立 SQLite 實例",{"type":611,"tag":874,"props":914,"children":915},{},[916],{"type":616,"value":917},"忘記啟用 WAL 模式——未啟用 WAL 的 SQLite 在高讀寫負載下效能顯著下降，且不支援並行讀取",{"type":611,"tag":655,"props":919,"children":921},{"id":920},"上線檢核清單",[922],{"type":616,"value":920},{"type":611,"tag":900,"props":924,"children":925},{},[926,931,936],{"type":611,"tag":874,"props":927,"children":928},{},[929],{"type":616,"value":930},"觀測：Litestream 複寫延遲監控、worker SQLite 檔案大小趨勢、工作流重播成功率",{"type":611,"tag":874,"props":932,"children":933},{},[934],{"type":616,"value":935},"成本：S3 PUT 請求費用（WAL 串流頻率）、Observer 拉取頻率與網路傳輸費用",{"type":611,"tag":874,"props":937,"children":938},{},[939],{"type":616,"value":940},"風險：定期演練從 S3 備份完整還原並重播工作流（不要只備份不演練，否則發現不了備份損壞）",{"title":323,"searchDepth":618,"depth":618,"links":942},[],{"data":944,"body":945,"excerpt":-1,"toc":1065},{"title":323,"description":323},{"type":608,"children":946},[947,952,975,980,1003,1008,1013,1018,1036,1041,1054,1060],{"type":611,"tag":655,"props":948,"children":950},{"id":949},"競爭版圖",[951],{"type":616,"value":949},{"type":611,"tag":900,"props":953,"children":954},{},[955,965],{"type":611,"tag":874,"props":956,"children":957},{},[958,963],{"type":611,"tag":674,"props":959,"children":960},{},[961],{"type":616,"value":962},"直接競品",{"type":616,"value":964},"：Temporal（工作流編排領域主流選擇，有 Temporal Cloud 管理服務）、Conductor（Netflix 開源，適合大規模微服務編排）、Prefect 與 Airflow（資料管道導向）",{"type":611,"tag":874,"props":966,"children":967},{},[968,973],{"type":611,"tag":674,"props":969,"children":970},{},[971],{"type":616,"value":972},"間接競品",{"type":616,"value":974},"：自建 Redis + Bull 佇列、AWS Step Functions（雲原生，lock-in 風險）、Azure Durable Functions（.NET 生態）",{"type":611,"tag":655,"props":976,"children":978},{"id":977},"護城河類型",[979],{"type":616,"value":977},{"type":611,"tag":900,"props":981,"children":982},{},[983,993],{"type":611,"tag":874,"props":984,"children":985},{},[986,991],{"type":611,"tag":674,"props":987,"children":988},{},[989],{"type":616,"value":990},"工程護城河",{"type":616,"value":992},"：零外部依賴的嵌入式設計讓邊緣部署、本地開發環境、單機 AI 代理場景具有天然優勢，競品難以在不犧牲架構簡潔性的前提下複製",{"type":611,"tag":874,"props":994,"children":995},{},[996,1001],{"type":611,"tag":674,"props":997,"children":998},{},[999],{"type":616,"value":1000},"生態護城河",{"type":616,"value":1002},"：LangGraph v0.2 已原生支援 SQLite checkpointer，Obelisk 推動社群標準化，形成正向循環",{"type":611,"tag":655,"props":1004,"children":1006},{"id":1005},"定價策略",[1007],{"type":616,"value":1005},{"type":611,"tag":612,"props":1009,"children":1010},{},[1011],{"type":616,"value":1012},"SQLite + Litestream 方案本身為開源免費，唯一持續成本是 S3 物件儲存費用（通常每 GB 月費不到 $0.03）。對比 Temporal Cloud 的按任務計費模式，突發性 AI 代理工作流的成本節省相當顯著——峰值時段費用不會因工作流數量線性成長。",{"type":611,"tag":655,"props":1014,"children":1016},{"id":1015},"企業導入阻力",[1017],{"type":616,"value":1015},{"type":611,"tag":900,"props":1019,"children":1020},{},[1021,1026,1031],{"type":611,"tag":874,"props":1022,"children":1023},{},[1024],{"type":616,"value":1025},"非同步複寫的資料遺失風險難以向企業安全與合規團隊解釋，需明確界定 RPO 邊界",{"type":611,"tag":874,"props":1027,"children":1028},{},[1029],{"type":616,"value":1030},"SQLite 單寫入者限制讓架構師對多節點水平擴展方案持懷疑態度",{"type":611,"tag":874,"props":1032,"children":1033},{},[1034],{"type":616,"value":1035},"缺乏如 Temporal 般完整的可觀測性生態（可視化 Dashboard、分散式追蹤工具整合）",{"type":611,"tag":655,"props":1037,"children":1039},{"id":1038},"第二序影響",[1040],{"type":616,"value":1038},{"type":611,"tag":900,"props":1042,"children":1043},{},[1044,1049],{"type":611,"tag":874,"props":1045,"children":1046},{},[1047],{"type":616,"value":1048},"AI 代理工作流普及可能推動「per-agent SQLite」成為開源框架預設設計模式，進而影響雲端工作流服務的定價競爭",{"type":611,"tag":874,"props":1050,"children":1051},{},[1052],{"type":616,"value":1053},"邊緣運算場景中 SQLite 持久工作流可能取代輕量級訊息佇列，重塑邊緣 AI 基礎設施選型",{"type":611,"tag":655,"props":1055,"children":1057},{"id":1056},"判決先觀望技術有效但生態尚不成熟",[1058],{"type":616,"value":1059},"判決先觀望（技術有效但生態尚不成熟）",{"type":611,"tag":612,"props":1061,"children":1062},{},[1063],{"type":616,"value":1064},"SQLite 持久工作流在正確場景下是清晰有效的架構選擇，技術論點站得住腳。但完整工具鏈（可觀測性、除錯工具、多框架標準化支援）仍在建構中，生產案例積累不足。對已有 Temporal 或 Postgres 基礎設施的團隊，遷移收益有限；新 AI 代理專案則值得認真評估。",{"title":323,"searchDepth":618,"depth":618,"links":1066},[],{"data":1068,"body":1069,"excerpt":-1,"toc":1094},{"title":323,"description":323},{"type":608,"children":1070},[1071,1077,1082],{"type":611,"tag":655,"props":1072,"children":1074},{"id":1073},"sqlite-wal-模式效能上限",[1075],{"type":616,"value":1076},"SQLite WAL 模式效能上限",{"type":611,"tag":612,"props":1078,"children":1079},{},[1080],{"type":616,"value":1081},"社群討論中引用的基準測試顯示，在啟用 WAL 模式並適當最佳化的條件下，SQLite 可達每秒 10 萬次事務 (100,000 TPS) ，測試資料集超過 10 億行。這個數字對工作流狀態持久化場景已綽綽有餘——工作流日誌的寫入頻率遠低於 OLTP 場景。",{"type":611,"tag":612,"props":1083,"children":1084},{},[1085,1087,1092],{"type":616,"value":1086},"真正的瓶頸在於",{"type":611,"tag":674,"props":1088,"children":1089},{},[1090],{"type":616,"value":1091},"單寫入者限制",{"type":616,"value":1093},"：SQLite 不支援多個 writer 並行寫入同一個資料庫檔案。這也是 Obelisk 採用「每個 worker 一個獨立 SQLite」設計的原因——用水平分片換取對單寫入者限制的規避，而非強行讓多個 worker 競爭同一個 SQLite 實例。",{"title":323,"searchDepth":618,"depth":618,"links":1095},[],{"data":1097,"body":1098,"excerpt":-1,"toc":1119},{"title":323,"description":323},{"type":608,"children":1099},[1100],{"type":611,"tag":900,"props":1101,"children":1102},{},[1103,1107,1111,1115],{"type":611,"tag":874,"props":1104,"children":1105},{},[1106],{"type":616,"value":46},{"type":611,"tag":874,"props":1108,"children":1109},{},[1110],{"type":616,"value":47},{"type":611,"tag":874,"props":1112,"children":1113},{},[1114],{"type":616,"value":48},{"type":611,"tag":874,"props":1116,"children":1117},{},[1118],{"type":616,"value":49},{"title":323,"searchDepth":618,"depth":618,"links":1120},[],{"data":1122,"body":1123,"excerpt":-1,"toc":1140},{"title":323,"description":323},{"type":608,"children":1124},[1125],{"type":611,"tag":900,"props":1126,"children":1127},{},[1128,1132,1136],{"type":611,"tag":874,"props":1129,"children":1130},{},[1131],{"type":616,"value":51},{"type":611,"tag":874,"props":1133,"children":1134},{},[1135],{"type":616,"value":52},{"type":611,"tag":874,"props":1137,"children":1138},{},[1139],{"type":616,"value":53},{"title":323,"searchDepth":618,"depth":618,"links":1141},[],{"data":1143,"body":1144,"excerpt":-1,"toc":1150},{"title":323,"description":57},{"type":608,"children":1145},[1146],{"type":611,"tag":612,"props":1147,"children":1148},{},[1149],{"type":616,"value":57},{"title":323,"searchDepth":618,"depth":618,"links":1151},[],{"data":1153,"body":1154,"excerpt":-1,"toc":1160},{"title":323,"description":58},{"type":608,"children":1155},[1156],{"type":611,"tag":612,"props":1157,"children":1158},{},[1159],{"type":616,"value":58},{"title":323,"searchDepth":618,"depth":618,"links":1161},[],{"data":1163,"body":1164,"excerpt":-1,"toc":1170},{"title":323,"description":59},{"type":608,"children":1165},[1166],{"type":611,"tag":612,"props":1167,"children":1168},{},[1169],{"type":616,"value":59},{"title":323,"searchDepth":618,"depth":618,"links":1171},[],{"data":1173,"body":1174,"excerpt":-1,"toc":1180},{"title":323,"description":105},{"type":608,"children":1175},[1176],{"type":611,"tag":612,"props":1177,"children":1178},{},[1179],{"type":616,"value":105},{"title":323,"searchDepth":618,"depth":618,"links":1181},[],{"data":1183,"body":1184,"excerpt":-1,"toc":1190},{"title":323,"description":109},{"type":608,"children":1185},[1186],{"type":611,"tag":612,"props":1187,"children":1188},{},[1189],{"type":616,"value":109},{"title":323,"searchDepth":618,"depth":618,"links":1191},[],{"data":1193,"body":1194,"excerpt":-1,"toc":1200},{"title":323,"description":112},{"type":608,"children":1195},[1196],{"type":611,"tag":612,"props":1197,"children":1198},{},[1199],{"type":616,"value":112},{"title":323,"searchDepth":618,"depth":618,"links":1201},[],{"data":1203,"body":1204,"excerpt":-1,"toc":1210},{"title":323,"description":115},{"type":608,"children":1205},[1206],{"type":611,"tag":612,"props":1207,"children":1208},{},[1209],{"type":616,"value":115},{"title":323,"searchDepth":618,"depth":618,"links":1211},[],{"data":1213,"body":1214,"excerpt":-1,"toc":1393},{"title":323,"description":323},{"type":608,"children":1215},[1216,1222,1227,1232,1237,1242,1248,1253,1258,1276,1281,1286,1301,1307,1312,1317,1322,1340,1345,1350,1355,1360,1365,1378],{"type":611,"tag":655,"props":1217,"children":1219},{"id":1218},"mcp-的定位與現狀",[1220],{"type":616,"value":1221},"MCP 的定位與現狀",{"type":611,"tag":612,"props":1223,"children":1224},{},[1225],{"type":616,"value":1226},"MCP(Model Context Protocol) 由 Anthropic 推出，旨在讓 AI agent 透過標準化協議連接外部服務與工具。",{"type":611,"tag":612,"props":1228,"children":1229},{},[1230],{"type":616,"value":1231},"Quandri 後端工程師 Chloe Kim 在《MCP is Dead》一文中，記錄了團隊將四個 MCP server 全數替換為 CLI + Skills 方案的實戰歷程，引發 Hacker News 社群大規模論戰。",{"type":611,"tag":612,"props":1233,"children":1234},{},[1235],{"type":616,"value":1236},"根據 Quandri 的測試，四個 MCP server 的工具定義共佔用了 200K context window 的 10.5%，單是 Linear server 就消耗約 12,800 tokens（含 42 個工具定義），但實際被呼叫到的只有兩個函式。",{"type":611,"tag":612,"props":1238,"children":1239},{},[1240],{"type":616,"value":1241},"替換後釋出約 21K tokens，回應穩定性與 terminal 除錯流程也顯著改善。這份數據讓許多曾遇到類似問題的開發者感同身受，批評聲浪一夕浮出水面。",{"type":611,"tag":655,"props":1243,"children":1245},{"id":1244},"反對方rest-json-oauth-就夠了",[1246],{"type":616,"value":1247},"反對方：REST + JSON + OAuth 就夠了",{"type":611,"tag":612,"props":1249,"children":1250},{},[1251],{"type":616,"value":1252},"反對 MCP 的核心論點在於：協議本身所解決的問題，既有技術棧早已有成熟解法。",{"type":611,"tag":612,"props":1254,"children":1255},{},[1256],{"type":616,"value":1257},"Quandri 歸納出 MCP 的三大痛點：",{"type":611,"tag":900,"props":1259,"children":1260},{},[1261,1266,1271],{"type":611,"tag":874,"props":1262,"children":1263},{},[1264],{"type":616,"value":1265},"context window 爆滿（tool schema 隨 server 數量線性膨脹）",{"type":611,"tag":874,"props":1267,"children":1268},{},[1269],{"type":616,"value":1270},"可靠性問題（首次呼叫慢 9.4 倍、mid-session crash、權限不透明）",{"type":611,"tag":874,"props":1272,"children":1273},{},[1274],{"type":616,"value":1275},"功能與現有 CLI/API 高度重疊",{"type":611,"tag":612,"props":1277,"children":1278},{},[1279],{"type":616,"value":1280},"HN 討論中，多位開發者直指：OpenAPI spec、OAuth 及 sandbox 早已處理了這些問題。",{"type":611,"tag":612,"props":1282,"children":1283},{},[1284],{"type":616,"value":1285},"批評者認為 MCP 不過是把 REST + JSON + OAuth 重新包裝了一層——讓開發者多了學習成本，卻未帶來本質突破。",{"type":611,"tag":667,"props":1287,"children":1288},{},[1289],{"type":611,"tag":612,"props":1290,"children":1291},{},[1292,1296,1299],{"type":611,"tag":674,"props":1293,"children":1294},{},[1295],{"type":616,"value":678},{"type":611,"tag":680,"props":1297,"children":1298},{},[],{"type":616,"value":1300},"\nOpenAPI spec：一種描述 RESTful API 結構的標準規格，讓開發者與工具能自動理解 API 的端點、參數與回應格式，無需手動閱讀文件。",{"type":611,"tag":655,"props":1302,"children":1304},{"id":1303},"支持方標準化協議的不可替代價值",[1305],{"type":616,"value":1306},"支持方：標準化協議的不可替代價值",{"type":611,"tag":612,"props":1308,"children":1309},{},[1310],{"type":616,"value":1311},"支持方最有力的論點，來自 OpenAI 負責 MCP 的成員：MCP 的真正價值在於讓「原本沒有 API 的服務」得以暴露出來，讓 AI agent 取得原本無法獲得的存取權，而非協議本身的技術細節。",{"type":611,"tag":612,"props":1313,"children":1314},{},[1315],{"type":616,"value":1316},"企業端支持者則強調合規場景的優勢：憑證分離（LLM 只看 request，不碰 token）以及跨組織的集中式 policy 執行，讓合規管控遠比管理零散 CLI 工具容易。",{"type":611,"tag":612,"props":1318,"children":1319},{},[1320],{"type":616,"value":1321},"Quandri 也承認 MCP 在三種場景仍有其位置：",{"type":611,"tag":900,"props":1323,"children":1324},{},[1325,1330,1335],{"type":611,"tag":874,"props":1326,"children":1327},{},[1328],{"type":616,"value":1329},"沒有 CLI 介面的服務",{"type":611,"tag":874,"props":1331,"children":1332},{},[1333],{"type":616,"value":1334},"非開發者用戶需要無縫存取的場景",{"type":611,"tag":874,"props":1336,"children":1337},{},[1338],{"type":616,"value":1339},"生產資料庫需要憑證保護與安全護欄的情境",{"type":611,"tag":612,"props":1341,"children":1342},{},[1343],{"type":616,"value":1344},"這三種情境，恰好是 CLI-First 策略無法覆蓋的邊界地帶。",{"type":611,"tag":655,"props":1346,"children":1348},{"id":1347},"開發者該如何選擇工具整合方案",[1349],{"type":616,"value":1347},{"type":611,"tag":612,"props":1351,"children":1352},{},[1353],{"type":616,"value":1354},"Quandri 的替代方案「CLI-First + Skills Pattern」並非普世解法，而是針對開發者工具鏈高度重疊時的務實選擇。",{"type":611,"tag":612,"props":1356,"children":1357},{},[1358],{"type":616,"value":1359},"Skills Pattern 的核心邏輯是「只在需要時載入工具說明」，有效避免 context window 被大量未使用的工具定義佔滿。",{"type":611,"tag":612,"props":1361,"children":1362},{},[1363],{"type":616,"value":1364},"選擇的關鍵在於對使用場景的清醒認識：",{"type":611,"tag":900,"props":1366,"children":1367},{},[1368,1373],{"type":611,"tag":874,"props":1369,"children":1370},{},[1371],{"type":616,"value":1372},"服務已有完善 CLI 或 REST API，且使用者以開發者為主 → CLI-First 策略更輕量",{"type":611,"tag":874,"props":1374,"children":1375},{},[1376],{"type":616,"value":1377},"需跨組織統一憑證管理、服務尚無 API，或用戶群為非技術人員 → MCP 展現差異化價值",{"type":611,"tag":667,"props":1379,"children":1380},{},[1381],{"type":611,"tag":612,"props":1382,"children":1383},{},[1384,1388,1391],{"type":611,"tag":674,"props":1385,"children":1386},{},[1387],{"type":616,"value":721},{"type":611,"tag":680,"props":1389,"children":1390},{},[],{"type":616,"value":1392},"\n就像「計程車 vs. 大眾運輸」的選擇：計程車 (CLI) 靈活、直達、速度快；公車系統 (MCP) 標準化、路線固定、適合大規模跨組織人流。沒有誰更好，只有哪個更適合你的情境。",{"title":323,"searchDepth":618,"depth":618,"links":1394},[],{"data":1396,"body":1397,"excerpt":-1,"toc":1430},{"title":323,"description":323},{"type":608,"children":1398},[1399,1405,1410,1415,1420,1425],{"type":611,"tag":655,"props":1400,"children":1402},{"id":1401},"讓無-api-服務可被-ai-存取",[1403],{"type":616,"value":1404},"讓無 API 服務可被 AI 存取",{"type":611,"tag":612,"props":1406,"children":1407},{},[1408],{"type":616,"value":1409},"MCP 的核心價值不在技術細節，而在讓「原本沒有 API 的服務」得以暴露，讓 AI agent 取得原本無法獲得的存取權。",{"type":611,"tag":612,"props":1411,"children":1412},{},[1413],{"type":616,"value":1414},"這是 CLI 方案無法覆蓋的場景——若服務本身沒有 CLI 或 REST 介面，MCP 就是唯一的標準化橋接選項。",{"type":611,"tag":655,"props":1416,"children":1418},{"id":1417},"企業合規的結構性優勢",[1419],{"type":616,"value":1417},{"type":611,"tag":612,"props":1421,"children":1422},{},[1423],{"type":616,"value":1424},"憑證分離（LLM 只看 request，不接觸 token）搭配跨組織集中式 policy 執行，讓合規管控遠比管理零散 CLI 工具容易。",{"type":611,"tag":612,"props":1426,"children":1427},{},[1428],{"type":616,"value":1429},"對有嚴格資安要求的企業而言，這種結構性護欄難以用臨時性的 CLI 腳本替代，MCP 的標準化在此展現了真正的差異化。",{"title":323,"searchDepth":618,"depth":618,"links":1431},[],{"data":1433,"body":1434,"excerpt":-1,"toc":1467},{"title":323,"description":323},{"type":608,"children":1435},[1436,1442,1447,1452,1457,1462],{"type":611,"tag":655,"props":1437,"children":1439},{"id":1438},"context-window-的結構性浪費",[1440],{"type":616,"value":1441},"context window 的結構性浪費",{"type":611,"tag":612,"props":1443,"children":1444},{},[1445],{"type":616,"value":1446},"Quandri 實測顯示四個 MCP server 吃掉 200K context window 的 10.5%，Linear server 單獨消耗 12,800 tokens，實際用到的卻只有兩個函式。",{"type":611,"tag":612,"props":1448,"children":1449},{},[1450],{"type":616,"value":1451},"這種浪費隨 server 數量線性膨脹，對依賴大型 context 的工作流程是不可接受的結構性缺陷。",{"type":611,"tag":655,"props":1453,"children":1455},{"id":1454},"技術上毫無新意",[1456],{"type":616,"value":1454},{"type":611,"tag":612,"props":1458,"children":1459},{},[1460],{"type":616,"value":1461},"OpenAPI spec、OAuth 與 sandbox 早已解決 MCP 試圖解決的問題，MCP 不過是把 REST + JSON + OAuth 重新包裝，徒增學習成本而無本質突破。",{"type":611,"tag":612,"props":1463,"children":1464},{},[1465],{"type":616,"value":1466},"可靠性問題（首次呼叫慢 9.4 倍、mid-session crash、權限不透明）更讓這個「新協議」難以在生產環境信任使用。",{"title":323,"searchDepth":618,"depth":618,"links":1468},[],{"data":1470,"body":1471,"excerpt":-1,"toc":1503},{"title":323,"description":323},{"type":608,"children":1472},[1473,1478,1483,1488,1493,1498],{"type":611,"tag":655,"props":1474,"children":1476},{"id":1475},"協議本身不是問題",[1477],{"type":616,"value":1475},{"type":611,"tag":612,"props":1479,"children":1480},{},[1481],{"type":616,"value":1482},"MCP 作為協議並沒有根本性缺陷，問題在於團隊的使用方式——把所有 server 的工具定義全部塞入 context，等於把問題製造出來再怪工具本身。",{"type":611,"tag":655,"props":1484,"children":1486},{"id":1485},"場景決定選擇",[1487],{"type":616,"value":1485},{"type":611,"tag":612,"props":1489,"children":1490},{},[1491],{"type":616,"value":1492},"開發者工具鏈完整的團隊，CLI-First + Skills Pattern 是更輕量的選擇；跨組織管理、非技術用戶或服務尚無 API 的場景，MCP 標準化仍有其位置。",{"type":611,"tag":655,"props":1494,"children":1496},{"id":1495},"生態系慣性不容忽視",[1497],{"type":616,"value":1495},{"type":611,"tag":612,"props":1499,"children":1500},{},[1501],{"type":616,"value":1502},"MCP 在 16 個月內達到每月 9,700 萬次 SDK 下載，標準化帶來的互通性往往比純技術優劣更具決定性，生態系的慣性讓棄用成本遠高於修補。",{"title":323,"searchDepth":618,"depth":618,"links":1504},[],{"data":1506,"body":1507,"excerpt":-1,"toc":1563},{"title":323,"description":323},{"type":608,"children":1508},[1509,1514,1519,1524,1530,1535,1540,1545],{"type":611,"tag":655,"props":1510,"children":1512},{"id":1511},"對開發者的影響",[1513],{"type":616,"value":1511},{"type":611,"tag":612,"props":1515,"children":1516},{},[1517],{"type":616,"value":1518},"使用 MCP 前，應先盤點實際需要的工具數量，避免把所有 server 全部載入 context。",{"type":611,"tag":612,"props":1520,"children":1521},{},[1522],{"type":616,"value":1523},"Skills Pattern 的「按需載入」策略能有效控制 context window 使用量，改善 agent 的推理品質與回應穩定性。",{"type":611,"tag":655,"props":1525,"children":1527},{"id":1526},"對團隊組織的影響",[1528],{"type":616,"value":1529},"對團隊／組織的影響",{"type":611,"tag":612,"props":1531,"children":1532},{},[1533],{"type":616,"value":1534},"若團隊以開發者為主且工具鏈完整，CLI-First 策略往往更輕量且易於除錯。",{"type":611,"tag":612,"props":1536,"children":1537},{},[1538],{"type":616,"value":1539},"若需跨組織統一憑證管理，或服務用戶為非技術人員，MCP 的標準化協議才能展現差異化價值，值得投資建置成本。",{"type":611,"tag":655,"props":1541,"children":1543},{"id":1542},"短期行動建議",[1544],{"type":616,"value":1542},{"type":611,"tag":900,"props":1546,"children":1547},{},[1548,1553,1558],{"type":611,"tag":874,"props":1549,"children":1550},{},[1551],{"type":616,"value":1552},"現有 MCP 環境：審查 server 清單，移除低使用率工具定義，或改用 Skills Pattern 按需載入",{"type":611,"tag":874,"props":1554,"children":1555},{},[1556],{"type":616,"value":1557},"新專案評估：先確認服務是否已有 CLI 或 REST API，有則優先 CLI-First，無則考慮 MCP",{"type":611,"tag":874,"props":1559,"children":1560},{},[1561],{"type":616,"value":1562},"企業合規場景：評估憑證分離與集中式 policy 需求，有明確需求再導入 MCP",{"title":323,"searchDepth":618,"depth":618,"links":1564},[],{"data":1566,"body":1567,"excerpt":-1,"toc":1614},{"title":323,"description":323},{"type":608,"children":1568},[1569,1574,1579,1584,1589,1594,1599,1604,1609],{"type":611,"tag":655,"props":1570,"children":1572},{"id":1571},"產業結構變化",[1573],{"type":616,"value":1571},{"type":611,"tag":612,"props":1575,"children":1576},{},[1577],{"type":616,"value":1578},"MCP 在 16 個月內達到每月 9,700 萬次 SDK 下載，顯示生態系已形成相當慣性。",{"type":611,"tag":612,"props":1580,"children":1581},{},[1582],{"type":616,"value":1583},"即便存在設計瑕疵，標準化協議帶來的互通性——讓任意 AI agent 可接入任意 MCP server——往往比純技術優劣更具決定性，產業難以輕易放棄。",{"type":611,"tag":655,"props":1585,"children":1587},{"id":1586},"倫理邊界",[1588],{"type":616,"value":1586},{"type":611,"tag":612,"props":1590,"children":1591},{},[1592],{"type":616,"value":1593},"此次爭議的深層問題，在於 AI 工具鏈的「標準化 vs. 客製化」之爭。",{"type":611,"tag":612,"props":1595,"children":1596},{},[1597],{"type":616,"value":1598},"過度依賴標準化協議，可能導致 context window 被通用工具定義大量佔用，壓縮 AI 真正執行任務的空間；放棄標準化，則可能讓每個團隊各自為政，提高整個生態系的整合成本。",{"type":611,"tag":655,"props":1600,"children":1602},{"id":1601},"長期趨勢預測",[1603],{"type":616,"value":1601},{"type":611,"tag":612,"props":1605,"children":1606},{},[1607],{"type":616,"value":1608},"短期內，MCP 與 CLI-First 將並存於不同場景，不存在「一個協議取代一切」的局面。",{"type":611,"tag":612,"props":1610,"children":1611},{},[1612],{"type":616,"value":1613},"中長期看，協議可能朝「動態工具載入」演進——只在 agent 需要時才將工具定義注入 context，從根本解決 context window 浪費問題。",{"title":323,"searchDepth":618,"depth":618,"links":1615},[],{"data":1617,"body":1618,"excerpt":-1,"toc":1624},{"title":323,"description":118},{"type":608,"children":1619},[1620],{"type":611,"tag":612,"props":1621,"children":1622},{},[1623],{"type":616,"value":118},{"title":323,"searchDepth":618,"depth":618,"links":1625},[],{"data":1627,"body":1628,"excerpt":-1,"toc":1634},{"title":323,"description":119},{"type":608,"children":1629},[1630],{"type":611,"tag":612,"props":1631,"children":1632},{},[1633],{"type":616,"value":119},{"title":323,"searchDepth":618,"depth":618,"links":1635},[],{"data":1637,"body":1638,"excerpt":-1,"toc":1644},{"title":323,"description":183},{"type":608,"children":1639},[1640],{"type":611,"tag":612,"props":1641,"children":1642},{},[1643],{"type":616,"value":183},{"title":323,"searchDepth":618,"depth":618,"links":1645},[],{"data":1647,"body":1648,"excerpt":-1,"toc":1654},{"title":323,"description":186},{"type":608,"children":1649},[1650],{"type":611,"tag":612,"props":1651,"children":1652},{},[1653],{"type":616,"value":186},{"title":323,"searchDepth":618,"depth":618,"links":1655},[],{"data":1657,"body":1658,"excerpt":-1,"toc":1664},{"title":323,"description":188},{"type":608,"children":1659},[1660],{"type":611,"tag":612,"props":1661,"children":1662},{},[1663],{"type":616,"value":188},{"title":323,"searchDepth":618,"depth":618,"links":1665},[],{"data":1667,"body":1668,"excerpt":-1,"toc":1674},{"title":323,"description":190},{"type":608,"children":1669},[1670],{"type":611,"tag":612,"props":1671,"children":1672},{},[1673],{"type":616,"value":190},{"title":323,"searchDepth":618,"depth":618,"links":1675},[],{"data":1677,"body":1678,"excerpt":-1,"toc":1812},{"title":323,"description":323},{"type":608,"children":1679},[1680,1686,1691,1696,1711,1717,1722,1737,1742,1747,1752,1758,1763,1768,1773,1779,1784,1789,1807],{"type":611,"tag":655,"props":1681,"children":1683},{"id":1682},"前端失落十年的歷史回顧",[1684],{"type":616,"value":1685},"前端「失落十年」的歷史回顧",{"type":611,"tag":612,"props":1687,"children":1688},{},[1689],{"type":616,"value":1690},"2010 年代，React、Angular、Vue 等 JavaScript 框架浪潮崛起，將瀏覽器視為應用程式的編譯目標，而非文件呈現環境。開發者開始透過元件庫封裝底層 HTML 邏輯，逐漸失去對語意化標籤、瀏覽器差異、無障礙設計 (accessibility) 與漸進增強的深層理解。",{"type":611,"tag":612,"props":1692,"children":1693},{},[1694],{"type":616,"value":1695},"這套能力被業界稱為「front of the frontend」——包含符合 WCAG 標準的 HTML 撰寫、跨裝置效能最佳化、以及完整的鍵盤導航支援。以 shadcn 的 radio button 元件為例：一行程式碼背後包裹著 ARIA 屬性與鍵盤互動的複雜度，讓開發者徹底失去理解機會。十年後，整個產業才意識到這段時期留下了多深的能力缺口。",{"type":611,"tag":667,"props":1697,"children":1698},{},[1699],{"type":611,"tag":612,"props":1700,"children":1701},{},[1702,1706,1709],{"type":611,"tag":674,"props":1703,"children":1704},{},[1705],{"type":616,"value":678},{"type":611,"tag":680,"props":1707,"children":1708},{},[],{"type":616,"value":1710},"\nWCAG(Web Content Accessibility Guidelines) ：W3C 制定的網頁內容無障礙設計指引，規範文字對比度、鍵盤可操作性、螢幕閱讀器相容性等標準，是無障礙設計的國際基準。",{"type":611,"tag":655,"props":1712,"children":1714},{"id":1713},"ai-生成程式碼的品質與技術債隱憂",[1715],{"type":616,"value":1716},"AI 生成程式碼的品質與技術債隱憂",{"type":611,"tag":612,"props":1718,"children":1719},{},[1720],{"type":616,"value":1721},"2026 年，全球新增程式碼中 41% 為 AI 生成，但大多數未經有效審查便直接上線。Mastro 部落格的核心論點指出：AI 程式碼生成是「漏洞抽象 (leaky abstraction) 」，與確定性編譯器根本不同——微小的輸入差異或模型版本變更就會產生截然不同的輸出，行為更像不穩定的初級工程師，而非可靠工具。",{"type":611,"tag":667,"props":1723,"children":1724},{},[1725],{"type":611,"tag":612,"props":1726,"children":1727},{},[1728,1732,1735],{"type":611,"tag":674,"props":1729,"children":1730},{},[1731],{"type":616,"value":678},{"type":611,"tag":680,"props":1733,"children":1734},{},[],{"type":616,"value":1736},"\n漏洞抽象 (leaky abstraction) ：指抽象層無法完全隱藏底層細節的現象，使用者終究需要理解底層才能除錯。由 Joel Spolsky 在 2002 年提出，常被用來描述「方便但遮蔽複雜度的工具」的固有風險。",{"type":611,"tag":612,"props":1738,"children":1739},{},[1740],{"type":616,"value":1741},"arXiv 大規模實證研究 (2603.28592) 分析了跨 6,275 個 GitHub repo 的 304,362 筆 AI 提交，揭示了一個不對稱能力問題：AI 工具擅長修正表層的程式碼壞味道，但引入的 bug 與安全問題數量多於修復的。在所發現的 484,606 個問題中，程式碼壞味道佔 89.1%、執行時 bug 佔 5.8%、安全漏洞佔 5.1%，且 24.2% 的 AI 技術債在最新版本仍未被修復。",{"type":611,"tag":612,"props":1743,"children":1744},{},[1745],{"type":616,"value":1746},"從生產力指標來看，AI 導入後每位開發者的 PR 數量增加 20%，但每個 PR 的線上事故率同步上升 23.5%。",{"type":611,"tag":612,"props":1748,"children":1749},{},[1750],{"type":616,"value":1751},"Forrester 預測 75% 的技術決策者將在 2026 年前面臨中度至嚴重的技術債；Gartner 則預測「prompt-to-app」方式將在 2028 年前讓軟體缺陷增加 2,500%。若不主動管理，AI 生成技術債的維護成本將在第二年達到傳統開發的 4 倍。",{"type":611,"tag":655,"props":1753,"children":1755},{"id":1754},"社群分歧效率提升還是劣幣驅逐良幣",[1756],{"type":616,"value":1757},"社群分歧：效率提升還是劣幣驅逐良幣",{"type":611,"tag":612,"props":1759,"children":1760},{},[1761],{"type":616,"value":1762},"HN 討論串呈現了鮮明的立場分歧。批評方認為 AI 加速了去技能化——knuckleheads 指出這不過是「軟體從工藝轉向工業化流程」的 20 年趨勢在 AI 時代的加速版本，對行業長期健康有深遠危害。",{"type":611,"tag":612,"props":1764,"children":1765},{},[1766],{"type":616,"value":1767},"支持方則提出反例：hombre_fatal 認為 LLMs 對 ARIA 無障礙屬性的掌握可能超過 90% 以上的前端開發者，AI 反而有機會在過去無人投資的角落推廣最佳實踐。d0liver 則直白指出，AI 出現之前軟體品質就已問題重重——把劣化責任全歸咎於 AI 工具，是一種不誠實的歷史敘事。",{"type":611,"tag":612,"props":1769,"children":1770},{},[1771],{"type":616,"value":1772},"bayarearefugee 提出了一個更深遠的結構性隱憂：開源生態系的貢獻長期依賴有穩定工作的開發者在業餘時間投入，若 AI 擾亂就業市場，這個生態基礎也將動搖——這是超越個別工具品質之外更難以修復的損傷。",{"type":611,"tag":655,"props":1774,"children":1776},{"id":1775},"開發者如何在-ai-時代保持專業價值",[1777],{"type":616,"value":1778},"開發者如何在 AI 時代保持專業價值",{"type":611,"tag":612,"props":1780,"children":1781},{},[1782],{"type":616,"value":1783},"esalman 在 HN 討論串中道出了核心洞見：「用 Rust 其實是這道問題最無趣的部分，沒有一定程度的領域知識，幾乎不可能解決它。」語言選擇或工具選擇從來不是真正的門檻——領域知識的深度才是。",{"type":611,"tag":612,"props":1785,"children":1786},{},[1787],{"type":616,"value":1788},"能辨識 AI 輸出是否邏輯一致、安全可靠、符合業務需求的工程師，在 AI 時代反而更有價值。具體策略包括：",{"type":611,"tag":900,"props":1790,"children":1791},{},[1792,1797,1802],{"type":611,"tag":874,"props":1793,"children":1794},{},[1795],{"type":616,"value":1796},"主動學習 AI 工具的弱項（語意 HTML、安全邊界、作用域管理），在 code review 中重點稽核這些環節",{"type":611,"tag":874,"props":1798,"children":1799},{},[1800],{"type":616,"value":1801},"建立「AI 輔助但人工審查」的工作流程，而非「AI 生成直接上線」的習慣",{"type":611,"tag":874,"props":1803,"children":1804},{},[1805],{"type":616,"value":1806},"持續培養對底層機制的理解，確保在抽象層洩漏時有能力下探除錯",{"type":611,"tag":612,"props":1808,"children":1809},{},[1810],{"type":616,"value":1811},"文章作者的警示仍然有效：「在某個時間點，抽象終究會洩漏，而到時候必須有人投入時間解決。」那個人，最好是你。",{"title":323,"searchDepth":618,"depth":618,"links":1813},[],{"data":1815,"body":1817,"excerpt":-1,"toc":1833},{"title":323,"description":1816},"AI 輔助開發提高了開發可及性，讓原本無法實作 ARIA 標準的開發者也能產出符合無障礙設計的程式碼。",{"type":608,"children":1818},[1819,1823,1828],{"type":611,"tag":612,"props":1820,"children":1821},{},[1822],{"type":616,"value":1816},{"type":611,"tag":612,"props":1824,"children":1825},{},[1826],{"type":616,"value":1827},"LLMs 對最佳實踐的掌握往往超過一般開發者，理論上能填補長期被忽視的品質缺口——尤其在語意化 HTML 與無障礙設計這類「沒人願意投資」的領域。",{"type":611,"tag":612,"props":1829,"children":1830},{},[1831],{"type":616,"value":1832},"20% 的 PR 產出率提升是真實的生產力增益。技術債問題可透過更嚴格的審查流程管理，而非拒絕工具本身——工具無罪，流程紀律才是關鍵。",{"title":323,"searchDepth":618,"depth":618,"links":1834},[],{"data":1836,"body":1838,"excerpt":-1,"toc":1854},{"title":323,"description":1837},"AI 輔助開發加速了去技能化：當開發者習慣讓 AI 生成邏輯，對底層機制的理解逐漸退化，形成正向回饋迴圈——技能越低，越依賴 AI，越失去鑑別 AI 錯誤的能力。",{"type":608,"children":1839},[1840,1844,1849],{"type":611,"tag":612,"props":1841,"children":1842},{},[1843],{"type":616,"value":1837},{"type":611,"tag":612,"props":1845,"children":1846},{},[1847],{"type":616,"value":1848},"arXiv 研究顯示 AI 引入的 bug 多於修復的，超過 15% 的 commit 帶有問題，24.2% 的技術債未被修復。",{"type":611,"tag":612,"props":1850,"children":1851},{},[1852],{"type":616,"value":1853},"PR 產出量增加 20% 但事故率增加 23.5%，精準呈現「速度換穩定性」的代價。這不只是管理問題，而是工具本身行為像不穩定初級工程師的結構性問題。",{"title":323,"searchDepth":618,"depth":618,"links":1855},[],{"data":1857,"body":1859,"excerpt":-1,"toc":1875},{"title":323,"description":1858},"問題的核心不是 AI 工具本身，而是開發文化能否維持有意義的品質審查。",{"type":608,"children":1860},[1861,1865,1870],{"type":611,"tag":612,"props":1862,"children":1863},{},[1864],{"type":616,"value":1858},{"type":611,"tag":612,"props":1866,"children":1867},{},[1868],{"type":616,"value":1869},"把 AI 當成免責工具（「AI 生成的，我不負責」）會放大所有問題；把它當成需要指導與審查的初級協作者，多數問題都可管理。",{"type":611,"tag":612,"props":1871,"children":1872},{},[1873],{"type":616,"value":1874},"真正的差異在於工程師能否保持對底層技術的理解——當漏洞抽象洩漏時，必須有人有能力下探除錯。這種能力不能外包給 AI，也不能靠抽象工具維持。",{"title":323,"searchDepth":618,"depth":618,"links":1876},[],{"data":1878,"body":1879,"excerpt":-1,"toc":1949},{"title":323,"description":323},{"type":608,"children":1880},[1881,1885,1890,1895,1913,1917,1922,1927,1931],{"type":611,"tag":655,"props":1882,"children":1883},{"id":1511},[1884],{"type":616,"value":1511},{"type":611,"tag":612,"props":1886,"children":1887},{},[1888],{"type":616,"value":1889},"AI 工具讓程式碼產出速度大幅提升，但同時要求開發者具備更強的審查能力，而非更弱。能識別 AI 生成程式碼中的邏輯錯誤、安全漏洞、語意問題的工程師，在 AI 時代反而更有價值。",{"type":611,"tag":612,"props":1891,"children":1892},{},[1893],{"type":616,"value":1894},"具體行為變化包括：",{"type":611,"tag":900,"props":1896,"children":1897},{},[1898,1903,1908],{"type":611,"tag":874,"props":1899,"children":1900},{},[1901],{"type":616,"value":1902},"在接受 AI 建議前先理解其底層邏輯，而非直接複製貼上",{"type":611,"tag":874,"props":1904,"children":1905},{},[1906],{"type":616,"value":1907},"在熟悉的領域使用 AI 提速，在不熟悉的領域保持手動實作以維持學習路徑",{"type":611,"tag":874,"props":1909,"children":1910},{},[1911],{"type":616,"value":1912},"主動補強 AI 的弱項：語意化 HTML、無障礙設計、安全邊界",{"type":611,"tag":655,"props":1914,"children":1915},{"id":1526},[1916],{"type":616,"value":1529},{"type":611,"tag":612,"props":1918,"children":1919},{},[1920],{"type":616,"value":1921},"組織需要在「AI 提速」與「品質維護」之間建立顯式的平衡機制。僅追蹤 PR 數量而不追蹤事故率，等同於以隱性方式接受「更多缺陷換取更快速度」的決策。",{"type":611,"tag":612,"props":1923,"children":1924},{},[1925],{"type":616,"value":1926},"招募策略也需要調整：能審查 AI 程式碼的資深工程師比純粹的 AI 輸出者更稀缺，薪資溢價將逐漸集中在具備底層技術深度的工程師身上。",{"type":611,"tag":655,"props":1928,"children":1929},{"id":1542},[1930],{"type":616,"value":1542},{"type":611,"tag":900,"props":1932,"children":1933},{},[1934,1939,1944],{"type":611,"tag":874,"props":1935,"children":1936},{},[1937],{"type":616,"value":1938},"為 AI 輔助開發建立明確的 code review 標準，而非沿用傳統人工撰寫程式碼的審查慣例",{"type":611,"tag":874,"props":1940,"children":1941},{},[1942],{"type":616,"value":1943},"每季追蹤一次 AI-assisted PR 的事故率與技術債累積速度，作為工具使用健康度的量化指標",{"type":611,"tag":874,"props":1945,"children":1946},{},[1947],{"type":616,"value":1948},"定期安排「無 AI 練習」時段，確保開發者的底層技能不會因過度依賴工具而退化",{"title":323,"searchDepth":618,"depth":618,"links":1950},[],{"data":1952,"body":1953,"excerpt":-1,"toc":2002},{"title":323,"description":323},{"type":608,"children":1954},[1955,1959,1964,1969,1973,1978,1983,1987,1992,1997],{"type":611,"tag":655,"props":1956,"children":1957},{"id":1571},[1958],{"type":616,"value":1571},{"type":611,"tag":612,"props":1960,"children":1961},{},[1962],{"type":616,"value":1963},"去技能化的長期影響會重塑就業市場的結構。入門級工程師職位可能萎縮——原本由初級工程師處理的程式碼生成工作正被 AI 替代，但這也切斷了讓新人累積技能的成長路徑。",{"type":611,"tag":612,"props":1965,"children":1966},{},[1967],{"type":616,"value":1968},"bayarearefugee 提出的開源生態隱憂值得重視：開源社群的活力長期依賴有穩定收入的工程師投入業餘時間貢獻，若 AI 持續壓縮初中階職位，開源生態的人才補給管道也將隨之萎縮。",{"type":611,"tag":655,"props":1970,"children":1971},{"id":1586},[1972],{"type":616,"value":1586},{"type":611,"tag":612,"props":1974,"children":1975},{},[1976],{"type":616,"value":1977},"核心倫理問題不是「AI 是否應該用於寫程式」，而是「誰為 AI 生成的有缺陷程式碼負責」。",{"type":611,"tag":612,"props":1979,"children":1980},{},[1981],{"type":616,"value":1982},"當 41% 的新增程式碼為 AI 生成且大多數未經有效審查，現行的程式碼品質問責機制已不足以應對這個規模。公共系統、醫療軟體、金融基礎設施若採用未充分審查的 AI 程式碼，後果不只是技術債，而是真實世界的安全風險。",{"type":611,"tag":655,"props":1984,"children":1985},{"id":1601},[1986],{"type":616,"value":1601},{"type":611,"tag":612,"props":1988,"children":1989},{},[1990],{"type":616,"value":1991},"短期內（1-2 年），技術債問題將持續累積，直到幾個高知名度的線上事故迫使產業建立更嚴格的 AI 程式碼審查標準。",{"type":611,"tag":612,"props":1993,"children":1994},{},[1995],{"type":616,"value":1996},"中期（3-5 年），能夠自動審查 AI 生成程式碼的工具 (AI-on-AI auditing) 將成為新興市場，靜態分析與形式驗證工具將迎來需求爆發。",{"type":611,"tag":612,"props":1998,"children":1999},{},[2000],{"type":616,"value":2001},"長期來看，「前端失落十年」的歷史教訓顯示：在技術能力被抽象化後，重建底層知識比預防失去更昂貴。現在投資工程師底層技能培訓的成本，遠低於未來除錯無人能理解的 AI 生成程式碼的代價。",{"title":323,"searchDepth":618,"depth":618,"links":2003},[],{"data":2005,"body":2006,"excerpt":-1,"toc":2012},{"title":323,"description":193},{"type":608,"children":2007},[2008],{"type":611,"tag":612,"props":2009,"children":2010},{},[2011],{"type":616,"value":193},{"title":323,"searchDepth":618,"depth":618,"links":2013},[],{"data":2015,"body":2016,"excerpt":-1,"toc":2022},{"title":323,"description":194},{"type":608,"children":2017},[2018],{"type":611,"tag":612,"props":2019,"children":2020},{},[2021],{"type":616,"value":194},{"title":323,"searchDepth":618,"depth":618,"links":2023},[],{"data":2025,"body":2026,"excerpt":-1,"toc":2032},{"title":323,"description":195},{"type":608,"children":2027},[2028],{"type":611,"tag":612,"props":2029,"children":2030},{},[2031],{"type":616,"value":195},{"title":323,"searchDepth":618,"depth":618,"links":2033},[],{"data":2035,"body":2036,"excerpt":-1,"toc":2042},{"title":323,"description":253},{"type":608,"children":2037},[2038],{"type":611,"tag":612,"props":2039,"children":2040},{},[2041],{"type":616,"value":253},{"title":323,"searchDepth":618,"depth":618,"links":2043},[],{"data":2045,"body":2046,"excerpt":-1,"toc":2052},{"title":323,"description":256},{"type":608,"children":2047},[2048],{"type":611,"tag":612,"props":2049,"children":2050},{},[2051],{"type":616,"value":256},{"title":323,"searchDepth":618,"depth":618,"links":2053},[],{"data":2055,"body":2056,"excerpt":-1,"toc":2062},{"title":323,"description":258},{"type":608,"children":2057},[2058],{"type":611,"tag":612,"props":2059,"children":2060},{},[2061],{"type":616,"value":258},{"title":323,"searchDepth":618,"depth":618,"links":2063},[],{"data":2065,"body":2066,"excerpt":-1,"toc":2072},{"title":323,"description":260},{"type":608,"children":2067},[2068],{"type":611,"tag":612,"props":2069,"children":2070},{},[2071],{"type":616,"value":260},{"title":323,"searchDepth":618,"depth":618,"links":2073},[],{"data":2075,"body":2076,"excerpt":-1,"toc":2224},{"title":323,"description":323},{"type":608,"children":2077},[2078,2084,2096,2101,2121,2126,2132,2137,2157,2162,2167,2173,2178,2183,2198,2203,2209,2214,2219],{"type":611,"tag":655,"props":2079,"children":2081},{"id":2080},"qwen-36-q4xl-消費級硬體實測數據",[2082],{"type":616,"value":2083},"Qwen 3.6 q4xl 消費級硬體實測數據",{"type":611,"tag":612,"props":2085,"children":2086},{},[2087,2089,2094],{"type":616,"value":2088},"2026 年 5 月，一篇 r/LocalLLaMA 貼文在社群引發轟動：一位玩家用兩張 RTX 4060 Ti（共 32GB VRAM），搭配 Q4_K_XL 量化版本，成功讓 Qwen3.6-35B-A3B 跑出 ",{"type":611,"tag":674,"props":2090,"children":2091},{},[2092],{"type":616,"value":2093},"125 tok/s",{"type":616,"value":2095}," 的生成速度。",{"type":611,"tag":612,"props":2097,"children":2098},{},[2099],{"type":616,"value":2100},"Qwen3.6-35B-A3B 於 2026-04-15 由阿里巴巴發布，採用全新 Gated DeltaNet 線性注意力架構與 Sparse MoE 設計（256 個 expert，每次路由 8 個加 1 個共享），原生支援多模態輸入與最長 262K 的 context 視窗。",{"type":611,"tag":667,"props":2102,"children":2103},{},[2104],{"type":611,"tag":612,"props":2105,"children":2106},{},[2107,2111,2114,2119],{"type":611,"tag":674,"props":2108,"children":2109},{},[2110],{"type":616,"value":678},{"type":611,"tag":680,"props":2112,"children":2113},{},[],{"type":611,"tag":674,"props":2115,"children":2116},{},[2117],{"type":616,"value":2118},"Sparse MoE(Sparse Mixture of Experts)",{"type":616,"value":2120},"：一種將模型分成多個「專家」子網路的架構，每次推論只啟動少數專家，讓模型參數總量很大但實際運算量相對精簡。Qwen3.6-35B-A3B 雖有 35B 參數，每次推論僅用約 3B 活躍參數。",{"type":611,"tag":612,"props":2122,"children":2123},{},[2124],{"type":616,"value":2125},"這個成績之所以讓社群稱為「insane perf/dollar」，關鍵在於 Q4_K_XL 量化讓整個模型塞進雙卡 32GB VRAM，而兩張 4060 Ti 的市場總價遠低於單張 RTX 4090，實測速度卻仍具競爭力。",{"type":611,"tag":655,"props":2127,"children":2129},{"id":2128},"nvfp4-量化的爭議與-sm_120-支援現況",[2130],{"type":616,"value":2131},"nvfp4 量化的爭議與 sm_120 支援現況",{"type":611,"tag":612,"props":2133,"children":2134},{},[2135],{"type":616,"value":2136},"llama.cpp 於 2026-04-29(build b8967) 正式為 Blackwell 架構 (sm_120) 啟用 NVFP4 tensor core 原生路徑，prefill 速度據稱提升 43–68%。然而這對 4060 Ti 用戶幾乎沒有意義——Ada Lovelace 架構 (sm_89) 不具備 FP4 tensor core，NVFP4 在此只能獲得記憶體節省效益，無任何速度加成。",{"type":611,"tag":667,"props":2138,"children":2139},{},[2140],{"type":611,"tag":612,"props":2141,"children":2142},{},[2143,2147,2150,2155],{"type":611,"tag":674,"props":2144,"children":2145},{},[2146],{"type":616,"value":678},{"type":611,"tag":680,"props":2148,"children":2149},{},[],{"type":611,"tag":674,"props":2151,"children":2152},{},[2153],{"type":616,"value":2154},"NVFP4",{"type":616,"value":2156},"：NVIDIA 專有的 4-bit 浮點數格式，需要硬體 tensor core 原生支援才能獲得速度提升。Blackwell（RTX 50 系列）才有此硬體；Ada Lovelace（RTX 40 系列）只能透過模擬執行，僅省記憶體不加速。",{"type":611,"tag":612,"props":2158,"children":2159},{},[2160],{"type":616,"value":2161},"社群對 NVFP4 的評價出現明顯分歧。u/jtjstock 直接批評「NVFP4 在 llama 上目前很爛」，而 u/Xp_12 更細緻地指出，問題根源在於量化配方品質（KLD 偏差）與 sm_120 加速支援尚未完整，並非格式本身有根本缺陷——w4a16 相對穩定，w4a4 的高品質配方難覓，但 vllm 的 b12x 支援正在推進。",{"type":611,"tag":612,"props":2163,"children":2164},{},[2165],{"type":616,"value":2166},"InsiderLLM 的分析也印證，NVFP4 與 Q4_K_M 的品質對比尚無定論，現階段在非 Blackwell 硬體上選用 K-quant 格式仍是更穩定的選擇。",{"type":611,"tag":655,"props":2168,"children":2170},{"id":2169},"性價比分析為何-4060-ti-成為本地推論新寵",[2171],{"type":616,"value":2172},"性價比分析：為何 4060 Ti 成為本地推論新寵",{"type":611,"tag":612,"props":2174,"children":2175},{},[2176],{"type":616,"value":2177},"記憶體頻寬是本地 LLM 推論最關鍵的瓶頸。RTX 4060 Ti 的 128-bit 匯流排僅提供 288 GB/s，而 RTX 4090 的 384-bit 匯流排可達 1,008 GB/s——後者是前者的 3.5 倍。",{"type":611,"tag":612,"props":2179,"children":2180},{},[2181],{"type":616,"value":2182},"然而，雙卡 4060 Ti 方案的邏輯不在於頻寬碾壓，而在於 VRAM 容量解鎖：兩張 4060 Ti 16GB 合計 32GB，足以完整載入 Qwen3.6-35B-A3B Q4_K_XL，而單張 4090 的 24GB 在此規格下恐面臨 VRAM 不足的限制。",{"type":611,"tag":667,"props":2184,"children":2185},{},[2186],{"type":611,"tag":612,"props":2187,"children":2188},{},[2189,2193,2196],{"type":611,"tag":674,"props":2190,"children":2191},{},[2192],{"type":616,"value":721},{"type":611,"tag":680,"props":2194,"children":2195},{},[],{"type":616,"value":2197},"\n把模型想成一本超厚字典，4060 Ti 是普通書架，4090 是寬版書架但只有一個。兩個普通書架合在一起放得下這本超厚字典；一個寬版書架因為長度不夠反而塞不進去——這就是 32GB vs 24GB 的本質差異。",{"type":611,"tag":612,"props":2199,"children":2200},{},[2201],{"type":616,"value":2202},"hardware-corner.net 的 GPU 排行榜也印證，對需要大 VRAM 的模型而言，雙卡低階方案的性價比往往優於高階單卡，兩張 4060 Ti 總價約為單張 4090 的 60–70%。",{"type":611,"tag":655,"props":2204,"children":2206},{"id":2205},"本地-llm-推論的未來展望",[2207],{"type":616,"value":2208},"本地 LLM 推論的未來展望",{"type":611,"tag":612,"props":2210,"children":2211},{},[2212],{"type":616,"value":2213},"此次 Qwen3.6 實測的意義，不只是一個跑分紀錄，而是一個更廣泛的訊號：消費級硬體組合正在趕上主流 35B 級模型的實用門檻，生成速度已足以支撐真實的本地 agentic 工作流程。",{"type":611,"tag":612,"props":2215,"children":2216},{},[2217],{"type":616,"value":2218},"Mike Masnick 在 Bluesky 分享，他花了整個週末將 agentic 設定切換到以本地模型為主（Gemma 4 31B 與 Qwen3.6-35B-A3B），結論是「本地模型現在真的很厲害」，印證了社群信心正在快速上升。",{"type":611,"tag":612,"props":2220,"children":2221},{},[2222],{"type":616,"value":2223},"從架構角度看，MoE 設計（活躍參數 3B）讓大參數模型在有限算力下實現高速生成，這個趨勢將持續推動「低預算跑大模型」的可能性邊界。當 sm_120 的 NVFP4 路徑成熟後，下一代消費級 GPU 的推論速度可望再有明顯躍升。",{"title":323,"searchDepth":618,"depth":618,"links":2225},[],{"data":2227,"body":2229,"excerpt":-1,"toc":2235},{"title":323,"description":2228},"Qwen3.6-35B-A3B 的高速本地推論是三個技術決策協同作用的結果：線性注意力降低長序列計算量、稀疏專家路由壓縮活躍算力、量化策略在精度與速度間取得平衡。",{"type":608,"children":2230},[2231],{"type":611,"tag":612,"props":2232,"children":2233},{},[2234],{"type":616,"value":2228},{"title":323,"searchDepth":618,"depth":618,"links":2236},[],{"data":2238,"body":2240,"excerpt":-1,"toc":2271},{"title":323,"description":2239},"傳統 Transformer 的注意力計算複雜度是 O(n²) ，隨 context 長度呈平方增長。Gated DeltaNet 引入線性注意力近似，將複雜度降至 O(n) ，使 262K context 視窗在有限記憶體下成為可能。",{"type":608,"children":2241},[2242,2246,2251],{"type":611,"tag":612,"props":2243,"children":2244},{},[2245],{"type":616,"value":2239},{"type":611,"tag":612,"props":2247,"children":2248},{},[2249],{"type":616,"value":2250},"「Gated」機制加入可學習的閘控層，改善了原版線性注意力在局部模式學習上的弱點，在長序列推論中提供更穩定的梯度流，讓模型長文本理解品質更接近標準注意力。",{"type":611,"tag":667,"props":2252,"children":2253},{},[2254],{"type":611,"tag":612,"props":2255,"children":2256},{},[2257,2261,2264,2269],{"type":611,"tag":674,"props":2258,"children":2259},{},[2260],{"type":616,"value":678},{"type":611,"tag":680,"props":2262,"children":2263},{},[],{"type":611,"tag":674,"props":2265,"children":2266},{},[2267],{"type":616,"value":2268},"DeltaNet",{"type":616,"value":2270},"：一種將注意力機制轉化為遞迴形式的線性注意力架構，透過差分更新 (delta) 計算注意力，避免全序列的二次複雜度。Gated 版本加入閘控機制後，在局部模式學習與長程依賴之間取得更好的平衡。",{"title":323,"searchDepth":618,"depth":618,"links":2272},[],{"data":2274,"body":2276,"excerpt":-1,"toc":2287},{"title":323,"description":2275},"模型擁有 256 個 expert 子網路，每次 token 生成只啟動 8 個路由 expert 加 1 個共享 expert，實際活躍參數約 3B。這讓「35B 模型」的推論計算成本接近 3B 模型，而知識容量卻來自完整 256 個 expert 的訓練積累。",{"type":608,"children":2277},[2278,2282],{"type":611,"tag":612,"props":2279,"children":2280},{},[2281],{"type":616,"value":2275},{"type":611,"tag":612,"props":2283,"children":2284},{},[2285],{"type":616,"value":2286},"對消費級硬體而言，這意味著每次生成的計算量大幅減少，算力瓶頸顯著降低，Q4_K_XL 量化的速度損耗在實際體驗中更能被接受。",{"title":323,"searchDepth":618,"depth":618,"links":2288},[],{"data":2290,"body":2292,"excerpt":-1,"toc":2318},{"title":323,"description":2291},"Q4_K_XL 是 K-quant 家族的 extra-large 變體，相比廣泛使用的 Q4_K_M（HuggingFace 上逾 13.5 萬個模型採用），它在 4-bit 記憶體佔用的基礎上採用更高混合精度配置，在關鍵層保留更高精度，輸出品質更接近全精度模型。",{"type":608,"children":2293},[2294,2298,2303],{"type":611,"tag":612,"props":2295,"children":2296},{},[2297],{"type":616,"value":2291},{"type":611,"tag":612,"props":2299,"children":2300},{},[2301],{"type":616,"value":2302},"對 4060 Ti 這類頻寬受限的架構，Q4_K_XL 比 NVFP4 更合適——前者有成熟的量化配方與廣泛的社群驗證，後者在 Ada Lovelace 上無速度提升，且 w4a4 高品質配方難覓。",{"type":611,"tag":667,"props":2304,"children":2305},{},[2306],{"type":611,"tag":612,"props":2307,"children":2308},{},[2309,2313,2316],{"type":611,"tag":674,"props":2310,"children":2311},{},[2312],{"type":616,"value":721},{"type":611,"tag":680,"props":2314,"children":2315},{},[],{"type":616,"value":2317},"\n把量化想成把高清影片壓縮成較小的檔案：Q4_K_XL 是智慧壓縮，在重要場景自動保留高畫質；NVFP4 是下一代壓縮格式，在支援它的新型播放器 (Blackwell GPU) 上極快，但在舊播放器 (4060 Ti) 上只省空間、播放速度不變。",{"title":323,"searchDepth":618,"depth":618,"links":2319},[],{"data":2321,"body":2322,"excerpt":-1,"toc":2438},{"title":323,"description":323},{"type":608,"children":2323},[2324,2328,2349,2353,2374,2378,2383,2387,2405,2409,2427,2433],{"type":611,"tag":655,"props":2325,"children":2326},{"id":949},[2327],{"type":616,"value":949},{"type":611,"tag":900,"props":2329,"children":2330},{},[2331,2340],{"type":611,"tag":874,"props":2332,"children":2333},{},[2334,2338],{"type":611,"tag":674,"props":2335,"children":2336},{},[2337],{"type":616,"value":962},{"type":616,"value":2339},"：Meta Llama 4 Scout（同為 MoE 架構，活躍參數接近）、Google Gemma 4 31B（本地推論玩家常見替代，與 Qwen3.6 並列測試）、Mistral 22B（參數較小，能力有差距）",{"type":611,"tag":874,"props":2341,"children":2342},{},[2343,2347],{"type":611,"tag":674,"props":2344,"children":2345},{},[2346],{"type":616,"value":972},{"type":616,"value":2348},"：商業 API 服務（Claude Haiku、GPT-4o mini）——不在乎隱私的場景替代",{"type":611,"tag":655,"props":2350,"children":2351},{"id":977},[2352],{"type":616,"value":977},{"type":611,"tag":900,"props":2354,"children":2355},{},[2356,2365],{"type":611,"tag":874,"props":2357,"children":2358},{},[2359,2363],{"type":611,"tag":674,"props":2360,"children":2361},{},[2362],{"type":616,"value":990},{"type":616,"value":2364},"：Gated DeltaNet + Sparse MoE 的架構研發與大規模訓練資源投入，非開源社群短期可複製",{"type":611,"tag":874,"props":2366,"children":2367},{},[2368,2372],{"type":611,"tag":674,"props":2369,"children":2370},{},[2371],{"type":616,"value":1000},{"type":616,"value":2373},"：Qwen 系列在 GGUF 社群已累積大量量化版本與社群實測，llama.cpp 對 Qwen 的支援成熟度名列前茅",{"type":611,"tag":655,"props":2375,"children":2376},{"id":1005},[2377],{"type":616,"value":1005},{"type":611,"tag":612,"props":2379,"children":2380},{},[2381],{"type":616,"value":2382},"Qwen3.6-35B-A3B 以 Apache 2.0 授權開源，本地部署零授權費。阿里巴巴同步提供 Qwen API 雲端服務（按 token 計費），形成「本地試用—雲端生產」的雙軌路徑，降低開發者評估門檻。",{"type":611,"tag":655,"props":2384,"children":2385},{"id":1015},[2386],{"type":616,"value":1015},{"type":611,"tag":900,"props":2388,"children":2389},{},[2390,2395,2400],{"type":611,"tag":874,"props":2391,"children":2392},{},[2393],{"type":616,"value":2394},"雙 GPU 機器的硬體採購與維護成本對中小企業仍有一定門檻",{"type":611,"tag":874,"props":2396,"children":2397},{},[2398],{"type":616,"value":2399},"量化格式選擇 (Q4_K_XL vs NVFP4) 需要具備評估能力的技術人力",{"type":611,"tag":874,"props":2401,"children":2402},{},[2403],{"type":616,"value":2404},"無 NVLink 的雙 4060 Ti 方案在企業 IT 標準採購流程中屬非典型配置",{"type":611,"tag":655,"props":2406,"children":2407},{"id":1038},[2408],{"type":616,"value":1038},{"type":611,"tag":900,"props":2410,"children":2411},{},[2412,2417,2422],{"type":611,"tag":874,"props":2413,"children":2414},{},[2415],{"type":616,"value":2416},"消費級多卡方案普及，可能推動 llama.cpp tensor split 效能進一步最佳化",{"type":611,"tag":874,"props":2418,"children":2419},{},[2420],{"type":616,"value":2421},"本地推論速度提升削弱商業 API 在延遲和成本上的差異化優勢，影響定價談判籌碼",{"type":611,"tag":874,"props":2423,"children":2424},{},[2425],{"type":616,"value":2426},"Sparse MoE 在本地推論的成功，將加速其他廠商在開源 MoE 模型上的競爭投入",{"type":611,"tag":655,"props":2428,"children":2430},{"id":2429},"判決值得部署高性價比生態成熟apache-20",[2431],{"type":616,"value":2432},"判決：值得部署（高性價比、生態成熟、Apache 2.0）",{"type":611,"tag":612,"props":2434,"children":2435},{},[2436],{"type":616,"value":2437},"Qwen3.6-35B-A3B Q4_K_XL 在雙 4060 Ti 上的表現，已達到實用本地推論的速度門檻，且成本低於高階單卡方案。對有本地部署需求、注重性價比的開發者，這是目前 35B 級開源模型中最具競爭力的組合之一。",{"title":323,"searchDepth":618,"depth":618,"links":2439},[],{"data":2441,"body":2442,"excerpt":-1,"toc":2578},{"title":323,"description":323},{"type":608,"children":2443},[2444,2449,2492,2498,2521,2526,2549,2555],{"type":611,"tag":655,"props":2445,"children":2447},{"id":2446},"主要實測數據",[2448],{"type":616,"value":2446},{"type":611,"tag":900,"props":2450,"children":2451},{},[2452,2462,2472,2482],{"type":611,"tag":874,"props":2453,"children":2454},{},[2455,2460],{"type":611,"tag":674,"props":2456,"children":2457},{},[2458],{"type":616,"value":2459},"平台",{"type":616,"value":2461},"：雙 RTX 4060 Ti 16GB（共 32GB VRAM），PCIe 分散推論",{"type":611,"tag":874,"props":2463,"children":2464},{},[2465,2470],{"type":611,"tag":674,"props":2466,"children":2467},{},[2468],{"type":616,"value":2469},"模型",{"type":616,"value":2471},"：Qwen3.6-35B-A3B Q4_K_XL",{"type":611,"tag":874,"props":2473,"children":2474},{},[2475,2480],{"type":611,"tag":674,"props":2476,"children":2477},{},[2478],{"type":616,"value":2479},"生成速度",{"type":616,"value":2481},"：125 tok/s",{"type":611,"tag":874,"props":2483,"children":2484},{},[2485,2490],{"type":611,"tag":674,"props":2486,"children":2487},{},[2488],{"type":616,"value":2489},"成本比較",{"type":616,"value":2491},"：雙 4060 Ti 約為單張 4090 的 60–70% 市場價",{"type":611,"tag":655,"props":2493,"children":2495},{"id":2494},"架構加速參考llamacpp-build-b8967僅適用-blackwell-sm_120",[2496],{"type":616,"value":2497},"架構加速參考（llama.cpp build b8967，僅適用 Blackwell sm_120）",{"type":611,"tag":900,"props":2499,"children":2500},{},[2501,2511],{"type":611,"tag":874,"props":2502,"children":2503},{},[2504,2509],{"type":611,"tag":674,"props":2505,"children":2506},{},[2507],{"type":616,"value":2508},"prefill 提升",{"type":616,"value":2510},"：43–68%（Blackwell 架構，FP4 tensor core 原生路徑）",{"type":611,"tag":874,"props":2512,"children":2513},{},[2514,2519],{"type":611,"tag":674,"props":2515,"children":2516},{},[2517],{"type":616,"value":2518},"Ada Lovelace(sm_89) 提升",{"type":616,"value":2520},"：0%（無 FP4 tensor core，僅記憶體節省）",{"type":611,"tag":655,"props":2522,"children":2524},{"id":2523},"記憶體頻寬對比",[2525],{"type":616,"value":2523},{"type":611,"tag":900,"props":2527,"children":2528},{},[2529,2539],{"type":611,"tag":874,"props":2530,"children":2531},{},[2532,2537],{"type":611,"tag":674,"props":2533,"children":2534},{},[2535],{"type":616,"value":2536},"RTX 4060 Ti",{"type":616,"value":2538},"：128-bit 匯流排，288 GB/s",{"type":611,"tag":874,"props":2540,"children":2541},{},[2542,2547],{"type":611,"tag":674,"props":2543,"children":2544},{},[2545],{"type":616,"value":2546},"RTX 4090",{"type":616,"value":2548},"：384-bit 匯流排，1,008 GB/s（約為 4060 Ti 的 3.5 倍）",{"type":611,"tag":655,"props":2550,"children":2552},{"id":2551},"swe-bench-verified-參考對比",[2553],{"type":616,"value":2554},"SWE-Bench Verified 參考對比",{"type":611,"tag":900,"props":2556,"children":2557},{},[2558,2568],{"type":611,"tag":874,"props":2559,"children":2560},{},[2561,2566],{"type":611,"tag":674,"props":2562,"children":2563},{},[2564],{"type":616,"value":2565},"Opus 4.7",{"type":616,"value":2567},"：87.6%（模型約 5T 參數）",{"type":611,"tag":874,"props":2569,"children":2570},{},[2571,2576],{"type":611,"tag":674,"props":2572,"children":2573},{},[2574],{"type":616,"value":2575},"Qwen3.6-35B-A3B",{"type":616,"value":2577},"：73.4%（推論活躍參數 3B，本地免費執行，無速率限制）",{"title":323,"searchDepth":618,"depth":618,"links":2579},[],{"data":2581,"body":2582,"excerpt":-1,"toc":2599},{"title":323,"description":323},{"type":608,"children":2583},[2584],{"type":611,"tag":900,"props":2585,"children":2586},{},[2587,2591,2595],{"type":611,"tag":874,"props":2588,"children":2589},{},[2590],{"type":616,"value":266},{"type":611,"tag":874,"props":2592,"children":2593},{},[2594],{"type":616,"value":267},{"type":611,"tag":874,"props":2596,"children":2597},{},[2598],{"type":616,"value":268},{"title":323,"searchDepth":618,"depth":618,"links":2600},[],{"data":2602,"body":2603,"excerpt":-1,"toc":2620},{"title":323,"description":323},{"type":608,"children":2604},[2605],{"type":611,"tag":900,"props":2606,"children":2607},{},[2608,2612,2616],{"type":611,"tag":874,"props":2609,"children":2610},{},[2611],{"type":616,"value":270},{"type":611,"tag":874,"props":2613,"children":2614},{},[2615],{"type":616,"value":271},{"type":611,"tag":874,"props":2617,"children":2618},{},[2619],{"type":616,"value":272},{"title":323,"searchDepth":618,"depth":618,"links":2621},[],{"data":2623,"body":2624,"excerpt":-1,"toc":2630},{"title":323,"description":276},{"type":608,"children":2625},[2626],{"type":611,"tag":612,"props":2627,"children":2628},{},[2629],{"type":616,"value":276},{"title":323,"searchDepth":618,"depth":618,"links":2631},[],{"data":2633,"body":2634,"excerpt":-1,"toc":2640},{"title":323,"description":277},{"type":608,"children":2635},[2636],{"type":611,"tag":612,"props":2637,"children":2638},{},[2639],{"type":616,"value":277},{"title":323,"searchDepth":618,"depth":618,"links":2641},[],{"data":2643,"body":2644,"excerpt":-1,"toc":2650},{"title":323,"description":278},{"type":608,"children":2645},[2646],{"type":611,"tag":612,"props":2647,"children":2648},{},[2649],{"type":616,"value":278},{"title":323,"searchDepth":618,"depth":618,"links":2651},[],{"data":2653,"body":2654,"excerpt":-1,"toc":2727},{"title":323,"description":323},{"type":608,"children":2655},[2656,2661,2694,2709,2715],{"type":611,"tag":655,"props":2657,"children":2659},{"id":2658},"投資規模與時程",[2660],{"type":616,"value":2658},{"type":611,"tag":612,"props":2662,"children":2663},{},[2664,2666,2671,2673,2678,2680,2685,2687,2692],{"type":616,"value":2665},"SoftBank 於 2026 年 5 月 30 日在法國「選擇法國」峰會宣布，將投資最高 ",{"type":611,"tag":674,"props":2667,"children":2668},{},[2669],{"type":616,"value":2670},"750 億歐元",{"type":616,"value":2672},"（約 870 億美元）在法國建設 AI 資料中心，稱為「歐洲最大 AI 基礎設施投資」。第一階段承諾投入 ",{"type":611,"tag":674,"props":2674,"children":2675},{},[2676],{"type":616,"value":2677},"450 億歐元",{"type":616,"value":2679},"，目標建置 ",{"type":611,"tag":674,"props":2681,"children":2682},{},[2683],{"type":616,"value":2684},"3.1 吉瓦 (GW)",{"type":616,"value":2686}," 容量，預計 2031 年完成；首座 2028 年啟用，最終目標 ",{"type":611,"tag":674,"props":2688,"children":2689},{},[2690],{"type":616,"value":2691},"5 吉瓦",{"type":616,"value":2693},"。",{"type":611,"tag":667,"props":2695,"children":2696},{},[2697],{"type":611,"tag":612,"props":2698,"children":2699},{},[2700,2704,2707],{"type":611,"tag":674,"props":2701,"children":2702},{},[2703],{"type":616,"value":678},{"type":611,"tag":680,"props":2705,"children":2706},{},[],{"type":616,"value":2708},"\n吉瓦 (GW) ：10 億瓦特，此處指資料中心總電力容量；3.1 GW 約相當於一座大型核電廠的輸出規模。",{"type":611,"tag":655,"props":2710,"children":2712},{"id":2711},"選址優勢清潔能源牌",[2713],{"type":616,"value":2714},"選址優勢：清潔能源牌",{"type":611,"tag":612,"props":2716,"children":2717},{},[2718,2720,2725],{"type":616,"value":2719},"三個選址均位於法國北部大區 (Hauts-de-France) ：敦克爾克 (Loon-Plage) 、Bosquel 及 Bouchain。SoftBank 特別強調法國 ",{"type":611,"tag":674,"props":2721,"children":2722},{},[2723],{"type":616,"value":2724},"95% 去碳化電力",{"type":616,"value":2726},"的優勢，與其美國俄亥俄州計畫依賴天然氣電廠的現況形成對比，顯示清潔能源供給已成 AI 基礎設施跨國選址的關鍵籌碼。",{"title":323,"searchDepth":618,"depth":618,"links":2728},[],{"data":2730,"body":2731,"excerpt":-1,"toc":2737},{"title":323,"description":319},{"type":608,"children":2732},[2733],{"type":611,"tag":612,"props":2734,"children":2735},{},[2736],{"type":616,"value":319},{"title":323,"searchDepth":618,"depth":618,"links":2738},[],{"data":2740,"body":2741,"excerpt":-1,"toc":2747},{"title":323,"description":320},{"type":608,"children":2742},[2743],{"type":611,"tag":612,"props":2744,"children":2745},{},[2746],{"type":616,"value":320},{"title":323,"searchDepth":618,"depth":618,"links":2748},[],{"data":2750,"body":2751,"excerpt":-1,"toc":2837},{"title":323,"description":323},{"type":608,"children":2752},[2753,2759,2781,2786,2817,2832],{"type":611,"tag":655,"props":2754,"children":2756},{"id":2755},"攻擊手法llmshare",[2757],{"type":616,"value":2758},"攻擊手法：LLMShare",{"type":611,"tag":612,"props":2760,"children":2761},{},[2762,2764,2771,2773,2779],{"type":616,"value":2763},"資安機構 Push Security 將此類手法命名為「LLMShare」——攻擊者利用 ChatGPT(",{"type":611,"tag":2765,"props":2766,"children":2768},"code",{"className":2767},[],[2769],{"type":616,"value":2770},"chatgpt.com/s/",{"type":616,"value":2772},") 與 Claude(",{"type":611,"tag":2765,"props":2774,"children":2776},{"className":2775},[],[2777],{"type":616,"value":2778},"claude.ai/share/",{"type":616,"value":2780},") 的正式分享連結散布惡意程式。由於連結托管於 OpenAI 與 Anthropic 的正式域名，安全過濾工具難以識別，用戶信任度也明顯較高，攻擊模式已擴展至 Grok，並有搭配 Google 廣告的版本。",{"type":611,"tag":655,"props":2782,"children":2784},{"id":2783},"兩條主要攻擊路徑",[2785],{"type":616,"value":2783},{"type":611,"tag":900,"props":2787,"children":2788},{},[2789,2807],{"type":611,"tag":874,"props":2790,"children":2791},{},[2792,2797,2799,2805],{"type":611,"tag":674,"props":2793,"children":2794},{},[2795],{"type":616,"value":2796},"ChatGPT 路徑",{"type":616,"value":2798},"：偽造「服務中斷」頁面，誘導用戶前往惡意域名 ",{"type":611,"tag":2765,"props":2800,"children":2802},{"className":2801},[],[2803],{"type":616,"value":2804},"openew[.]app",{"type":616,"value":2806}," 下載受感染安裝包，且該站點對掃描工具顯示無害內容 (cloaking) 。",{"type":611,"tag":874,"props":2808,"children":2809},{},[2810,2815],{"type":611,"tag":674,"props":2811,"children":2812},{},[2813],{"type":616,"value":2814},"Claude 路徑",{"type":616,"value":2816},"：惡意對話偽裝為「Apple Support」安裝指南，要求用戶開啟 Terminal 並貼上 base64 編碼命令，以 polymorphic delivery 技術在記憶體中執行，規避簽名偵測，最終植入 MacSync 竊取程式，竊取瀏覽器憑證、Cookies 及 macOS Keychain 內容。",{"type":611,"tag":667,"props":2818,"children":2819},{},[2820],{"type":611,"tag":612,"props":2821,"children":2822},{},[2823,2827,2830],{"type":611,"tag":674,"props":2824,"children":2825},{},[2826],{"type":616,"value":678},{"type":611,"tag":680,"props":2828,"children":2829},{},[],{"type":616,"value":2831},"\nPolymorphic delivery：每次執行時自動變形程式碼，使特徵值不斷改變，讓傳統防毒軟體難以依靠固定特徵識別。",{"type":611,"tag":612,"props":2833,"children":2834},{},[2835],{"type":616,"value":2836},"GitHub 上另有假安裝程式搭載 Deno RAT，鎖定 50+ 種加密貨幣錢包擴充套件，透過 Chrome DevTools Protocol 竊取螢幕影像，相關推廣影片累積觀看逾 5 萬次。",{"title":323,"searchDepth":618,"depth":618,"links":2838},[],{"data":2840,"body":2842,"excerpt":-1,"toc":2884},{"title":323,"description":2841},"惡意流量來自受信任的 AI 服務正式域名，傳統 URL 過濾與域名黑名單已完全失效。工程師應更新端點防護規則：",{"type":608,"children":2843},[2844,2848,2879],{"type":611,"tag":612,"props":2845,"children":2846},{},[2847],{"type":616,"value":2841},{"type":611,"tag":900,"props":2849,"children":2850},{},[2851,2856,2861],{"type":611,"tag":874,"props":2852,"children":2853},{},[2854],{"type":616,"value":2855},"加入 base64 命令執行的行為偵測規則",{"type":611,"tag":874,"props":2857,"children":2858},{},[2859],{"type":616,"value":2860},"監控從 AI 分享頁面觸發的 Terminal 指令",{"type":611,"tag":874,"props":2862,"children":2863},{},[2864,2866,2871,2873],{"type":616,"value":2865},"封鎖已知 IoC：",{"type":611,"tag":2765,"props":2867,"children":2869},{"className":2868},[],[2870],{"type":616,"value":2804},{"type":616,"value":2872},"、SHA256 ",{"type":611,"tag":2765,"props":2874,"children":2876},{"className":2875},[],[2877],{"type":616,"value":2878},"de8c50e8...ec2dde78",{"type":611,"tag":612,"props":2880,"children":2881},{},[2882],{"type":616,"value":2883},"macOS Keychain 與瀏覽器憑證為主要目標，應列入安全稽核優先項目；同時需重新評估企業 AI 工具存取政策。",{"title":323,"searchDepth":618,"depth":618,"links":2885},[],{"data":2887,"body":2889,"excerpt":-1,"toc":2900},{"title":323,"description":2888},"攻擊刻意鎖定非技術用戶——對 AI 感到好奇的員工也可能點入偽裝成官方安裝指南的惡意對話。由於連結域名合法，傳統資安意識培訓（「不點陌生連結」）幾乎失去效果。",{"type":608,"children":2890},[2891,2895],{"type":611,"tag":612,"props":2892,"children":2893},{},[2894],{"type":616,"value":2888},{"type":611,"tag":612,"props":2896,"children":2897},{},[2898],{"type":616,"value":2899},"企業應評估是否禁止員工透過個人裝置存取 AI 共享連結、是否要求 AI 工具安裝走 IT 核准流程。MacSync 竊取程式可竊取企業 SSO Cookies，一旦成功可能引發更廣泛的帳號接管事件。",{"title":323,"searchDepth":618,"depth":618,"links":2901},[],{"data":2903,"body":2904,"excerpt":-1,"toc":2947},{"title":323,"description":323},{"type":608,"children":2905},[2906,2911,2916,2931,2937,2942],{"type":611,"tag":655,"props":2907,"children":2909},{"id":2908},"計費模式大翻轉",[2910],{"type":616,"value":2908},{"type":611,"tag":612,"props":2912,"children":2913},{},[2914],{"type":616,"value":2915},"2026 年 6 月 1 日起，GitHub Copilot 從「固定月費 + 進階請求次數」切換為「Token 用量計費」。訂閱費用本身不變（Pro $10／月、Business $19／用戶／月、Enterprise $39／用戶／月），但每月額度改為等值 GitHub AI Credits，input、output 與 cached tokens 皆依各模型 API 定價扣抵。",{"type":611,"tag":667,"props":2917,"children":2918},{},[2919],{"type":611,"tag":612,"props":2920,"children":2921},{},[2922,2926,2929],{"type":611,"tag":674,"props":2923,"children":2924},{},[2925],{"type":616,"value":678},{"type":611,"tag":680,"props":2927,"children":2928},{},[],{"type":616,"value":2930},"\nGitHub AI Credits 是 Copilot 的新計量單位，每筆對話依實際 token 消耗量計費，類似電話帳單從「包月通話」改為「依分鐘計費」。",{"type":611,"tag":655,"props":2932,"children":2934},{"id":2933},"問題核心agentic-session-成本爆炸",[2935],{"type":616,"value":2936},"問題核心：Agentic Session 成本爆炸",{"type":611,"tag":612,"props":2938,"children":2939},{},[2940],{"type":616,"value":2941},"關鍵矛盾在於 agentic coding session——Copilot 自主規劃、研究並執行多步驟任務時，單次 session 可消耗 $30–$40 的 Credits。",{"type":611,"tag":612,"props":2943,"children":2944},{},[2945],{"type":616,"value":2946},"Business 方案每月僅提供 $30 額度（促銷至 2026 年 8 月），意味著一次 agentic session 就可能耗光整月配額。社群截圖顯示帳單從每月 $29 飆至 $750，乃至 $39 方案用量換算後達 $5,851.77。官方公告帖在短時間內累積逾 400 則留言、近 900 個倒讚。",{"title":323,"searchDepth":618,"depth":618,"links":2948},[],{"data":2950,"body":2952,"excerpt":-1,"toc":2981},{"title":323,"description":2951},"Token 計費等同每次 prompt 後面掛了一張帳單，agentic workflow 用量難以預測。建議：",{"type":608,"children":2953},[2954,2958,2976],{"type":611,"tag":612,"props":2955,"children":2956},{},[2957],{"type":616,"value":2951},{"type":611,"tag":870,"props":2959,"children":2960},{},[2961,2966,2971],{"type":611,"tag":874,"props":2962,"children":2963},{},[2964],{"type":616,"value":2965},"嚴格限制 autonomous coding session，改用明確指令的單步提問",{"type":611,"tag":874,"props":2967,"children":2968},{},[2969],{"type":616,"value":2970},"縮小 context window，避免重複傳遞大型 codebase",{"type":611,"tag":874,"props":2972,"children":2973},{},[2974],{"type":616,"value":2975},"評估替代方案（Claude Code API、OpenAI Codex）的 token 成本透明度",{"type":611,"tag":612,"props":2977,"children":2978},{},[2979],{"type":616,"value":2980},"短期最直接的應對是計算自己的典型 session 消耗，再對比新方案額度。",{"title":323,"searchDepth":618,"depth":618,"links":2982},[],{"data":2984,"body":2986,"excerpt":-1,"toc":3015},{"title":323,"description":2985},"多家企業已估算成本將增加 4 倍以上，而 Enterprise 每月僅 $70 Credits 遠不敷重度 agentic 使用。",{"type":608,"children":2987},[2988,2992,2997],{"type":611,"tag":612,"props":2989,"children":2990},{},[2991],{"type":616,"value":2985},{"type":611,"tag":612,"props":2993,"children":2994},{},[2995],{"type":616,"value":2996},"Microsoft 改版背後是補貼時代的終結——舊定額方案長期虧損。企業現在需要評估：",{"type":611,"tag":870,"props":2998,"children":2999},{},[3000,3005,3010],{"type":611,"tag":874,"props":3001,"children":3002},{},[3003],{"type":616,"value":3004},"是否繼續採購 Copilot，或轉向按需計費更透明的工具",{"type":611,"tag":874,"props":3006,"children":3007},{},[3008],{"type":616,"value":3009},"限制 agentic session 使用範圍，避免帳單失控",{"type":611,"tag":874,"props":3011,"children":3012},{},[3013],{"type":616,"value":3014},"觀察 Microsoft 是否在社群壓力下調整額度，再作長期決策",{"title":323,"searchDepth":618,"depth":618,"links":3016},[],{"data":3018,"body":3020,"excerpt":-1,"toc":3062},{"title":323,"description":3019},"此報導源自 2026 年 3 月的 IPAM 研討會及同月 arXiv 預印本，近期因學術社群廣泛引用而重新引發熱議。",{"type":608,"children":3021},[3022,3026,3032,3037,3042,3047],{"type":611,"tag":612,"props":3023,"children":3024},{},[3025],{"type":616,"value":3019},{"type":611,"tag":655,"props":3027,"children":3029},{"id":3028},"ai-打破數學研究的孤島結構",[3030],{"type":616,"value":3031},"AI 打破數學研究的孤島結構",{"type":611,"tag":612,"props":3033,"children":3034},{},[3035],{"type":616,"value":3036},"菲爾茲獎得主陶哲軒 (Terence Tao) 宣告，AI 已「準備好進入黃金時代」。他指出，數學研究史上從未有分工——從問題定義到論文發表，向來由同一人獨力完成。AI 有潛力打破此孤島，催生「工業數學」：大型 AI 輔助團隊同步追求更廣泛議題，縮減個別深度、擴大整體覆蓋。",{"type":611,"tag":655,"props":3038,"children":3040},{"id":3039},"驗證才是成敗關鍵",[3041],{"type":616,"value":3039},{"type":611,"tag":612,"props":3043,"children":3044},{},[3045],{"type":616,"value":3046},"陶哲軒警告，有效運用 AI 的程度與驗證嚴謹度成正比，否則只會堆積未測試的想法。他提出「數學嗅覺」概念——資深數學家能在逐行驗證前直覺判斷證明可信度。形式驗證工具（如 Lean）是防止邏輯脆弱論證偷渡的關鍵防線。",{"type":611,"tag":667,"props":3048,"children":3049},{},[3050],{"type":611,"tag":612,"props":3051,"children":3052},{},[3053,3057,3060],{"type":611,"tag":674,"props":3054,"children":3055},{},[3056],{"type":616,"value":678},{"type":611,"tag":680,"props":3058,"children":3059},{},[],{"type":616,"value":3061},"\n形式驗證：以數學方式逐步確認每個推理步驟正確；Lean 是數學社群主流的形式驗證語言。",{"title":323,"searchDepth":618,"depth":618,"links":3063},[],{"data":3065,"body":3067,"excerpt":-1,"toc":3078},{"title":323,"description":3066},"Tao 的框架為工具選用提供清晰指引：形式驗證能力比單純生成流暢度更具長期價值。",{"type":608,"children":3068},[3069,3073],{"type":611,"tag":612,"props":3070,"children":3071},{},[3072],{"type":616,"value":3066},{"type":611,"tag":612,"props":3074,"children":3075},{},[3076],{"type":616,"value":3077},"目前實際可用的場景：文獻搜尋（數週壓縮至數分鐘）、候選程式碼生成、可行性探索。但「選對問題」與驗證結果仍是人類不可外包的核心任務。若所在機構有嚴謹的驗證流程，現在是整合 AI 輔助工具的合適時機。",{"title":323,"searchDepth":618,"depth":618,"links":3079},[],{"data":3081,"body":3083,"excerpt":-1,"toc":3094},{"title":323,"description":3082},"陶哲軒的「工業數學」願景預示研究機構架構轉變：從明星研究員單打獨鬥，轉向以 AI 為中介的大型協作團隊。",{"type":608,"children":3084},[3085,3089],{"type":611,"tag":612,"props":3086,"children":3087},{},[3088],{"type":616,"value":3082},{"type":611,"tag":612,"props":3090,"children":3091},{},[3092],{"type":616,"value":3093},"對 AI 工具廠商而言，學術市場將更重視嚴謹驗證能力，而非流暢生成；能整合形式驗證的平台將獲得競爭優勢。菲爾茲獎得主公開背書，亦將加速其他學術機構跟進採用。",{"title":323,"searchDepth":618,"depth":618,"links":3095},[],{"data":3097,"body":3098,"excerpt":-1,"toc":3150},{"title":323,"description":323},{"type":608,"children":3099},[3100,3105,3110,3115,3120,3135,3140,3145],{"type":611,"tag":655,"props":3101,"children":3103},{"id":3102},"吊墜計畫與三大策略支柱",[3104],{"type":616,"value":3102},{"type":611,"tag":612,"props":3106,"children":3107},{},[3108],{"type":616,"value":3109},"Meta 正秘密開發一款可夾附衣物或掛頸佩戴的 AI 吊墜，由穿戴式裝置副總裁 Alex Himel 的內部備忘錄確認。",{"type":611,"tag":612,"props":3111,"children":3112},{},[3113],{"type":616,"value":3114},"吊墜技術來自 Meta 2025 年底收購的新創 Limitless，後者原售 99 美元錄音穿戴裝置，背後投資人包含 Sam Altman 與 a16z。收購後 Limitless 停售原有產品，技術直接納入 Meta 路線圖。",{"type":611,"tag":612,"props":3116,"children":3117},{},[3118],{"type":616,"value":3119},"備忘錄同時揭露另外兩大策略支柱：搭載持續攝影機的超感知眼鏡，以及企業訂閱服務「Wearables for Work」。",{"type":611,"tag":667,"props":3121,"children":3122},{},[3123],{"type":611,"tag":612,"props":3124,"children":3125},{},[3126,3130,3133],{"type":611,"tag":674,"props":3127,"children":3128},{},[3129],{"type":616,"value":678},{"type":611,"tag":680,"props":3131,"children":3132},{},[],{"type":616,"value":3134},"\n超感知眼鏡 (supersensing glasses) ：配備持續運作攝影機與多元感測器的智慧眼鏡，可即時追蹤日常活動並提供情境提醒。",{"type":611,"tag":655,"props":3136,"children":3138},{"id":3137},"技術規格與商業目標",[3139],{"type":616,"value":3137},{"type":611,"tag":612,"props":3141,"children":3142},{},[3143],{"type":616,"value":3144},"所有裝置由 Meta 最新 AI 模型 Muse Spark 驅動，並整合尚未發布的 AI agent「Hatch」。訂閱制分兩層：Meta One Plus（$7.99／月）與 Meta One Premium（$19.99／月）。",{"type":611,"tag":612,"props":3146,"children":3147},{},[3148],{"type":616,"value":3149},"內部狗糧測試預計 2027 年春季啟動；2026 年下半年整體穿戴裝置銷售目標為 1,000 萬台。",{"title":323,"searchDepth":618,"depth":618,"links":3151},[],{"data":3153,"body":3155,"excerpt":-1,"toc":3166},{"title":323,"description":3154},"Muse Spark 與 Hatch agent 的整合架構尚未公開，但持續錄音穿戴裝置對推論效能與隱私架構提出雙重挑戰。",{"type":608,"children":3156},[3157,3161],{"type":611,"tag":612,"props":3158,"children":3159},{},[3160],{"type":616,"value":3154},{"type":611,"tag":612,"props":3162,"children":3163},{},[3164],{"type":616,"value":3165},"邊緣運算能力將決定是否需要持續上傳音訊串流——若採雲端處理，隱私保護架構須在設計初期鎖定。Limitless 已有成熟的對話錄製與摘要管線，Meta 需決定是沿用或全面整合進自家 AI 堆疊。開發者平台開放後，第三方穿戴式 AI 應用將成為新興整合場景。",{"title":323,"searchDepth":618,"depth":618,"links":3167},[],{"data":3169,"body":3171,"excerpt":-1,"toc":3182},{"title":323,"description":3170},"Reality Labs 2026 年 Q1 虧損達 40 億美元，此次硬體多元佈局是降低財務壓力的關鍵賭注。",{"type":608,"children":3172},[3173,3177],{"type":611,"tag":612,"props":3174,"children":3175},{},[3176],{"type":616,"value":3170},{"type":611,"tag":612,"props":3178,"children":3179},{},[3180],{"type":616,"value":3181},"Meta 透過收購 Limitless 直接取得已驗證的市場需求與用戶基礎，比從零開發更節省試錯成本。企業訂閱制若能轉換現有 700 萬眼鏡用戶，將為 Reality Labs 創造穩定的經常性收入。此舉同時對 Humane、Rabbit 等 AI 穿戴新創造成直接競爭壓力。",{"title":323,"searchDepth":618,"depth":618,"links":3183},[],{"data":3185,"body":3186,"excerpt":-1,"toc":3208},{"title":323,"description":323},{"type":608,"children":3187},[3188,3193,3198,3203],{"type":611,"tag":655,"props":3189,"children":3191},{"id":3190},"融資概況與投資陣容",[3192],{"type":616,"value":3190},{"type":611,"tag":612,"props":3194,"children":3195},{},[3196],{"type":616,"value":3197},"OpenRouter 於 2026 年 5 月 28 日完成 1.13 億美元 B 輪融資，估值達 13 億美元，較 11 個月前 A 輪（5.47 億美元）翻逾一倍。本輪由 CapitalG（Alphabet 旗下獨立成長基金）領投，戰略投資方涵蓋 NVentures（NVIDIA 創投）、Snowflake Ventures、Databricks Ventures 及 MongoDB Ventures；原有股東 a16z 與 Menlo Ventures 跟投。",{"type":611,"tag":655,"props":3199,"children":3201},{"id":3200},"規模與核心能力",[3202],{"type":616,"value":3200},{"type":611,"tag":612,"props":3204,"children":3205},{},[3206],{"type":616,"value":3207},"OpenRouter 連結 800 萬以上開發者與 400 個以上模型，過去六個月週處理量從 5 兆 tokens 成長至 25 兆 tokens（5 倍成長），全年預計突破千兆 (1 quadrillion)tokens。平台核心定位為「intelligent routing」——提供 provider failover、延遲最佳化、guardrails 及零資料保留 (zero-data-retention) 政策，協助企業從單一模型 pilot 過渡至多模型生產環境。",{"title":323,"searchDepth":618,"depth":618,"links":3209},[],{"data":3211,"body":3213,"excerpt":-1,"toc":3224},{"title":323,"description":3212},"OpenRouter 路由層解決多模型環境三個痛點：provider failover 降低單點故障、延遲最佳化讓模型選擇動態化、guardrails 提供合規管控。",{"type":608,"children":3214},[3215,3219],{"type":611,"tag":612,"props":3216,"children":3217},{},[3218],{"type":616,"value":3212},{"type":611,"tag":612,"props":3220,"children":3221},{},[3222],{"type":616,"value":3223},"然而社群指出關鍵問題：開源模型可能被路由至未明確標示量化程度的供應商，讓工程師誤以為使用完整模型，實際跑的卻是 4B 或 8B 量化縮減版。生產環境引入前，應確認供應商透明度或指定路由至可信供應商。",{"title":323,"searchDepth":618,"depth":618,"links":3225},[],{"data":3227,"body":3229,"excerpt":-1,"toc":3240},{"title":323,"description":3228},"CapitalG、NVentures 與 Snowflake、Databricks 同時入股，暗示 LLM 路由正成為 AI 基礎設施標準層。年度收入超過 5,000 萬美元，商業模式已初步驗證。",{"type":608,"children":3230},[3231,3235],{"type":611,"tag":612,"props":3232,"children":3233},{},[3234],{"type":616,"value":3228},{"type":611,"tag":612,"props":3236,"children":3237},{},[3238],{"type":616,"value":3239},"長期護城河仍存疑：若 LLM 市場整合至少數主流模型，路由溢價難以持續說服大客戶；各大雲端平台的原生路由服務是潛在競爭威脅。",{"title":323,"searchDepth":618,"depth":618,"links":3241},[],{"data":3243,"body":3244,"excerpt":-1,"toc":3311},{"title":323,"description":323},{"type":608,"children":3245},[3246,3252,3257,3272,3278,3283,3306],{"type":611,"tag":655,"props":3247,"children":3249},{"id":3248},"_231-人天-13-日曆天",[3250],{"type":616,"value":3251},"231 人天 → 13 日曆天",{"type":611,"tag":612,"props":3253,"children":3254},{},[3255],{"type":616,"value":3256},"Salesforce 工程負責人 Srinivas Tallapragada 於 2026 年 5 月 30 日發表文章，披露一個遷移案例：將 33 個 API endpoint 遷移至雲原生架構，原估 231 人天，以 Agentic workflow 只花 13 個日曆天完成——快了約 18 倍。",{"type":611,"tag":667,"props":3258,"children":3259},{},[3260],{"type":611,"tag":612,"props":3261,"children":3262},{},[3263,3267,3270],{"type":611,"tag":674,"props":3264,"children":3265},{},[3266],{"type":616,"value":678},{"type":611,"tag":680,"props":3268,"children":3269},{},[],{"type":616,"value":3271},"\n231「人天」是多人協作的總工作量估算，與日曆天不同；13 天是實際掛鐘時間。此數據來自 Salesforce 官方，尚未經第三方獨立驗證。",{"type":611,"tag":655,"props":3273,"children":3275},{"id":3274},"全公司量化績效2026-年-4-月-vs-2025-年-4-月",[3276],{"type":616,"value":3277},"全公司量化績效（2026 年 4 月 vs 2025 年 4 月）",{"type":611,"tag":612,"props":3279,"children":3280},{},[3281],{"type":616,"value":3282},"Salesforce 已將整個工程組織切換至 Anthropic Claude Code，取消 token 限制，並自建「Claude Code skills」模組封裝團隊 context 與工作流程：",{"type":611,"tag":900,"props":3284,"children":3285},{},[3286,3291,3296,3301],{"type":611,"tag":874,"props":3287,"children":3288},{},[3289],{"type":616,"value":3290},"每位開發者合併 PR 數：+79%",{"type":611,"tag":874,"props":3292,"children":3293},{},[3294],{"type":616,"value":3295},"每位開發者完成工作項目：+50.8%",{"type":611,"tag":874,"props":3297,"children":3298},{},[3299],{"type":616,"value":3300},"ML-based Effective Output Score：+151.3%",{"type":611,"tag":874,"props":3302,"children":3303},{},[3304],{"type":616,"value":3305},"系統事故數：-5%",{"type":611,"tag":612,"props":3307,"children":3308},{},[3309],{"type":616,"value":3310},"公司預計 2026 年在 Anthropic token 上花費約 3 億美元。工程師角色從手動編碼轉為「Agentic system 架構師」，負責設計問題結構與可複用模式。",{"title":323,"searchDepth":618,"depth":618,"links":3312},[],{"data":3314,"body":3316,"excerpt":-1,"toc":3327},{"title":323,"description":3315},"Salesforce 的 Agentic 架構核心是 Claude Code + 自建「skills」模組，將團隊 context 封裝成可複用工件。角色轉型重點：從「寫程式」變成「設計委派策略與可複用 patterns」。",{"type":608,"children":3317},[3318,3322],{"type":611,"tag":612,"props":3319,"children":3320},{},[3321],{"type":616,"value":3315},{"type":611,"tag":612,"props":3323,"children":3324},{},[3325],{"type":616,"value":3326},"官方坦承的挑戰同樣值得關注：長時間 session 的 context 管理難題、CLAUDE.md 輸出品質不穩定、Agent 自主執行的安全邊界——大規模部署時皆非小事。",{"title":323,"searchDepth":618,"depth":618,"links":3328},[],{"data":3330,"body":3332,"excerpt":-1,"toc":3343},{"title":323,"description":3331},"Salesforce 與 Anthropic 深度綁定（預計年付 3 億美元 token 費用），是目前企業採用 AI coding 工具最具規模的公開案例。",{"type":608,"children":3333},[3334,3338],{"type":611,"tag":612,"props":3335,"children":3336},{},[3337],{"type":616,"value":3331},{"type":611,"tag":612,"props":3339,"children":3340},{},[3341],{"type":616,"value":3342},"+79% PRs、+151% 效能指標的量化展示，將加速企業主管對 AI coding 工具的採購壓力。但數據為廠商自報，整合複雜度與安全顧慮仍是中小型企業觀望的主因。",{"title":323,"searchDepth":618,"depth":618,"links":3344},[],{"data":3346,"body":3347,"excerpt":-1,"toc":3380},{"title":323,"description":323},{"type":608,"children":3348},[3349,3355],{"type":611,"tag":655,"props":3350,"children":3352},{"id":3351},"工程生產力指標2026-年-4-月-vs-2025-年-4-月",[3353],{"type":616,"value":3354},"工程生產力指標（2026 年 4 月 vs 2025 年 4 月）",{"type":611,"tag":900,"props":3356,"children":3357},{},[3358,3362,3367,3371,3375],{"type":611,"tag":874,"props":3359,"children":3360},{},[3361],{"type":616,"value":3290},{"type":611,"tag":874,"props":3363,"children":3364},{},[3365],{"type":616,"value":3366},"每位開發者完成工作項目數：+50.8%",{"type":611,"tag":874,"props":3368,"children":3369},{},[3370],{"type":616,"value":3300},{"type":611,"tag":874,"props":3372,"children":3373},{},[3374],{"type":616,"value":3305},{"type":611,"tag":874,"props":3376,"children":3377},{},[3378],{"type":616,"value":3379},"遷移案例：231 人天 → 13 日曆天（約 18 倍提速）",{"title":323,"searchDepth":618,"depth":618,"links":3381},[],{"data":3383,"body":3384,"excerpt":-1,"toc":3469},{"title":323,"description":323},{"type":608,"children":3385},[3386,3391,3413,3425,3430,3450],{"type":611,"tag":655,"props":3387,"children":3389},{"id":3388},"專案概覽",[3390],{"type":616,"value":3388},{"type":611,"tag":612,"props":3392,"children":3393},{},[3394,3396,3404,3406,3411],{"type":616,"value":3395},"開源專案 ",{"type":611,"tag":3397,"props":3398,"children":3401},"a",{"href":531,"rel":3399},[3400],"nofollow",[3402],{"type":616,"value":3403},"train-llm-from-scratch",{"type":616,"value":3405}," 以完整的「從零到生成文字」工作流程登上 GitHub Trending，截至 2026-05-31 已累積 ",{"type":611,"tag":674,"props":3407,"children":3408},{},[3409],{"type":616,"value":3410},"2,300 顆星、371 個 Fork",{"type":616,"value":3412},"，MIT 授權。",{"type":611,"tag":612,"props":3414,"children":3415},{},[3416,3418,3423],{"type":616,"value":3417},"80% 內容以 Jupyter Notebook 撰寫，支援從 ",{"type":611,"tag":674,"props":3419,"children":3420},{},[3421],{"type":616,"value":3422},"1,300 萬到 20 億以上參數",{"type":616,"value":3424},"的模型規模，即使資源有限的開發者也能彈性調整 batch size、context length 等超參數進行實驗。",{"type":611,"tag":655,"props":3426,"children":3428},{"id":3427},"訓練架構",[3429],{"type":616,"value":3427},{"type":611,"tag":612,"props":3431,"children":3432},{},[3433,3435,3440,3442,3448],{"type":616,"value":3434},"專案實作《Attention is All You Need》論文的 Transformer 架構，包含多頭注意力、MLP、位置嵌入與 Layer Norm。訓練資料集採用 ",{"type":611,"tag":674,"props":3436,"children":3437},{},[3438],{"type":616,"value":3439},"The Pile",{"type":616,"value":3441},"（825 GB 多元語料），Tokenizer 使用 OpenAI ",{"type":611,"tag":2765,"props":3443,"children":3445},{"className":3444},[],[3446],{"type":616,"value":3447},"r50k_base",{"type":616,"value":3449},"(tiktoken) ，與 GPT-3 相容。",{"type":611,"tag":667,"props":3451,"children":3452},{},[3453],{"type":611,"tag":612,"props":3454,"children":3455},{},[3456,3460,3463,3467],{"type":611,"tag":674,"props":3457,"children":3458},{},[3459],{"type":616,"value":678},{"type":611,"tag":680,"props":3461,"children":3462},{},[],{"type":611,"tag":674,"props":3464,"children":3465},{},[3466],{"type":616,"value":3439},{"type":616,"value":3468}," 是 EleutherAI 發布的 825 GB 開源大規模語料庫，涵蓋網頁、書籍、學術論文等多元來源，是訓練開源 LLM 的常見基準資料集。",{"title":323,"searchDepth":618,"depth":618,"links":3470},[],{"data":3472,"body":3474,"excerpt":-1,"toc":3494},{"title":323,"description":3473},"工作流程明確：clone repo → install requirements → 下載資料 → 前處理 → 設定超參數 → 訓練 → 生成文字，所有步驟在 Notebook 中逐步示範，降低環境設定障礙。",{"type":608,"children":3475},[3476,3489],{"type":611,"tag":612,"props":3477,"children":3478},{},[3479,3481,3487],{"type":616,"value":3480},"工作流程明確：",{"type":611,"tag":2765,"props":3482,"children":3484},{"className":3483},[],[3485],{"type":616,"value":3486},"clone repo → install requirements → 下載資料 → 前處理 → 設定超參數 → 訓練 → 生成文字",{"type":616,"value":3488},"，所有步驟在 Notebook 中逐步示範，降低環境設定障礙。",{"type":611,"tag":612,"props":3490,"children":3491},{},[3492],{"type":616,"value":3493},"13M 參數小模型即可產生語法連貫的文字，適合本機驗證流程；更大規模模型在長序列一致性上明顯提升。整體架構緊貼原版論文，適合想深入理解 LLM 訓練機制的工程師作為學習起點或修改基礎。",{"title":323,"searchDepth":618,"depth":618,"links":3495},[],{"data":3497,"body":3499,"excerpt":-1,"toc":3510},{"title":323,"description":3498},"「可執行教學資源」登上 Trending，反映業界對 LLM 自主研發能力的高需求——企業不再滿足於只呼叫 API，而是希望掌握底層訓練流程。",{"type":608,"children":3500},[3501,3505],{"type":611,"tag":612,"props":3502,"children":3503},{},[3504],{"type":616,"value":3498},{"type":611,"tag":612,"props":3506,"children":3507},{},[3508],{"type":616,"value":3509},"MIT 授權加上 Notebook 格式降低入門門檻，有助於加速工程師從「LLM 使用者」轉型為「LLM 訓練者」，間接降低對外部模型提供商的依賴。對於尋求建立內部 AI 能力的企業，此專案提供了從教學到 PoC 的踏板。",{"title":323,"searchDepth":618,"depth":618,"links":3511},[],{"data":3513,"body":3514,"excerpt":-1,"toc":3553},{"title":323,"description":323},{"type":608,"children":3515},[3516,3522,3527,3542,3548],{"type":611,"tag":655,"props":3517,"children":3519},{"id":3518},"從-copilot-噱頭到真正的-agent-工作流程",[3520],{"type":616,"value":3521},"從 Copilot 噱頭到真正的 Agent 工作流程",{"type":611,"tag":612,"props":3523,"children":3524},{},[3525],{"type":616,"value":3526},"Microsoft 與 Nvidia 聯手宣布「PC 新時代」，核心轉折是放棄依賴雲端的 Copilot 模式，改以 Windows 本地端執行的 AI Agent 框架取代。Copilot+ PC 計畫被媒體直接形容為「基本上失敗了」，此次轉向以 OpenClaw 框架為核心，讓 Agent 可在 PC 本機直接執行工作流程，減少對雲端運算的依賴。",{"type":611,"tag":667,"props":3528,"children":3529},{},[3530],{"type":611,"tag":612,"props":3531,"children":3532},{},[3533,3537,3540],{"type":611,"tag":674,"props":3534,"children":3535},{},[3536],{"type":616,"value":678},{"type":611,"tag":680,"props":3538,"children":3539},{},[],{"type":616,"value":3541},"\nOpenClaw 是微軟自 2026 年初採用的本地 Agent 執行框架，由工程師 Omar Shahine 主導，預計整合進 Microsoft 365。",{"type":611,"tag":655,"props":3543,"children":3545},{"id":3544},"硬體側nvidia-首款-windows-主處理器晶片",[3546],{"type":616,"value":3547},"硬體側：Nvidia 首款 Windows 主處理器晶片",{"type":611,"tag":612,"props":3549,"children":3550},{},[3551],{"type":616,"value":3552},"Nvidia 傳聞代號 N1 與 N1X 的 Arm 架構晶片，將 CPU、GPU 與 AI 加速整合成單一封裝，以「主處理器」而非獨立 GPU 的角色進入 PC 市場。Dell 與 Microsoft Surface 系列將率先搭載，預計於 Computex 台北展及 Microsoft Build 大會正式亮相。",{"title":323,"searchDepth":618,"depth":618,"links":3554},[],{"data":3556,"body":3557,"excerpt":-1,"toc":3563},{"title":323,"description":568},{"type":608,"children":3558},[3559],{"type":611,"tag":612,"props":3560,"children":3561},{},[3562],{"type":616,"value":568},{"title":323,"searchDepth":618,"depth":618,"links":3564},[],{"data":3566,"body":3567,"excerpt":-1,"toc":3573},{"title":323,"description":569},{"type":608,"children":3568},[3569],{"type":611,"tag":612,"props":3570,"children":3571},{},[3572],{"type":616,"value":569},{"title":323,"searchDepth":618,"depth":618,"links":3574},[],{"data":3576,"body":3577,"excerpt":-1,"toc":3664},{"title":323,"description":323},{"type":608,"children":3578},[3579,3584,3589,3594,3599,3604,3609,3614,3619,3624,3629,3634,3639,3644,3649,3654,3659],{"type":611,"tag":655,"props":3580,"children":3582},{"id":3581},"社群熱議排行",[3583],{"type":616,"value":3581},{"type":611,"tag":612,"props":3585,"children":3586},{},[3587],{"type":616,"value":3588},"本日討論熱度最高的四個主題：MCP 協議存廢之爭、Qwen 3.6 消費級推論突破、GitHub Copilot 帳單暴增，以及 SQLite 工作流架構選型。",{"type":611,"tag":612,"props":3590,"children":3591},{},[3592],{"type":616,"value":3593},"GitHub Copilot 計費爭議由 simonw(HN) 引爆——他找到一個 $39 訂閱換算用量計費為 $5,851.77 的實際案例，在社群迅速擴散。",{"type":611,"tag":612,"props":3595,"children":3596},{},[3597],{"type":616,"value":3598},"Qwen 3.6 本地推論話題由 masnick.com（Bluesky，60 likes）帶起熱度，稱週末實測已將大部分 agentic 設定切換至本地模型。",{"type":611,"tag":612,"props":3600,"children":3601},{},[3602],{"type":616,"value":3603},"MCP 已累積每月 9,700 萬次 SDK 下載，torcdotdev.bsky.social（Bluesky，3 upvotes）指出其成長規模，但 HN 多名開發者同步提出根本性質疑。",{"type":611,"tag":655,"props":3605,"children":3607},{"id":3606},"技術爭議與分歧",[3608],{"type":616,"value":3606},{"type":611,"tag":612,"props":3610,"children":3611},{},[3612],{"type":616,"value":3613},"MCP 社群內部對立明顯：ok_dad(HN) 反批評者——「你批評 MCP，卻提不出本質上不同的替代方案，OAuth 加 JSON 就是 MCP」。",{"type":611,"tag":612,"props":3615,"children":3616},{},[3617],{"type":616,"value":3618},"geysersam(HN) 主張 curl 或 python 直存 API 已然足夠；@milvusio(X) 則認為協議本身沒問題，真正痛點是把 50 個工具定義塞進 context。",{"type":611,"tag":612,"props":3620,"children":3621},{},[3622],{"type":616,"value":3623},"本地推論陣營也有分歧：u/jtjstock(Reddit r/LocalLLaMA) 直批「NVFP4 在 llama 上目前很爛」；u/Xp_12 反駁稱問題在量化配方與 sm_120 加速支援不完整，非協議本身。",{"type":611,"tag":655,"props":3625,"children":3627},{"id":3626},"實戰經驗",[3628],{"type":616,"value":3626},{"type":611,"tag":612,"props":3630,"children":3631},{},[3632],{"type":616,"value":3633},"vmbm(HN) 警告最清楚：$10–$200 月費下跑 agentic workflow 的用戶，換用量計費後成本可能暴增 10–100 倍——「用啤酒錢跑幾百個 agent 很爽，但換成遊艇錢就不好玩了」。",{"type":611,"tag":612,"props":3635,"children":3636},{},[3637],{"type":616,"value":3638},"masnick.com（Bluesky，60 likes）實測 Qwen 3.6-35B-A3B 與 Gemma 4 31B 本地部署後得出結論：「本地模型現在真的很厲害。」",{"type":611,"tag":612,"props":3640,"children":3641},{},[3642],{"type":616,"value":3643},"Salesforce 內部案例（廠商自報）稱 Agentic coding 工作流將 231 人天遷移壓縮至 13 曆天；firefoxd(HN) 提醒：「整合相容性問題在 72 小時後才是真正考驗。」",{"type":611,"tag":655,"props":3645,"children":3647},{"id":3646},"未解問題與社群預期",[3648],{"type":616,"value":3646},{"type":611,"tag":612,"props":3650,"children":3651},{},[3652],{"type":616,"value":3653},"aussieguy1234(HN) 點出 OpenRouter 量化透明度缺口：「你以為自己在用完整模型，背後卻是量化版本。」B 輪融資後如何建立供應商品質管控，社群尚無答案。",{"type":611,"tag":612,"props":3655,"children":3656},{},[3657],{"type":616,"value":3658},"MCP 路線圖對「動態工具載入」與 context 最佳化的回應時程未明，「限制工具數量」只是繞路，社群期待官方正面回應。",{"type":611,"tag":612,"props":3660,"children":3661},{},[3662],{"type":616,"value":3663},"Meta AI 吊墜的持續錄音功能引發隱私疑慮，Bluesky 用戶 (46 upvotes) 預測：「執行長將強制員工配戴，儘管我並不樂見。」監管走向懸而未決。",{"title":323,"searchDepth":618,"depth":618,"links":3665},[],{"data":3667,"body":3669,"excerpt":-1,"toc":3690},{"title":323,"description":3668},"2026-05-31 這一天，AI 工具的「真實成本」從抽象概念變成了具體帳單。",{"type":608,"children":3670},[3671,3675,3680,3685],{"type":611,"tag":612,"props":3672,"children":3673},{},[3674],{"type":616,"value":3668},{"type":611,"tag":612,"props":3676,"children":3677},{},[3678],{"type":616,"value":3679},"GitHub Copilot $5,851 案例、OpenRouter 量化透明度爭議、MCP context 爆滿——三個看似獨立的事件，指向同一個社群共識：帳面功能與實際成本之間的落差，正在被迫攤牌。",{"type":611,"tag":612,"props":3681,"children":3682},{},[3683],{"type":616,"value":3684},"Qwen 3.6 在消費級 GPU 的突破、SQLite 工作流架構的逐步成熟，則指向另一個方向：本地化、低依賴、可預測成本的 AI 架構，正在獲得越來越多實戰背書。",{"type":611,"tag":612,"props":3686,"children":3687},{},[3688],{"type":616,"value":3689},"值得持續關注的是 Microsoft Build 大會的本地 Agent API 進度——若成熟度達標，企業 AI 工作流的採購邏輯將迎來一次結構性重組。",{"title":323,"searchDepth":618,"depth":618,"links":3691},[],{"data":3693,"body":3694,"excerpt":-1,"toc":4088},{"title":323,"description":323},{"type":608,"children":3695},[3696,3700,3728,3734,3967,3972,3985,3998,4002,4053,4057,4082],{"type":611,"tag":655,"props":3697,"children":3698},{"id":855},[3699],{"type":616,"value":855},{"type":611,"tag":900,"props":3701,"children":3702},{},[3703,3708,3713,3718,3723],{"type":611,"tag":874,"props":3704,"children":3705},{},[3706],{"type":616,"value":3707},"兩張 RTX 4060 Ti 16GB（VRAM 合計 32GB）",{"type":611,"tag":874,"props":3709,"children":3710},{},[3711],{"type":616,"value":3712},"llama.cpp build b8967+（推薦最新穩定版）",{"type":611,"tag":874,"props":3714,"children":3715},{},[3716],{"type":616,"value":3717},"CUDA 12.4+（Ada Lovelace sm_89 支援）",{"type":611,"tag":874,"props":3719,"children":3720},{},[3721],{"type":616,"value":3722},"磁碟空間：Q4_K_XL 量化版本約 22–24 GB",{"type":611,"tag":874,"props":3724,"children":3725},{},[3726],{"type":616,"value":3727},"主機板需有兩個 PCIe 插槽（建議 x16 + x8 以上，避免 x4 頻寬限制）",{"type":611,"tag":655,"props":3729,"children":3731},{"id":3730},"最小-poc",[3732],{"type":616,"value":3733},"最小 PoC",{"type":611,"tag":3735,"props":3736,"children":3740},"pre",{"className":3737,"code":3738,"language":3739,"meta":323,"style":323},"language-bash shiki shiki-themes vitesse-dark","# 1. 下載模型\nhuggingface-cli download Qwen/Qwen3.6-35B-A3B-GGUF \\\n  --include \"qwen3.6-35b-a3b-q4_k_xl.gguf\" \\\n  --local-dir ./models\n\n# 2. 執行（雙 GPU tensor split）\n./llama-cli \\\n  -m ./models/qwen3.6-35b-a3b-q4_k_xl.gguf \\\n  -ngl 99 \\\n  --tensor-split 1,1 \\\n  --ctx-size 8192 \\\n  -p \"請介紹 Qwen3.6 的架構特色\" \\\n  -n 256\n","bash",[3741],{"type":611,"tag":2765,"props":3742,"children":3743},{"__ignoreMap":323},[3744,3756,3782,3810,3823,3832,3841,3854,3872,3891,3909,3927,3953],{"type":611,"tag":3745,"props":3746,"children":3749},"span",{"class":3747,"line":3748},"line",1,[3750],{"type":611,"tag":3745,"props":3751,"children":3753},{"style":3752},"--shiki-default:#758575DD",[3754],{"type":616,"value":3755},"# 1. 下載模型\n",{"type":611,"tag":3745,"props":3757,"children":3758},{"class":3747,"line":618},[3759,3765,3771,3776],{"type":611,"tag":3745,"props":3760,"children":3762},{"style":3761},"--shiki-default:#80A665",[3763],{"type":616,"value":3764},"huggingface-cli",{"type":611,"tag":3745,"props":3766,"children":3768},{"style":3767},"--shiki-default:#C98A7D",[3769],{"type":616,"value":3770}," download",{"type":611,"tag":3745,"props":3772,"children":3773},{"style":3767},[3774],{"type":616,"value":3775}," Qwen/Qwen3.6-35B-A3B-GGUF",{"type":611,"tag":3745,"props":3777,"children":3779},{"style":3778},"--shiki-default:#C99076",[3780],{"type":616,"value":3781}," \\\n",{"type":611,"tag":3745,"props":3783,"children":3784},{"class":3747,"line":79},[3785,3790,3796,3801,3806],{"type":611,"tag":3745,"props":3786,"children":3787},{"style":3778},[3788],{"type":616,"value":3789},"  --include",{"type":611,"tag":3745,"props":3791,"children":3793},{"style":3792},"--shiki-default:#C98A7D77",[3794],{"type":616,"value":3795}," \"",{"type":611,"tag":3745,"props":3797,"children":3798},{"style":3767},[3799],{"type":616,"value":3800},"qwen3.6-35b-a3b-q4_k_xl.gguf",{"type":611,"tag":3745,"props":3802,"children":3803},{"style":3792},[3804],{"type":616,"value":3805},"\"",{"type":611,"tag":3745,"props":3807,"children":3808},{"style":3778},[3809],{"type":616,"value":3781},{"type":611,"tag":3745,"props":3811,"children":3812},{"class":3747,"line":136},[3813,3818],{"type":611,"tag":3745,"props":3814,"children":3815},{"style":3778},[3816],{"type":616,"value":3817},"  --local-dir",{"type":611,"tag":3745,"props":3819,"children":3820},{"style":3767},[3821],{"type":616,"value":3822}," ./models\n",{"type":611,"tag":3745,"props":3824,"children":3825},{"class":3747,"line":80},[3826],{"type":611,"tag":3745,"props":3827,"children":3829},{"emptyLinePlaceholder":3828},true,[3830],{"type":616,"value":3831},"\n",{"type":611,"tag":3745,"props":3833,"children":3835},{"class":3747,"line":3834},6,[3836],{"type":611,"tag":3745,"props":3837,"children":3838},{"style":3752},[3839],{"type":616,"value":3840},"# 2. 執行（雙 GPU tensor split）\n",{"type":611,"tag":3745,"props":3842,"children":3844},{"class":3747,"line":3843},7,[3845,3850],{"type":611,"tag":3745,"props":3846,"children":3847},{"style":3761},[3848],{"type":616,"value":3849},"./llama-cli",{"type":611,"tag":3745,"props":3851,"children":3852},{"style":3778},[3853],{"type":616,"value":3781},{"type":611,"tag":3745,"props":3855,"children":3857},{"class":3747,"line":3856},8,[3858,3863,3868],{"type":611,"tag":3745,"props":3859,"children":3860},{"style":3778},[3861],{"type":616,"value":3862},"  -m",{"type":611,"tag":3745,"props":3864,"children":3865},{"style":3767},[3866],{"type":616,"value":3867}," ./models/qwen3.6-35b-a3b-q4_k_xl.gguf",{"type":611,"tag":3745,"props":3869,"children":3870},{"style":3778},[3871],{"type":616,"value":3781},{"type":611,"tag":3745,"props":3873,"children":3875},{"class":3747,"line":3874},9,[3876,3881,3887],{"type":611,"tag":3745,"props":3877,"children":3878},{"style":3778},[3879],{"type":616,"value":3880},"  -ngl",{"type":611,"tag":3745,"props":3882,"children":3884},{"style":3883},"--shiki-default:#4C9A91",[3885],{"type":616,"value":3886}," 99",{"type":611,"tag":3745,"props":3888,"children":3889},{"style":3778},[3890],{"type":616,"value":3781},{"type":611,"tag":3745,"props":3892,"children":3894},{"class":3747,"line":3893},10,[3895,3900,3905],{"type":611,"tag":3745,"props":3896,"children":3897},{"style":3778},[3898],{"type":616,"value":3899},"  --tensor-split",{"type":611,"tag":3745,"props":3901,"children":3902},{"style":3767},[3903],{"type":616,"value":3904}," 1,1",{"type":611,"tag":3745,"props":3906,"children":3907},{"style":3778},[3908],{"type":616,"value":3781},{"type":611,"tag":3745,"props":3910,"children":3912},{"class":3747,"line":3911},11,[3913,3918,3923],{"type":611,"tag":3745,"props":3914,"children":3915},{"style":3778},[3916],{"type":616,"value":3917},"  --ctx-size",{"type":611,"tag":3745,"props":3919,"children":3920},{"style":3883},[3921],{"type":616,"value":3922}," 8192",{"type":611,"tag":3745,"props":3924,"children":3925},{"style":3778},[3926],{"type":616,"value":3781},{"type":611,"tag":3745,"props":3928,"children":3930},{"class":3747,"line":3929},12,[3931,3936,3940,3945,3949],{"type":611,"tag":3745,"props":3932,"children":3933},{"style":3778},[3934],{"type":616,"value":3935},"  -p",{"type":611,"tag":3745,"props":3937,"children":3938},{"style":3792},[3939],{"type":616,"value":3795},{"type":611,"tag":3745,"props":3941,"children":3942},{"style":3767},[3943],{"type":616,"value":3944},"請介紹 Qwen3.6 的架構特色",{"type":611,"tag":3745,"props":3946,"children":3947},{"style":3792},[3948],{"type":616,"value":3805},{"type":611,"tag":3745,"props":3950,"children":3951},{"style":3778},[3952],{"type":616,"value":3781},{"type":611,"tag":3745,"props":3954,"children":3956},{"class":3747,"line":3955},13,[3957,3962],{"type":611,"tag":3745,"props":3958,"children":3959},{"style":3778},[3960],{"type":616,"value":3961},"  -n",{"type":611,"tag":3745,"props":3963,"children":3964},{"style":3883},[3965],{"type":616,"value":3966}," 256\n",{"type":611,"tag":655,"props":3968,"children":3970},{"id":3969},"驗測規劃",[3971],{"type":616,"value":3969},{"type":611,"tag":612,"props":3973,"children":3974},{},[3975,3977,3983],{"type":616,"value":3976},"首次執行後，觀察終端輸出的 ",{"type":611,"tag":2765,"props":3978,"children":3980},{"className":3979},[],[3981],{"type":616,"value":3982},"eval time",{"type":616,"value":3984}," 欄位，確認 token/s 在 100 以上（受記憶體頻寬限制，實際值因 prompt 長度與 context 大小可能浮動 ±20%）。",{"type":611,"tag":612,"props":3986,"children":3987},{},[3988,3990,3996],{"type":616,"value":3989},"同時用 ",{"type":611,"tag":2765,"props":3991,"children":3993},{"className":3992},[],[3994],{"type":616,"value":3995},"nvidia-smi dmon",{"type":616,"value":3997}," 監控雙卡 VRAM 使用量，確認模型分攤至兩卡，無單卡溢出 (OOM) 現象。",{"type":611,"tag":655,"props":3999,"children":4000},{"id":896},[4001],{"type":616,"value":896},{"type":611,"tag":900,"props":4003,"children":4004},{},[4005,4023,4033,4043],{"type":611,"tag":874,"props":4006,"children":4007},{},[4008,4013,4015,4021],{"type":611,"tag":674,"props":4009,"children":4010},{},[4011],{"type":616,"value":4012},"--tensor-split 比例不當",{"type":616,"value":4014},"：兩卡規格相同時設為 ",{"type":611,"tag":2765,"props":4016,"children":4018},{"className":4017},[],[4019],{"type":616,"value":4020},"1,1",{"type":616,"value":4022},"，規格不同時需依 VRAM 比例調整，否則負載不均導致其中一卡 OOM",{"type":611,"tag":874,"props":4024,"children":4025},{},[4026,4031],{"type":611,"tag":674,"props":4027,"children":4028},{},[4029],{"type":616,"value":4030},"ctx-size 過大",{"type":616,"value":4032},"：262K context 需要大量額外 KV cache 記憶體，建議從 8K–16K 開始測試",{"type":611,"tag":874,"props":4034,"children":4035},{},[4036,4041],{"type":611,"tag":674,"props":4037,"children":4038},{},[4039],{"type":616,"value":4040},"NVFP4 誤用",{"type":616,"value":4042},"：在 Ada Lovelace 硬體上載入 NVFP4 版本，速度不會提升，可能因格式相容性出現品質下降",{"type":611,"tag":874,"props":4044,"children":4045},{},[4046,4051],{"type":611,"tag":674,"props":4047,"children":4048},{},[4049],{"type":616,"value":4050},"主機板 PCIe 頻寬",{"type":616,"value":4052},"：若第二插槽為 x4，跨卡傳輸受限，實際速度可能低於 125 tok/s 實測值",{"type":611,"tag":655,"props":4054,"children":4055},{"id":920},[4056],{"type":616,"value":920},{"type":611,"tag":900,"props":4058,"children":4059},{},[4060,4072,4077],{"type":611,"tag":874,"props":4061,"children":4062},{},[4063,4065,4070],{"type":616,"value":4064},"觀測：",{"type":611,"tag":2765,"props":4066,"children":4068},{"className":4067},[],[4069],{"type":616,"value":3982},{"type":616,"value":4071}," (token/s) 、雙卡 VRAM 使用率 (nvidia-smi) 、GPU 溫度（防止降頻）",{"type":611,"tag":874,"props":4073,"children":4074},{},[4075],{"type":616,"value":4076},"成本：兩張 4060 Ti TDP 各約 165W，峰值合計 ~330W，需確認電源供應器容量",{"type":611,"tag":874,"props":4078,"children":4079},{},[4080],{"type":616,"value":4081},"風險：PCIe 插槽頻寬限制、跨卡無 NVLink（4060 Ti 不支援 NVLink，依賴 PCIe 分散，延遲高於 NVLink 方案）",{"type":611,"tag":4083,"props":4084,"children":4085},"style",{},[4086],{"type":616,"value":4087},"html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":323,"searchDepth":618,"depth":618,"links":4089},[]]