[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-why-aws-is-right-to-move-q-developer-users-to-kiro-zh":3,"tags-why-aws-is-right-to-move-q-developer-users-to-kiro-zh":34,"related-lang-why-aws-is-right-to-move-q-developer-users-to-kiro-zh":45,"related-posts-why-aws-is-right-to-move-q-developer-users-to-kiro-zh":49,"series-industry-41ee09c7-6650-4565-80bf-f8b7e00fd3d3":86},{"id":4,"title":5,"content":6,"summary":7,"source":8,"source_url":9,"author":10,"image_url":11,"keywords":12,"language":18,"translated_content":10,"views":19,"is_premium":20,"created_at":21,"updated_at":21,"cover_image":11,"published_at":22,"rewrite_status":23,"rewrite_error":10,"rewritten_from_id":24,"slug":25,"category":26,"related_article_id":27,"status":28,"google_indexed_at":29,"x_posted_at":10,"tweet_text":10,"title_rewritten_at":10,"title_original":10,"key_takeaways":30,"topic_cluster_id":10,"embedding":10,"is_canonical_seed":20},"41ee09c7-6650-4565-80bf-f8b7e00fd3d3","為什麼 AWS 把 Q Developer 使用者轉到 Kiro 是對的","\u003Cp data-speakable=\"summary\">AWS 正把 AI 寫碼重心從 Q Developer 轉到 Kiro，因為後者更適合完整的開發工作流。\u003C\u002Fp>\u003Cp>AWS 把 Q Developer 從 AI 寫碼主軸退場，改推 Kiro，這一步是對的。新 Q Developer 註冊將在 \u003Ca href=\"\u002Fnews\u002Fibm-think-2026-control-over-ai-zh\">2026\u003C\u002Fa> 年 5 月 15 日停止，Opus 4.6 於 2026 年 5 月 29 日退出 Q Developer Pro，付費 IDE 外掛則在 2027 年 4 月 30 日結束支援。這不是小修小補，而是明確宣告：AWS 不再把「IDE 裡的通用聊天助手」視為 AI \u003Ca href=\"\u002Ftag\u002F軟體開發\">軟體開發\u003C\u002Fa>的終局。\u003C\u002Fp>\u003Ch2>第一個論點：Q Developer 已經證明了價值，也暴露了上限\u003C\u002Fh2>\u003Cp>Q Developer 的確有用。它把 AI 帶進 \u003Ca href=\"\u002Ftag\u002Fvs-code\">VS Code\u003C\u002Fa>、JetBrains、Eclipse 和 Visual Studio，讓開發者在原本的編輯器裡就能做生成、除錯與問答。這件事的價值在於教育市場：AI 不該只停留在獨立網頁，而要進入日常開發流程。問題是，這種價值很快就碰到天花板，因為 prompt-by-prompt 的互動只能解決局部問題，無法自然處理架構、測試、需求與長期約束。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778227859877-f170.png\" alt=\"為什麼 AWS 把 Q Developer 使用者轉到 Kiro 是對的\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>AWS 自己也把重點講得很清楚：它認為過去一年的經驗顯示，最有影響力的開發體驗已經超越程式碼生成與補全。這句話等於承認，單一提示詞、單一檔案、單一步驟，並不是 AI 寫碼的正確工作單位。真正重要的是變更計畫、相依關係、驗證路徑與專案規則。Q Developer 能當好助手，但它不適合長期承載這種更大的工作流。\u003C\u002Fp>\u003Ch2>第二個論點：Kiro 的產品形狀才是 agentic 軟體工作的答案\u003C\u002Fh2>\u003Cp>Kiro 不是把聊天框換個名字，而是把工作方式重做一遍。它圍繞 specs、h\u003Ca href=\"\u002Fnews\u002Funipool-shared-expert-pool-moe-zh\">oo\u003C\u002Fa>ks、steering files、custom subagents 與 powers 建構，目標是把 AI 從反應式工具變成可持續執行的開發系統。Specs 提供穩定目標，hooks 讓系統能在存檔或提交等事件上動作，steering files 保存架構與慣例，custom subagents 則把安全審查、\u003Ca href=\"\u002Ftag\u002Fapi\">API\u003C\u002Fa> 契約驗證這類工作拆成明確責任。這是從「幫我寫一個函式」走向「幫我正確交付一個功能」。\u003C\u002Fp>\u003Cp>最能證明 AWS 認定這條路更強的，是模型分配策略。最新的寫碼模型，包括 \u003Ca href=\"\u002Ftag\u002Fopus-47\">Opus 4.7\u003C\u002Fa>，只在 Kiro 上提供。AWS 不是把 Kiro 當成另一個入口，而是把最強模型放進最能消化它們的工作環境。這種平台轉移的邏輯很直接：能力要放在對的流程裡才有價值。若把這些模型繼續留在 Q Developer，只會延長一個 AWS 已經判定不完整的產品哲學。\u003C\u002Fp>\u003Ch2>反方可能怎麼說\u003C\u002Fh2>\u003Cp>最強的反對意見是客戶連續性。Q Developer 已經嵌在許多團隊每天使用的工具裡，AWS 也沒有把所有觸點一起砍掉。AWS 管理主控台、文件、Marketing Website、Console Mobile App，以及 Slack、\u003Ca href=\"\u002Ftag\u002Fmicrosoft\">Microsoft\u003C\u002Fa> Te\u003Ca href=\"\u002Fnews\u002Factcam-joint-camera-motion-control-zh\">am\u003C\u002Fa>s 這些聊天場景都還保留 Q Developer。對依賴這些入口的團隊來說，Kiro 不是即插即用的替代品，而是新的環境、新的概念與新的遷移成本。\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778227849763-62sw.png\" alt=\"為什麼 AWS 把 Q Developer 使用者轉到 Kiro 是對的\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>這個顧慮真實存在，但不足以推翻這個策略。AWS 並沒有說 Kiro 取代 Q Developer 的每一個表面，而是說 IDE 外掛與付費訂閱模型不再是承載最先進寫碼能力的最佳位置。這條線劃得合理。保留主控台與聊天體驗，能照顧輕量工作；把嚴肅的開發工作移到專用的 agentic IDE，則能讓核心能力真正發揮。限制也很明白：只需要簡單協助的使用者，轉換會感到麻煩。但產品方向仍然正確，因為舊形態對 AWS 想做的事來說太窄了。\u003C\u002Fp>\u003Ch2>你能做什麼\u003C\u002Fh2>\u003Cp>如果你是工程師，別再把 AI 寫碼工具當成可互換的自動補全層。先判斷你的工作需要的是聊天助手，還是具備 specs、hooks 與持久專案上下文的 agentic 環境。如果你是 PM 或創辦人，這次調整代表 AI 開發工具正在從「回答提示」走向「編排工作流」。現在就評估 Kiro，對照你現有的 Q Developer 用法做映射，趁 AWS 還在並行支援時完成遷移。\u003C\u002Fp>","AWS 結束把 Q Developer 當成 AI 寫碼核心，改推 Kiro，是把產品重心從提示詞助手轉向可持續的 agentic 工作流。","aws.amazon.com","https:\u002F\u002Faws.amazon.com\u002Fblogs\u002Fdevops\u002Famazon-q-developer-end-of-support-announcement\u002F",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778227859877-f170.png",[13,14,15,16,17],"AWS","Q Developer","Kiro","AI 寫碼","agentic IDE","zh",2,false,"2026-05-08T08:10:26.571375+00:00","2026-05-08T08:10:26.502+00:00","done","ba44b52d-8e4c-4008-a577-096993cd72be","why-aws-is-right-to-move-q-developer-users-to-kiro-zh","industry","025c9bce-38ef-421a-b79e-6b365f1f6693","published","2026-05-08T09:00:13.902+00:00",[31,32,33],"AWS 退出以 Q Developer 為中心的 AI 寫碼路線，是承認 prompt-first 模式已到上限。","Kiro 的 specs、hooks 與 subagents 更適合承載完整的軟體交付流程。","AWS 用長過渡期與模型分流，降低遷移風險，同時明確押注新產品方向。",[35,37,39,41,43],{"name":16,"slug":36},"ai-寫碼",{"name":17,"slug":38},"agentic-ide",{"name":13,"slug":40},"aws",{"name":14,"slug":42},"q-developer",{"name":15,"slug":44},"kiro",{"id":27,"slug":46,"title":47,"language":48},"why-aws-is-right-to-move-q-developer-users-to-kiro-en","Why AWS is right to move Q Developer users to Kiro","en",[50,56,62,68,74,80],{"id":51,"slug":52,"title":53,"cover_image":54,"image_url":54,"created_at":55,"category":26},"e6379f8a-3305-4862-bd15-1192d3247841","why-nebius-ai-pivot-is-more-real-than-hype-zh","為什麼 Nebius 的 AI 轉型比炒作更真實","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778823044520-9mfz.png","2026-05-15T05:30:24.978992+00:00",{"id":57,"slug":58,"title":59,"cover_image":60,"image_url":60,"created_at":61,"category":26},"66c4e357-d84d-43ef-a2e7-120c4609e98e","nvidia-backs-corning-factories-with-billions-zh","Nvidia 出資 Corning 工廠擴產","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778822450270-trdb.png","2026-05-15T05:20:27.701475+00:00",{"id":63,"slug":64,"title":65,"cover_image":66,"image_url":66,"created_at":67,"category":26},"31d8109c-8b0b-46e2-86bc-d274a03269d1","why-anthropic-gates-foundation-ai-public-goods-zh","為什麼 Anthropic 和 Gates Foundation 應該投資 A…","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778796636474-u508.png","2026-05-14T22:10:21.138177+00:00",{"id":69,"slug":70,"title":71,"cover_image":72,"image_url":72,"created_at":73,"category":26},"17cafb6e-9f2c-43c4-9ba3-ef211d2780b1","why-observability-is-critical-cloud-native-systems-zh","為什麼可觀測性是雲原生系統的生存條件","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778794245143-tfqn.png","2026-05-14T21:30:25.97324+00:00",{"id":75,"slug":76,"title":77,"cover_image":78,"image_url":78,"created_at":79,"category":26},"2fb441af-d3c6-4af8-a356-a40b25a67c00","data-centers-pushing-homeowners-to-solar-zh","資料中心推升房主裝太陽能","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778793651300-gi06.png","2026-05-14T21:20:40.899115+00:00",{"id":81,"slug":82,"title":83,"cover_image":84,"image_url":84,"created_at":85,"category":26},"387bddd8-e5fc-4aa9-8d1b-43a34b0ece43","how-to-choose-gpu-for-yihuan-zh","怎麼選《异环》GPU","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1778786461303-39mx.png","2026-05-14T19:20:29.220124+00:00",[87,92,97,102,107,112,117,122,127,132],{"id":88,"slug":89,"title":90,"created_at":91},"ee073da7-28b3-4752-a319-5a501459fb87","ai-in-2026-what-actually-matters-now-zh","2026 AI 真正重要的事","2026-03-26T07:09:12.008134+00:00",{"id":93,"slug":94,"title":95,"created_at":96},"83bd1795-8548-44c9-9a7e-de50a0923f71","trump-ai-framework-power-speech-state-preemption-zh","川普 AI 框架瞄準電力、言論與州權","2026-03-26T07:12:18.695466+00:00",{"id":98,"slug":99,"title":100,"created_at":101},"ea6be18b-c903-4e54-97b7-5f7447a612e0","nvidia-gtc-2026-big-ai-announcements-zh","NVIDIA GTC 2026 重點拆解","2026-03-26T07:14:26.62638+00:00",{"id":103,"slug":104,"title":105,"created_at":106},"4bcec76f-4c36-4daa-909f-54cd702f7c93","claude-users-spreading-out-and-getting-better-zh","Claude 用戶更分散，也更會用","2026-03-26T07:22:52.325888+00:00",{"id":108,"slug":109,"title":110,"created_at":111},"bd903b15-2473-4178-9789-b7557816e535","openclaw-raises-hard-question-for-ai-models-zh","OpenClaw 逼問 AI 模型價值","2026-03-26T07:24:54.707486+00:00",{"id":113,"slug":114,"title":115,"created_at":116},"eeac6b9e-ad9d-4831-8eec-8bba3f9bca6a","gap-google-gemini-checkout-fashion-search-zh","Gap 把結帳搬進 Gemini","2026-03-26T07:28:23.937768+00:00",{"id":118,"slug":119,"title":120,"created_at":121},"0740e53f-605d-4d57-8601-c10beb126f3c","google-pushes-gemini-transition-to-march-2026-zh","Google 把 Gemini 轉換延到 2026 年 3…","2026-03-26T07:30:12.825269+00:00",{"id":123,"slug":124,"title":125,"created_at":126},"e660d801-2421-4529-8fa9-86b82b066990","metas-llama-4-benchmark-scandal-gets-worse-zh","Meta Llama 4 分數風波又擴大","2026-03-26T07:34:21.156421+00:00",{"id":128,"slug":129,"title":130,"created_at":131},"183f9e7c-e143-40bb-a6d5-67ba84a3a8bc","accenture-mistral-ai-sovereign-enterprise-deal-zh","Accenture 攜手 Mistral AI 賣主權 AI","2026-03-26T07:38:14.818906+00:00",{"id":133,"slug":134,"title":135,"created_at":136},"191d9b1b-768a-478c-978c-dd7431a38149","mistral-ai-faces-its-hardest-year-yet-zh","Mistral AI 迎來最硬的一年","2026-03-26T07:40:23.716374+00:00"]