DEV Community: ninghonggang

The late-2025 Juejin picking roundups are now mixing four artifact categories into one S/A/B column

ninghonggang — Thu, 16 Jul 2026 11:08:05 +0000

I went down a rabbit hole this morning reading the late-2025 Juejin picking roundups side by side, and the mobile-app tier snuck into a column I do not think it belongs in. The 编程工具评测 piece ranked Cursor at S档, Claude Code and Codex at A档, then slid Rork, VibeCode App, and Anything — three mobile-app generators — into the same list, and put Lovable and v0 in a frontend-component row that shares the scorecard with GitHub Copilot and Codeium. The AI开发工具最新排行 piece crowned Cursor at 综合能力第一 with a 20元/月 price, Codeium as 免费, and V0.dev as the Vercel-integrated UI specialist, then folded Lovable, BlackBox AI, Replit, and CodeWhisperer into a single ranked list with no metric stated. After putting the mobile tier next to the editor-loop tier next to the component-tier next to the terminal-agent tier, my honest take is that the picking roundups now mix four artifact categories into one column, and the verdict is collapsing across categories that should not share a ranking.

The piece that crystallized it for me opens with Cursor at S档闭眼选, gives Codex an A档 for fast GPT updates, gives Claude Code an A档 while noting that 代理能力 is no longer ahead of Cursor, then slides Lovable and v0 into the same tier because 一句话生成 covers the same audience as Cursor's Cmd+K, then drops Rork, VibeCode App, and Anything into B档 because they generate iOS and Android via Expo. To be fair I would take the exact tier boundaries with a grain of salt because vendors have shuffled bundles since, but the structural tell is what has been rattling around in my head all morning. Cursor, Codex, Claude Code, v0, Lovable, Rork, VibeCode App, and Anything are all in the same ordered list, and the list never names its sort column.

The meta-pattern I want to put down is that the late-2025 picking roundups are now mixing editor-IDE products, terminal-agent products, mobile-app generators, and component-tier frontend tools into one verdict column without acknowledging that the artifact each one ships is the deciding factor. Cursor and Claude Code leave a reviewable git diff with tests and terminal evidence. Codex leaves a patch or a ChatGPT plan upgrade. v0 leaves a React component pointed at Vercel. Lovable leaves a hosted web prototype. Rork and VibeCode App leave an Expo-built iOS and Android pair. Replit leaves a running hosted prototype. Those handoff objects have completely different lifetimes, verification costs, and review loops, and ranking them in one column is like ranking PostgreSQL, GitHub Actions, and a senior backend engineer because all three can help ship a backend. The S that puts Cursor on top and the B that puts Rork below it look like a verdict on quality, but they are really a verdict on four different jobs the roundup never separated out.

Honestly I am a little skeptical of any 2026 picking roundup that prints a single S/A/B tier letter or a single decimal score across these four artifact categories, because the letter is really telling me four different things depending on which author wrote it. The 综合能力第一 ranking of Cursor is sorting on editor-loop fluency, the 性价比之王 ranking of Codeium is sorting on 免费 versus 20元/月 pricing, the V0.dev as UI specialist ranking is sorting on Vercel deployment, and the Lovable ranking is sorting on prototype speed. None of those axes is the same. My gut says the format has not yet noticed that the row it is scoring no longer maps onto a single shape.

The practical takeaway is that the picking roundups are still useful for the within-category anchor and not useful for the cross-category re-rank most engineers are quietly trying to do this quarter. They are good at telling me Cursor, Claude Code, Codex, GitHub Copilot, and Codeium are the five editor-loop tools worth evaluating, and that v0 and Lovable are the two component-tier tools worth evaluating, and that Rork, VibeCode App, and Anything are the three mobile-app generators worth evaluating. They are not good at telling me which one to pick when the job requires a reviewable diff versus a deployed mobile prototype versus a hosted web app, because those three jobs do not share a verdict column. The S letter and the five-axis decimal both compress four artifact categories into one cell, and the cell no longer carries the information the reader needs.

I will reassess in three months. For now I am still mostly on Cursor and Claude Code for repository work, ChatGPT for open-ended exploration, GitHub Copilot when GitHub and VS Code integration removes friction, and v0 when the deliverable is a component rather than a feature, and I am explicitly leaving Lovable, Rork, VibeCode App, and Anything out of my stack until the job genuinely asks for a hosted prototype or a mobile pair. Give it six months and I expect either the picking roundups to bolt on an explicit artifact category column — editor IDE, terminal agent, hosted prototype, component tier, mobile pair — or the tier letter and the decimal scorecard to harden into a permanent cross-category verdict the reader has to decompose by hand, and whichever moves first will tell me whether the format has finally noticed that the row it is ranking is no longer one shape.

The Missing Column in AI Tool Rankings Is the Artifact Left Behind

ninghonggang — Wed, 15 Jul 2026 11:08:54 +0000

I went down a rabbit hole this morning reading the Juejin results for 热门 AI 2025, and the Google learning recap made me notice a column that is missing from almost every AI tool roundup I read. The post moves from Gemini 3 turning a PDF into an interactive tutorial, to guided debugging that leaves the code untouched, to an AI function that writes classifications into Google Sheets, to a mortgage calculator generated inside Google Search. The companion NotebookLM piece moves through cited answers, study guides, quizzes, podcasts, recipe books, and narrated video. Then the December coding ranking goes back to scoring CodeBuddy at 9.6, Sourcegraph Cody at 8.2, Replit Ghostwriter at 8.0, and Codeium at 7.8. Those numbers compare products, but they do not say what artifact I will have in my hands when the session ends, and after years of shipping software I think that missing artifact column matters more than another decimal score.

The contrast gets sharper when I put the outputs side by side. Gemini in Google Search can generate a one-use interactive calculator that exists for the current question. Gemini in Google Sheets can leave behind labeled cells that a colleague can inspect and edit. NotebookLM can return an answer with a citation that jumps back to the exact paragraph in a PDF, or turn the same sources into an audio overview and a video. Cursor and Claude Code can leave a repository diff, tests, terminal output, and a commit candidate. v0 can leave a React component that is already pointed toward Vercel, while Replit can leave a running hosted prototype. To be fair, I would take some of the feature boundaries with a grain of salt because Google, Anthropic, OpenAI, and Vercel keep moving them, but the outputs are not minor UI differences. A cited answer, a mutable spreadsheet, a disposable micro-app, and a reviewable Git diff have completely different lifetimes and verification costs.

That is the next layer down from saying the market has shifted from product rankings to surface rankings. Even a surface is only useful insofar as it produces the right artifact for the next person in the workflow. I do not really care whether Gemini 3 looks smarter than ChatGPT in a demo if the job requires a source-bounded memo another engineer can audit. I do not care whether Cursor feels faster than Claude Code if the job requires a small diff, passing tests, and a clean explanation for a pull request reviewer. I do not care whether NotebookLM can make the most natural podcast if the deliverable is a spreadsheet of claims tied to citations. Honestly, I am a little skeptical of a five-axis scorecard that gives autonomous agent capability and multimodality their own rows but does not ask whether the output is durable, editable, attributable, executable, or easy to review. Those properties decide whether the next hour is productive or spent translating one AI surface into another.

The practical change for me is simple: before I choose a product, I write down the artifact I need. For unfamiliar code, I want Claude Code or Cursor to leave a diff, tests, and terminal evidence rather than a confident chat transcript. For source-heavy research, I want NotebookLM to leave citations rather than a polished summary whose provenance I have to reconstruct. For UI exploration, I want v0 to leave components I can move into a real repository, not screenshots. For bulk feedback triage, a Gemini function in Google Sheets is more useful than ChatGPT prose because the result lands where the team already filters and corrects it. GitHub Copilot still earns its place when the artifact is incremental code inside VS Code and the review loop already lives in GitHub. My gut says this framing also explains why broad rankings feel increasingly wrong: CodeBuddy, Gemini, NotebookLM, v0, and Claude Code are not merely competing on capability; they are manufacturing different handoff objects.

I will reassess in three months. For now I am still mostly on Cursor and Claude Code for repository work, ChatGPT for open-ended exploration, NotebookLM for source-bounded reading, and Gemini when the output belongs inside Google Search or Google Sheets. The difference is that I no longer record the winner of a tool comparison without recording the artifact, its owner, its lifetime, and how it will be checked. Give it six months and I expect the better AI roundups to add an output-artifact column beside price and agent capability, with entries such as cited answer, editable table, reviewable diff, deployed component, and disposable interactive page. Until that happens, I will keep treating the decimal score as product trivia and the artifact left behind as the engineering decision.

The S/A Tier Letter Is Hiding Four Scorecard Columns In Picking Roundups

ninghonggang — Tue, 14 Jul 2026 11:07:50 +0000

I went down a rabbit hole this morning reading the late-2025 Juejin picking roundups side by side — the 2025 的热门 AI 编程工具评测 piece that anchored the review on S/A/B/D tier letters, the 2025年12月权威 piece that printed decimal scorecards from 9.6 down to 7.2 on five axes, the November frontend guide that put Cursor at 综合能力第一 with a 20元/月 price, and the 2025年AI工具定价指南 piece that walked through Gemini Pro at 19.99 dollars per month — and the thing that finally crystallized for me is that the tier letter is no longer the same column it was a year ago, because the picking roundups are now compressing at least four verdicts — code generation, agent autonomy, IDE polish, ecosystem fit — into one S/A/B cell, and the S that puts Cursor on top and the A that puts Claude Code one tier below both look like they disagree when they actually agree on the breakdown across two axes neither post disclosed. I want to put it down before the next quarterly roundup ossifies the letter further.

The piece that pushed me over the edge was the tier-letter review that placed Cursor at S档闭眼选, v0 on the S/A boundary, Claude Code and Codex at A档, and Replit at B档 in a single ordered list, while noting in a side comment that Claude Code had recently seen 性能下降 and its 代理能力 was no longer ahead of Cursor. Then I read the decimal scorecard piece that handed Tencent CodeBuddy a 9.6, Sourcegraph Cody an 8.2, Replit Ghostwriter an 8.0, and Codeium a 7.8 across a five-axis grid. The November frontend piece separately ranked Cursor at 综合能力第一 and Codeium as 性价比之王 at 免费. To be fair I am taking the exact decimal scores and the dollar amounts with a grain of salt because the test corpus is never disclosed and vendors have shuffled tiers since, but the structural tell is what has been rattling around in my head all morning. The S letter absorbed four scorecard columns into one.

The meta-pattern I want to call out is that the late-2025 picking roundups are using the tier letter as a verdict-shorthand that hides a migration from product rankings to job rankings, and the same product can be S on one axis and A on another without the post ever noticing. The tier-letter review puts Cursor at S and Claude Code at A, but if the axis it sorted on was IDE polish and editor-loop fluency Cursor wins, while if the axis was terminal-first agent autonomy with reviewable diffs Claude Code wins and the gap inverts. The decimal scorecard piece formally broke the column into five axes but still ranked CodeBuddy at 9.6 and Blackbox at 7.2 as if the aggregate replaced the breakdown. Honestly I am a little skeptical of any 2026 roundup that prints a single S letter without an axis column, because the S is really telling me one of four different things depending on which author wrote it and which column they were mentally sorting on.

The practical takeaway I want to put down is that the late-2025 to early-2026 picking roundups are still useful for two narrow jobs and not useful for the cross-tier re-rank most engineers are quietly trying to do this quarter. They are good at the per-category anchor, because the tier-letter review did name Cursor, Claude Code, Codex, v0, and Replit as the five worth buying and the decimal piece did name CodeBuddy and Cody and Ghostwriter and Codeium as the eight worth evaluating. They are good at the within-tier rank for the axis the author was sorting on, because the gap between Cursor at S and Replit at B is exactly the kind of decision a team lead needs between two completers. They are not good at the cross-tier re-rank, because the engineer trying to decide Cursor versus Claude Code has to read the tier letter and the side comment about 代理能力 and discover they describe two different columns. The single-cell tier letter is the row that broke ties by hiding the columns underneath it.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land, except that I now think of them as a Cursor-IDE surface and a Claude-Code-terminal surface rather than two competitors. What has changed is that I now read the picking roundups as a tier-letter verdict on a column the post never disclosed, and I look for the side comments and the decimal breakdown before I trust the letter, and when the letter and the side comment disagree I treat the letter as marketing. Give it six months and I expect either the picking roundups to bolt on an explicit axis column underneath the tier letter or the tier letter to harden into a permanent one-cell verdict the reader has to decompose, and whichever moves first will tell me whether the format has finally noticed that the S it prints is no longer one number.

The AI pricing roundup has quietly forked into three currencies

ninghonggang — Sun, 12 Jul 2026 11:07:55 +0000

I went down a rabbit hole this morning reading the late-2025 Juejin AI tool pricing coverage side by side, and the thing that finally crystallized for me is that the price-anchored format has itself forked into two sub-currencies that publish under the same search query, and on top of that the dollar-mode sub-format has bolted on a forecast column the yuan-mode sub-format does not carry. The engineer trying to read a single 2026 pricing post is now bridging three price-time coordinates before they even get to the well-known pricing-vs-scorecard split, and the bridge work is invisible because all three pieces look like AI tool pricing from the search results page.

The piece that pushed me over the edge was the 2025 AI tool pricing guide, which walked through Google Gemini Pro at 19.99 dollars, ChatGPT Plus at 20 dollars, Claude Pro at 20 dollars, Grok at 40 dollars, and Midjourney at 10 to 120 dollars, all in dollars, all monthly, with an explicit forecast paragraph noting that API prices dropped 90 percent across 2024 to 2025 but that ChatGPT Plus is projected to rise toward 44 dollars by 2029. Then I read the 2025 年度盘点 piece, which listed Gemini Pro at 140 元, ChatGPT Plus at 140 元, Claude Pro at 140 元, Midjourney standard at 210 元, and Claude MAX at 700 元, all in yuan, all monthly, with no forecast column and no exchange-rate note. To be fair I am taking the dollar amounts and the yuan amounts with a grain of salt because both pieces were published in late 2025 and vendors have shuffled tiers since, but the sub-currency fork inside the pricing format is what has been rattling around in my head all morning.

The meta-pattern I want to call out is that the late-2025 to early-2026 Juejin AI tool coverage has now forked into three price-time coordinates that the engineer has to bridge manually. The dollar-now coordinate puts ChatGPT Plus at 20 dollars and Gemini Pro at 19.99 dollars and Claude Pro at 20 dollars, which is a clean three-way tie. The dollar-future coordinate from the same pricing guide puts ChatGPT Plus at a projected 44 dollars by 2029 and leaves Gemini Pro and Claude Pro unprojected, which is not a tie at all. The yuan-now coordinate puts the same ChatGPT Plus and Gemini Pro and Claude Pro at 140 元 each, also a three-way tie, but at roughly 7.05 元 to the dollar that tie means the Chinese reader is paying about 19.86 元 while the US reader is paying 20 dollars, which is the same number only if you ignore the currency. Honestly I am a little skeptical of any 2026 roundup workflow that pulls a single pricing post off the search results page and trusts it as a single source of truth, because the three coordinates are really telling me the price-anchored format has specialized to the point where one post is not a substitute for another.

The practical takeaway I want to put down is that the late-2025 to early-2026 pricing roundups are still useful for three narrow jobs and not useful for the fourth job most engineers are quietly trying to do. The dollar-now sub-format is good at the US-credit-card-bill job, because the 20 dollar figure matches what shows up on the statement. The dollar-future sub-format is good at the budget-projection job, because the 44 dollar projection tells a finance lead what to budget for in three years. The yuan-now sub-format is good at the China-credit-card-bill job, because the 140 元 figure matches what the Chinese reader is paying through 神马中转 API or a domestic wallet. None of them are good at the cross-currency stack-assembly job, because the reader has to take the dollar-now anchor from one piece, the dollar-future anchor from the same piece, and the yuan-now anchor from another, and then convert at the prevailing rate to discover that the 44 dollar ChatGPT Plus projection is roughly 310 元 while the 140 元 ChatGPT Plus today is roughly 19.86 dollars, and the only place that conversion is happening is in the reader's head.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land, except the 44 dollar ChatGPT Plus forecast is the first time a roundup has put a number on the trajectory. What has changed is that I now read the dollar-mode pricing pieces for the US-card-bill anchor and the trajectory column, the yuan-mode pricing pieces for the domestic-card-bill anchor, and the scorecard pieces for the coding-side rank, and I treat any single pricing roundup as one slice of a three-slice workflow rather than as a verdict. Give it six months and I expect either the yuan-mode pricing pieces to bolt on an exchange-rate column or the dollar-mode pricing pieces to bolt on an explicit 44 dollar projection for Gemini Pro and Claude Pro, and whichever moves first will tell me whether the pricing-format collapses back into one currency or hardens into a permanent reader-bridging chore.

The picking-format forked again: editorial verdicts and commercial walkthroughs under the same search query

ninghonggang — Sat, 11 Jul 2026 11:10:57 +0000

I spent a chunk of this morning reading the late-2025 Juejin AI tool coverage one more time, partly because I keep getting asked which roundup to trust, and partly because I wanted to see whether the format had finally settled into a single verdict or kept forking. The set I worked through was the 2025 coding tools S/A/B/D tier ranking piece, the 中文AI工具推荐 directory that runs seven categorical sections and pivots halfway through to 神马中转 API, the AI tool pricing guide with the monthly-bill anchor, and the December authoritative eight-mainstream coding ranking with the 9.6/8.2/7.8 decimal scorecard, and the thing that crystallized for me is that the picking-format itself has now split into a fork I had not quite named yet: the editorial sub-format that prints verdicts and the commercial sub-format that prints sponsors, and the two sub-formats publish under the same search query while answering completely different questions.

The piece that pushed me over the edge was reading the AI tool pricing guide, which walked through Google Gemini Pro at 19.99 dollars per month, ChatGPT Plus at 20 dollars per month, Claude Pro at 20 dollars per month, Grok at 40 dollars per month, Midjourney at 10 to 120 dollars per month, Perplexity Pro at 20 dollars per month, all consumer or generalist, all with a monthly bill the reader has to add up. Then I read the S/A/B/D tier ranking, which put Cursor at S-tier, v0 at S/A boundary, Claude Code at A-tier, Replit at B-tier, and skipped C-tier with a footnote that the C-tier did not have meaningful candidates this year. To be fair I am taking the exact dollar amounts and the exact tier placements with a grain of salt because both pieces were published in late 2025 and vendors have shuffled tiers since, but the structural fork is what has been rattling around in my head all morning. The pricing guide is recommending tools the S/A/B/D piece never scored, and the S/A/B/D piece is scoring tools the pricing guide never priced.

The meta-pattern I want to call out is that the late-2025 to early-2026 Juejin AI tool coverage has now split into three sub-formats that no longer share a single ranking convention. The editorial tier-grading sub-format puts tools into S/A/B/D buckets with no C and a footnote that explains the gap, and v0 sits ambiguously on the boundary. The decimal-scorecard sub-format prints 9.6/8.2/7.8 across five axes for eight IDE plugins with no price column. The commercial sub-format prints affiliate pricing tables and sponsor walkthroughs with the verdict pre-baked into the click-through. Honestly I am a little skeptical of any 2026 roundup workflow that pulls the first result for 热门 AI 2025 off Juejin and trusts it as a single source of truth, because the three sub-formats are really telling me the picking genre has specialized to the point where one post is not a substitute for another, and the engineer who reads the editorial tier-grading piece will never hear about the 神马中转 API pivot and the engineer who reads the commercial piece will never hear the v0 S/A-boundary caveat.

The practical takeaway I want to put down is that the late-2025 to early-2026 roundups are still useful for three narrow jobs and not useful for the fourth job most engineers are quietly trying to do. The tier-grading sub-format is good at the quick-bucketing job, because the S/A/B/D piece gives a busy engineer a one-glance verdict that survives a skim read. The decimal-scorecard sub-format is good at the within-axis spread job, because the spread between CodeBuddy at 9.6 and Blackbox at 7.2 is exactly the kind of decision a team lead needs between two autocomplete candidates. The commercial sub-format is good at the surface-scout job, because the China-access pivot surfaced tools I had not seen on the editorial pieces. None of them are good at the bias-adjusted selection job, because the reader has to take the tier verdict from the editorial piece and the dollar amount from the commercial piece and the within-axis spread from the scorecard piece, and the three reads on the same tool can land in three different buckets without any of them being dishonest.

I will reassess in three months. I am mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land, except the monthly bill is roughly where I expected it because I had to do the addition myself. What has changed is that I now read the tier-grading pieces for the bucketing signal, the decimal-scorecard pieces for within-axis spread, and the commercial pieces for the surface-scout, and I treat any single roundup as one slice of a three-slice workflow rather than as a verdict. Give it six months and I expect either the editorial camp to publish a transparency column naming which commercial rows are paid or the commercial camp to publish a tier badge mirroring the S/A/B/D buckets, whichever moves first will tell me whether the picking-format collapses into one currency or hardens into a chore.

The Picking-Format Has Forked Into Three Incompatible Sub-Formats And That's The Story

ninghonggang — Fri, 10 Jul 2026 11:08:40 +0000

I went down a rabbit hole this morning reading the late-2025 Juejin AI tool coverage side by side — the 2025 coding tools review with the S/A/B/D tier ranking, the November frontend picking guide with the 按预算选择 structure, the December authoritative eight-mainstream coding ranking with the 9.6/8.2/7.8 decimal scorecards, and the 2025 Chinese AI tools directory with seven categorical sections plus a 神马中转 API pivot — and the thing that finally crystallized for me is that the picking-format itself has forked into at least three incompatible sub-formats on the same page, and the engineer who reads two picks in the same week can get two different rankings on the same tool without either one being obviously wrong.

The piece that pushed me over the edge was reading the S/A/B/D tier ranking piece next to the decimal scorecard piece and noticing that they share almost no product names and use completely different ranking currencies. The S/A/B/D piece put Cursor at S-tier, v0 at S/A boundary, Claude Code at A-tier, Replit and Chef at B-tier, and explicitly skipped C-tier with a footnote saying the C-tier did not have any meaningful candidates this year. The decimal scorecard piece put CodeBuddy at 9.6, Sourcegraph Cody at 8.2, Replit Ghostwriter at 8.0, Codeium at 7.8, Tabnine at 7.6, CodeWhisperer at 7.5, JetBrains AI Assistant at 7.4, and Blackbox at 7.2 on a five-axis grid. To be fair I am taking the exact decimal scores with a grain of salt because both pieces were published in the last quarter of 2025 and the test corpora are the authors' own workloads, but the structural disjointness is what has been rattling around in my head all morning. Two pieces from the same genre, same month, same language, with the same headline framing, and the verdict-overlap is almost zero.

The meta-pattern I want to call out is that the late-2025 Juejin picking-format has split into three sub-formats that no longer agree on what a pick looks like. The tier-grading sub-format puts tools into S/A/B/D buckets with no C and with v0 sitting ambiguously on the S/A boundary. The decimal-scorecard sub-format prints a 9.6/8.2/7.8 grid across five axes with a separate row for each tool. The budget-tier sub-format in the frontend guide ranks tools by how much monthly spend the engineer can absorb (预算充足, 预算有限, 无预算), with GitHub Copilot at ten dollars per month anchoring the cheap tier and Cursor at twenty dollars per month anchoring the comfortable tier. Honestly I am a little skeptical of any 2026 picking roundup that treats a single piece as a single source of truth, because the three sub-formats are really telling me the picking genre has forked internally and the engineer who reads one picking post is reading a third of the picking story.

The practical takeaway I want to put down is that the late-2025 to early-2026 Juejin picking roundups are still useful for three narrow jobs and not useful for the fourth job most engineers are quietly trying to do. The tier-grading sub-format is good at the quick-bucketing job, because the S/A/B/D piece gives a busy engineer a one-glance verdict that survives a skim read. The decimal-scorecard sub-format is good at the within-axis spread job, because the spread between CodeBuddy at 9.6 and Blackbox at 7.2 is exactly the kind of decision a team lead needs to make between two autocomplete candidates. The budget-tier sub-format is good at the monthly-bill-matching job, because the 按预算选择 structure tells an engineer with a tight budget to start with Codeium and V0 instead of Cursor and GitHub Copilot. None of them are good at the cross-sub-format consensus job, because the engineer has to take the tier verdict from one piece and the decimal verdict from another and the budget verdict from a third, and the three verdicts on the same tool can land in three different buckets without any of them being dishonest.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land, except the picking-format split is now making the within-IDE-tooling decision harder rather than easier. What has changed is that I now read the tier-grading pieces for the quick-bucketing signal, the decimal-scorecard pieces for the within-axis spread, and the budget-tier pieces for the monthly-bill-matching verdict, and I treat any single picking roundup as one slice of a three-slice workflow rather than as a verdict. Give it six months and I expect either the tier-grading sub-format to publish a decimal scorecard alongside each tier or the decimal-scorecard sub-format to publish an explicit tier alongside each row, and whichever moves first will tell me whether the picking-format is going to collapse back into one currency or harden into a permanent reader-bridging chore.

The pricing guide and the scorecard stopped sharing tools

ninghonggang — Wed, 08 Jul 2026 11:09:44 +0000

I went down a rabbit hole this morning reading the late-2025 Juejin AI tool coverage side by side — the 2025 AI tool pricing guide piece anchored on monthly bills, the December authoritative eight-mainstream coding ranking anchored on decimal scorecards, the November frontend-developer picking guide, and the 论文季 sponsored walkthrough — and the thing that finally crystallized for me is that the price-anchored coverage and the scorecard-anchored coverage are now recommending two completely disjoint toolsets that share almost no product names, and the engineer trying to assemble a 2026 stack has to bridge two reviews that do not agree on what counts as a tool worth ranking. I want to put it down before the disjoint-toolsets split becomes invisible to readers because both formats look like 2025 AI roundups from the search results page.

The piece that pushed me over the edge was the pricing guide, which walked through Google Gemini Pro at 19.99 dollars per month, ChatGPT Plus at 20 dollars per month, Claude Pro at 20 dollars per month, Grok at 40 dollars per month, Midjourney at 10 to 120 dollars per month, Perplexity Pro at 20 dollars per month, and Poe on the 5 to 249.99 dollar span, all consumer or generalist, all with a monthly bill to add up. Then I read the December ranking piece, which scored Tencent CodeBuddy at 9.6, Sourcegraph Cody at 8.2, Replit Ghostwriter at 8.0, Codeium at 7.8, Tabnine at 7.6, Amazon CodeWhisperer at 7.5, JetBrains AI Assistant at 7.4, and Blackbox at 7.2 on the five axes, all coding or IDE, all scored on a decimal grid, all with no price column. The two pieces share zero product names. To be fair I am taking the dollar amounts with a grain of salt because the pricing guide was published in late 2025 and vendors have shuffled tiers since, but the disjointness is what has been rattling around in my head all morning. The pricing guide is recommending tools the scorecard never heard of, and the scorecard is ranking tools the pricing guide never priced.

The meta-pattern I want to call out is that the late-2025 Juejin AI tool coverage has quietly bifurcated into a consumer-and-generalist camp anchored on monthly bills and a coding-and-IDE camp anchored on decimal scorecards, and the two camps no longer share a single product name across their top tens. The pricing guide names Gemini Pro, ChatGPT Plus, Claude Pro, Grok, Midjourney, Perplexity, Poe. The December ranking names CodeBuddy, Sourcegraph Cody, Replit Ghostwriter, Codeium, Tabnine, CodeWhisperer, JetBrains AI Assistant, Blackbox. Honestly I am a little skeptical of any 2026 roundup workflow that pulls a best AI tools post off the search results page and trusts it as a single source of truth, because the disjointness is really telling me that the two formats have specialized to the point where one post is not a substitute for the other, and the engineer who reads only the pricing guide will never hear about CodeBuddy and the engineer who reads only the scorecard will never hear that Claude Code is now its own subscription tier.

The practical takeaway I want to put down is that the late-2025 to early-2026 roundups are still useful for two narrow jobs each and not useful for the third job most engineers are quietly trying to do. The pricing-guide format is good at the monthly-bill job, because Gemini Pro plus ChatGPT Plus plus Claude Pro plus Midjourney plus Perplexity adds up to a number the engineer needs to know. The scorecard format is good at the within-category coding rank, because the spread between CodeBuddy at 9.6 and Blackbox at 7.2 is exactly the kind of decision a team lead needs to make between two autocomplete candidates. They are not good at the cross-category stack-assembly job, because the reader has to take the price column from one piece and the code-generation pick from the other and discover that the recommended coding tool is not priced in the pricing guide, and the recommended generalist tool is not scored in the December ranking. The disjoint top-ten overlap.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land, except Claude Code has quietly become its own subscription tier outside the IDE, and the monthly bill is roughly where I expected it to be because I had to do the addition myself. What has changed is that I now read the pricing guide pieces for the monthly bill, the scorecard pieces for the within-category rank, and the picking-guide pieces for the alternative survey, and I treat any single roundup as one slice of a three-slice workflow rather than as a verdict. Give it six months and I expect either the price-anchored coverage to start naming coding IDEs with explicit monthly bills or the scorecard-anchored coverage to start naming generalist assistants with decimal ranks, and whichever moves first will tell me whether the engineer is still doing the merge at the keyboard.

The 2026 Juejin AI tool roundup has quietly become a content-commerce funnel

ninghonggang — Mon, 06 Jul 2026 11:07:24 +0000

I went down a rabbit hole this morning reading the late-2025 Juejin AI tool roundups side by side — the 2026年前端开发者必学的10个AI工具 piece with the affiliate pricing table, the 论文季AI工具实测 sponsored walkthrough that ended on 雷小兔, the 2025年中文AI工具推荐 directory that pivoted halfway through to 神马中转 API, and the 2025年AI开发工具最新排行 with the 20元/月 Cursor anchor — and the thing that finally crystallized for me is that the 2025 to 2026 roundup format has quietly completed its transition from editorial coverage to content commerce, and almost every "best AI tools" post I read this morning is now structured around a sponsor pick and an affiliate link with the verdict pre-baked into the structure. I want to put it down before the format ossifies any further into a listicle funnel with editorial skin.

The piece that pushed me over the edge was the 10-tool 前端 guide that opened with a 3x productivity claim, walked through GitHub Copilot at 10美元 per month with a 优惠链接, then V0 by Vercel for free, then Tabnine at 12美元 per month for enterprise, with a five-star rating column tacked onto every row, and the very last section was a Q&A that pointed back to the Phind link. The 论文季 piece ran a similar shape: five tools tested one by one, ending with 雷小兔 on a six-bullet highlight list with 学生免费 repeated four times. To be fair I am taking the exact productivity multiplier claims with a grain of salt because the test corpus is the author's own workload, but the structural pattern is what has been rattling around in my head all morning. The format is no longer "here are ten tools ranked" — the format is "here are ten tools, four are affiliate picks, one is a sponsor, and the verdict reads like a buyer's guide because the genre has become one."

The meta-pattern I want to call out is that the 2025 to 2026 Juejin AI tool coverage has split into a content-commerce camp that prints affiliate pricing tables and sponsor walkthroughs, and an editorial camp that still tries to print decimal scorecards and ranking currencies, and the two camps share almost no format conventions anymore. The 前端 guide priced every tool in dollars with an explicit 优惠链接 column. The 论文季 piece structured the whole review as a five-tool showdown with the sponsor placed last and awarded an extra bullet list. The 中文AI工具推荐 piece pivoted halfway through to 神马中转 API as the China workaround for ChatGPT and Claude. The 2025 AI tool pricing guide at result 5 was the rare one that named dollar prices and Anthropic and OpenAI and Google and stopped short of telling you to click anything. Honestly I am a little skeptical of any 2026 roundup that prints an affiliate link column without disclosing which rows are paid, because what the affiliate-link column is really telling me is that the format has been optimized for the click-through rate rather than for the engineer's tool selection, and the verdict is now load-bearing for someone's revenue share.

The practical takeaway I want to put down is that the late-2025 to early-2026 roundups are still useful for two narrow jobs and not useful for the selection job most readers think they are doing. They are good at the surface-scout job, because the 10-tool 前端 guide did surface Phind and Pieces and Continue which I had not seen on the picking roundups. They are good at the China-access workaround job, because the 神马中转 API mention is genuinely useful for engineers behind the GFW. They are not good at the bias-adjusted selection job, because the reader has to discount the sponsor rows and the affiliate rows by an unknown amount before the verdict applies to their own workflow, and that discount is not disclosed anywhere. The fact that the top result for "热门 AI 2025" on Juejin is now a listicle funnel with the verdict pre-baked into the structure is the structural tell.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land, and the monthly bill is roughly where I expected it because I had to do the addition myself. What has changed is that I now read the late-2025 to early-2026 Juejin roundups as content-commerce artifacts first and editorial coverage second, and I look for the affiliate pricing table and the sponsor bullet list before I look for the verdict, and when both are present I treat the verdict as marketing. Give it six months and I expect either the editorial camp to publish a roundup that explicitly discounts the affiliate rows or the content-commerce camp to publish a transparency page that names which rows are paid, and whichever one moves first will tell me whether the format has finally noticed the reader is now doing the bias-adjustment at the keyboard.

The picking scorecard still has no row for MCP and the GitHub trending list is dominated by MCP servers

ninghonggang — Sun, 05 Jul 2026 11:10:19 +0000

I went down a rabbit hole this morning reading the late-2025 Juejin picking roundups next to the 2025 AI工程新趋势 piece and the August and October GitHub trending recaps, and the thing that finally crystallized for me is that the picking scorecards are still printing the same 2024 axes — autocomplete latency in milliseconds, response speed tier, autonomous agent capability star count, security and SOC2 star count, team collaboration star count — while the underlying substrate the community is actually shipping on is the Model Context Protocol layer and the memory-layer projects like supermemory and mem0, none of which shows up as a scorecard row. I would not have written that six months ago, and I want to put it down before the row that breaks ties between Cursor and Claude Code and Trae and Windsurf gets buried under another quarter of decimal-precision coverage.

The piece that pushed me over the edge was noticing that the August trending list led with Archon (a MCP server for sharing project context across Claude Code and Cursor and Windsurf), Claude Code Router, and Serena, and the October list led with Agent-S and claude-cookbooks and supermemory and TradingAgents-CN, while the December ranking printed Tencent CodeBuddy at 9.6, Sourcegraph Cody at 8.2, Replit Ghostwriter at 8.0, Codeium at 7.8 on the five axes. The AI工程新趋势 piece named MCP普及 (Model Context Protocol spread) as one of this year's defining trends. To be fair I am taking the exact decimal scores with a grain of salt because the test corpus is never disclosed, but the structural standoff is what has been rattling around in my head all morning. The picking scorecard has not added a row for MCP support, and the trending list is dominated by MCP servers.

The meta-pattern I want to call out is that the late-2025 picking roundups and the GitHub trending recaps are now measuring different layers of the same stack and the picking scorecard has no row to translate between them. Cursor 1.7 added MCP support. Claude Code is built on MCP. Windsurf routes through MCP. Trae is built on MCP. Codex CLI ships with a MCP layer. GitHub Copilot has been quietly repositioning around Copilot Chat and PR summaries, which barely show up in the scorecards I read this morning. Honestly I am a little skeptical of any AI tool ranking that scores tools on the SOC2 axis and ignores the MCP compatibility axis, because the SOC2 column is grading the procurement story and the MCP column is grading the integration story and engineers are now hiring on the integration story. The trending projects that do show up on the picking scorecards are the ones that won the autocomplete race a year ago and never had to compete on MCP. The trending projects that don't show up — Archon, Claude Code Router, supermemory, Graphiti, AGENTS.md, Agent-S — are the ones the picking roundups have no row to evaluate.

The practical takeaway I want to put down is that the late-2025 Juejin picking roundups are still useful for two narrow jobs and not useful for the third job most engineers are quietly trying to do this quarter. They are good at the per-category pick, because the 2025年度盘点 named a clear general-assistant pick and the December ranking named a clear coding pick. They are good at the alternative-survey job, because the long-tail walk through Windsurf and Trae and Codex CLI and Antigravity and Kiro is genuinely helpful if you have not heard of any of them yet. They are not good at the agent-runtime substrate question, because the row that would tell you which MCP-aware backend to pair with your actual workflow is not in the scorecard, and the trending lists tell you the substrate matters more than the frontend but do not tell you which frontend to pair it with. I have not stress-tested Archon or Claude Code Router the way I have with Cursor and Claude Code, so I want to actually wire them up for a quarter before I oversell or undersell them, but the fact that the picking scorecard has not added an MCP row across an entire year of quarterly reviews is the structural tell.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land. What has changed is that I now read the picking roundups as a list of which MCP-aware tools have shipped the most polish, and I read the GitHub trending recaps as the source of truth on what the agent-runtime substrate looks like, and I expect the next generation of roundups to either drop MCP support as the column nobody needed or to make it the row that breaks ties between otherwise identical tools. Give it six months and I expect either the picking scorecards to add an MCP row or the agent-runtime projects to ship their own consumer-facing AI coding tools and reabsorb Cursor and Claude Code as their IDE frontends, and whichever one moves first will tell me whether the format has finally noticed the row that matters has moved out from under it.

Three ranking currencies and zero overlap: what 2025 Juejin AI roundups actually disagree about

ninghonggang — Sat, 04 Jul 2026 11:08:10 +0000

I went down a rabbit hole this morning reading the Juejin 2025 AI tool roundups next to the Juejin GitHub trending monthly lists, and the thing that finally crystallized for me is that the late-2025 roundup format has quietly forked into three incompatible ranking currencies — the five-axis decimal scorecard that the December coding ranking printed, the 元 per month price column that the 2025 年度盘点 piece anchored on, and the star-velocity monthly count that the October and August and May GitHub trending lists sorted by — and no post uses more than one, and the engineer trying to assemble a stack has to convert between the three currencies themselves to discover the recommendations contradict each other. I want to put it down before the three-currency split hardens into the default state of the roundup format.

The piece that pushed me over the edge was noticing the May GitHub trending list landing at the same time as the late-2025 picking roundups, and the two reading experiences produced two entirely different rankings. The May list led with WeClone and MoneyPrinterTurbo and Void and Suna and LTX-Video and mem0 and FlowGram.AI and Ladybird, the October list led with prompt-eng-interactive-tutorial and Agent-S and claude-cookbooks and nanoGPT and supermemory and TradingAgents-CN, and not one of those names showed up in the 选型横评 verdict. To be fair the GitHub lists explicitly sort by monthly star velocity and the picking roundups explicitly sort by 五轴 capability scores, and I am taking the star counts with a grain of salt, but the structural standoff is what has been rattling around in my head all morning. The same week produced a 选一个开始用 verdict that named Cursor and Claude Code, and a trending list that led with chat-clone training kits and short-video automation frameworks, and the two pieces had zero overlap in their top ten.

The meta-pattern I want to call out is that the 2025 Juejin AI tool coverage has produced three ranking currencies that no single post reconciles, and each post picks the currency that flatters its own conclusion. The 2025 年度盘点 piece anchored on 元 per month and named Gemini Pro and ChatGPT Plus and Claude Pro all at 140 元 per month with Midjourney standard at 210 元 and Claude MAX at 700 元 per month, which is a price story. The December IDE ranking anchored on the 9.6/8.2/8.0/7.8/7.6/7.5/7.4/7.2 five-axis card for CodeBuddy and Cody and Ghostwriter and Codeium and Tabnine and CodeWhisperer and JetBrains and Blackbox, which is a capability story. The October trending piece led with prompt-eng-interactive-tutorial and Agent-S, which is a developer-curiosity story. Honestly I am a little skeptical of any 2025 roundup ecosystem that lets three ranking currencies co-exist without any cross-currency normalization, because the three-currency split is really telling me that each format is optimizing for a different reader job — the price piece for the budget-conscious engineer, the scorecard piece for the procurement officer, the trending piece for the developer who wants to know what their peers are bookmarking — and none maps cleanly onto the working engineer trying to pick one tool to pay for this quarter.

The practical takeaway I want to put down is that the three formats are still useful for three narrow jobs and not useful for the integration job most readers are quietly trying to do. The price-anchored 2025 年度盘点 is good at the budget tier job because the 140 元 anchor makes the per-month comparison honest. The scorecard-anchored December IDE ranking is good at the enterprise procurement job because it weighed 等保三级 compliance. The star-velocity trending list is good at the what-is-everyone-starring-this-month job because it surfaces WeClone and Agent-S and mem0 which the picking roundups completely ignore. They are not good at the cross-currency reconciliation job, because Cursor Pro at twenty dollars is in the price column but not in the trending list, Claude Code is in the scorecard column but not in the trending list, and Mem0 is in the trending list but not in either of the other two. I have not stress-tested WeClone or Agent-S the way I have with Cursor and Claude Code, but the fact that three ranking currencies coexist without a published conversion table is the structural tell.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land. What has changed is that I now read the 2025 Juejin roundups as three ranking-currency artifacts rather than three picking guides, and I do my own cross-currency scoring in a notebook before I act on any of them. Give it six months and I expect either the roundups to publish a cross-currency normalized score or the front page to show a meta-ranking that converts between the three formats, and whichever one moves first will tell me whether the format has finally noticed the engineers are already doing the merge at the keyboard.

The price-anchor split nobody called out in the late-2025 Juejin roundups

ninghonggang — Fri, 03 Jul 2026 11:06:57 +0000

I went down a rabbit hole this morning reading the late-2025 Juejin AI tool roundups side by side — the 12-scenario 2025 年度盘点 piece, the December authoritative eight-mainstream coding ranking, the November frontend-developer picking guide, and the July global LLM leaderboard — and the thing that finally crystallized for me is that the 2025 roundup format made a quiet structural shift that nobody called out, the broad-market roundups and the category-specific roundups stopped sharing a common price-anchor frame, and the engineer doing the actual selection is left multiplying per-scenario subscriptions in their head to discover the cumulative monthly bill that neither format is willing to print. I want to put it down before the price-anchor split hardens into a permanent format split.

The piece that pushed me over the edge was the December coding ranking that printed Tencent CodeBuddy at 9.6 out of 10, Sourcegraph Cody at 8.2, Replit Ghostwriter at 8.0, Codeium at 7.8, Tabnine at 7.6, Amazon CodeWhisperer at 7.5, JetBrains AI Assistant at 7.4, and Blackbox at 7.2 on a five-axis card nobody else seems to use, alongside the 2025 年度盘点 piece that priced Gemini Pro and ChatGPT Plus and Claude Pro all at 140 元 per month with no attempt to combine them. To be fair the December ranking was explicit about being coding-only, and I am taking the exact decimal scores with a grain of salt because the test corpus is undisclosed, but the structural disconnect is what has been rattling around in my head all morning. The coding post ranks eight tools and never mentions price, the broad-market post prices five flagship tools and never asks which two you would actually combine.

The meta-pattern I want to call out is that the 2025 Juejin roundups split into a price-aware broad-market camp and a price-blind category-specific camp, and neither asks the cross-category stack question most engineers are quietly trying to answer. The 2025 年度盘点 priced Gemini Pro and ChatGPT Plus and Claude Pro at the same 140 元 per month anchor, then noted Midjourney standard at 210 元 per month and Claude MAX at 700 元 per month, which tells a Chinese reader exactly what tier to budget for the general-assistant slot but stops short of asking which coding tool and which image tool would pair with that tier without doubling the bill. The December coding ranking filled the alternative-survey job with the eight-tool card and the long-tail walk, but skipped the price column entirely, so a reader who finishes the coding post still does not know whether to budget 10 元 per month for GitHub Copilot, 20 元 per month for Cursor, or 200 元 per month for Cursor Business. Honestly I am a little skeptical of any 2025 roundup that prints a five-axis decimal scorecard without a price column, because what the price-blindness is really telling me is that the format has been optimized for the Juejin front-page ranking contest rather than for telling a working engineer how to assemble a stack they can actually afford.

The practical takeaway I want to put down is that the late-2025 roundups are still useful for two narrow jobs and not useful for the integration job most readers think they are doing. They are good at the per-category pick, because the 2025 年度盘点 named a clear general-assistant pick and the December coding ranking named a clear coding pick and the November frontend guide named Cursor as the large-project pick with Codeium as the free fallback. They are good at the long-tail survey, because the December ranking walked through JetBrains AI Assistant and Blackbox which I had not seen anyone discuss in months, and the 2025 年度盘点 named a half-dozen Chinese-native options including 通义灵码 and Doubao that the English-language coverage mostly skips. They are not good at the monthly-bill integration, because the engineer has to do the multiplication across 140 元 for Gemini plus 20 元 for Cursor plus 20 元 for Claude Code plus 210 元 for Midjourney, and that calculation is not in any of the four posts. The fact that no late-2025 Juejin roundup publishes the cross-category total monthly estimate is the structural tell.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land, and the monthly bill is roughly where I expected it because I had to do the addition myself. What has changed is that I now read the late-2025 Juejin roundups as one half of a two-piece reading and I look for the price column in the coding posts and the decimal scorecard in the broad-market posts, and when neither is there I treat the verdict as provisional. Give it six months and I expect either the coding roundups to start including a price column or the broad-market roundups to start publishing a cross-category total monthly estimate, and whichever format moves first will tell me whether the roundups have finally noticed the bill is bigger than any single post hints.

The Juejin AI coding roundups have stopped disagreeing, and that is the problem

ninghonggang — Thu, 02 Jul 2026 11:06:16 +0000

I went down a rabbit hole this morning reading the Juejin 2026 AI coding roundups next to the Juejin 2025 roundups I had bookmarked, and the thing that finally crystallized for me is that the headline pick has not changed in twelve months while the long tail of alternatives has forked into at least four product philosophies, and the roundups are still trying to score all of them on a single axis and rank them against Cursor and Claude Code as if that question still made sense. I would not have written that sentence a year ago, and I want to put it down before the long tail fragments further.

The piece that pushed me over the edge was the recent Juejin Cursor 顶流 piece that walked through nine alternatives in the same sequence I keep seeing — Claude Code, Windsurf, Zed, Kiro, Antigravity, Fusion, Void, Trae, and Codex — and tried to pick a winner by mapping each onto a four-axis card none of them were designed for. The earlier roundup that triggered it listed four of the same names and produced almost the same Cursor-plus-Claude Code pairing. To be fair the 2026 piece is more honest — the author admits the four axes were chosen because the alternatives no longer share a common workload — and I am taking the exact verdict with a grain of salt, but the structural standoff is what has been rattling around in my head. A year of roundups later, the headline pick is identical and the menu of alternatives has multiplied and forked into philosophies that no single scorecard can rank.

The meta-pattern I want to call out is that the 2025 roundups and the 2026 roundups have converged on the same Cursor-plus-Claude Code answer at exactly the moment when the alternative survey expanded from four tools to nine, and the agreement at the top is hiding the disagreement underneath. The 2025 roundups surveyed Cursor, Claude Code, Augment, and Windsurf — three IDE-shaped tools plus one terminal agent. The 2026 roundups survey Cursor, Claude Code, Windsurf, Zed, Kiro, Antigravity, Void, Trae, Codex, OpenCode, Qoder, and Gemini CLI, and they are not all the same kind of thing. Void is open source. Zed is speed-first. Kiro is spec-driven. Antigravity is a project manager with a browser extension. Qoder is a project-wiki IDE. Trae is a free ByteDance clone. OpenCode is the BYOK model-swapper. Honestly I am a little skeptical of any AI tool roundup that flattens open source versus proprietary, agent terminal versus AI IDE, spec-driven versus chat-driven, free versus twenty dollars versus two hundred dollars into the same table and then ranks them against Cursor like they are competing in the same category, because what the long-tail split is really telling me is that the roundups have ossified a ranking framework for a category that has already splintered into at least four incompatible reader jobs, and reader agreement on Cursor plus Claude Code has replaced reader insight into which alternative fits a specific workflow. The two long tails that have grown the most are the open-source BYO-model camp and the spec-driven enterprise camp, and neither shows up in the roundup dismissal sentences.

The practical takeaway I want to put down is that the 2026 roundups are good for one narrow job and not useful at all for the other job most readers think they are doing. They are good at the top-pair confirmation job, because every post corroborates that Cursor plus Claude Code is the day-to-day plus heavy-lift combo. They are good at the category-baseline job, because Cursor Pro at twenty dollars, Claude Pro at twenty dollars, GitHub Copilot at ten dollars, and Trae at free are the four anchors and they show up with the same dollar precision. They are not good at the alternative-selection job, because the long tail has bifurcated into four reader personas — open-source maxis who want Void or OpenCode, enterprise spec-driven teams who want Kiro or Qoder, speed-focused single-developer users who want Zed, and free-tier readers who want Trae or Antigravity — and the roundups still rank all four against Cursor on the same axes. Give it six months and I expect one of two things: either the roundups publish four independent top-three lists, or the long tail consolidates back below five tools because the free-tier options quietly stop being free. I want to actually try Void and OpenCode for a month to see if the BYOK workflow is real or just philosophical.

I will reassess in three months. The last time I said that I was mostly on Cursor and Claude Code for coding and ChatGPT for everything else, which is still roughly where I land, and the monthly bill is roughly where I expected it. What has changed is that I now read the Juejin long-tail surveys as four different reader-job shortlists stapled together, and I sort by reader job before I read the dismissal sentences, and I skip the verdict paragraph because the Cursor-plus-Claude Code recommendation has been true for so long it no longer tells me anything I did not already know.