Skip to content

#大佬观点

1 today

Apr 17Friday

Dwarkesh Patel

Jensen Huang Makes the Case for Selling Chips to China

Jensen Huang argues the US should keep selling AI chips to China, saying China is about 40% of the global tech industry and abandoning that market weakens the US stack and developer base. He says a DeepSeek model optimized for Huawei first would disadvantage the US, and that Nvidia wins on compute, programmability, and ecosystem. The key issue is ecosystem lock-in, not a single export ban alone.

Why it matters: High-signal commentary from Nvidia's CEO on export controls: HKR-H comes from the contrarian China-sales frame, HKR-K from the 40% market claim and Huawei-optimization mechanism, and HKR-R from ecosystem-share anxiety. Kept below 80 because this is a short opinion clip, not a new

最佳拍档 (BestPartners)

Turn your coworker into a Skill? GitHub viral project and Anthropic Skills explained

The video says the open-source “coworker.skill” project gained over 13,000 GitHub stars in days, but it produces a standardized SKILL.md prompt package, not a digital worker replacement. It gives a timeline: Anthropic launched Claude Skills on Oct 16, 2025, then published Agent Skills as an open standard on Dec 18; the mechanism keeps only a short summary in context until a task matches. The real point is scope: it fits standardized workflows like reports, docs, and code review, while the post does not disclose cross-platform compatibility rates or any settled legal standard.

Why it matters: This clears HKR-H/K/R: the coworker-to-Skill hook is sticky, the post adds dates/stars/mechanism, and the labor/IP angle resonates. I kept it at 76 because it is secondary commentary, not a primary release or first-hand test, and key compatibility/legal facts are still undiscolse

Hacker News front page

The Beginning of Scarcity in AI

Nvidia Blackwell GPU rental prices rose from $2.75 to $4.08 per hour in two months, a 48% jump, signaling tighter AI compute supply. The post adds that CoreWeave raised prices 20% and extended minimum contracts from one to three years, while Anthropic limited its newest model to about 40 organizations. The real signal is procurement and capacity allocation, not model scores alone.

Why it matters: This clears HKR-H/K/R because it ties a strong scarcity angle to hard numbers: Blackwell rent up 48%, CoreWeave up 20% with 3-year minimums, and Anthropic limiting access to ~40 orgs. Importance stays below P1 because it is synthesized commentary, not a primary disclosure.

X · @dotey

Boris Cherny shares practical tips from recent heavy use of Claude Opus 4.7

Boris Cherny outlined five ways to use Claude Opus 4.7, centered on Auto mode approving safe commands and a /go skill chaining tests, code simplification, and PR creation. The post names Auto mode, Recaps, Focus mode, effort level, and computer use; pricing, launch date, and benchmark data are not disclosed. The real shift is workflow, not just the model itself.

TechCrunch · AI

AI traffic to US retailers rose 393% in Q1, and it’s boosting their revenue too

Adobe says AI traffic to U.S. retail sites rose 393% year over year in Q1 2026. The post also cites 269% growth in March and 693% during the holiday season, and says AI-referred shoppers converted better and drove more revenue, but it does not disclose the lift in conversion or revenue.

Why it matters: HKR-H/K/R all pass: the 393% stat is clickable, the story adds concrete growth numbers, and the real signal is AI becoming a retail distribution channel. Score stays in the low featured band because this is second-hand reporting on Adobe data, and the post does not disclose exact

Apr 16Thursday

Ben's Bites

My cheatsheet for a clean context

Ben's Bites publishes a context-management cheatsheet, arguing agents should stop near 60% context usage and stating he does not trust 1M-token windows for stable recall. His concrete tactics are to use separate sessions for context gathering, compress many docs into one summary file, and run Gemma 4 26B offline with no-skills to reduce local startup load. The sharp point is context pollution: web search results, AI slop, and misinformation compound over long sessions.

Why it matters: Strong HKR-H/K/R: the 60%-context rule and distrust of 1M-token memory are clickable, concrete, and relatable for agent users. Score stays mid-featured because this is a first-person workflow note, not a product launch, paper, or externally validated dataset.

Hacker News front page

AI cybersecurity is not proof of work

antirez argues AI bug finding is bounded by model intelligence level I, not by brute-force sampling alone; for the same code, execution paths eventually saturate. His concrete example is the OpenBSD SACK bug: weaker models fail even with unlimited tokens because they do not connect window validation, integer overflow, and the NULL branch. The key variable is model quality and access speed, not just more GPU.

Why it matters: High-quality commentary with HKR-H from the contrarian headline, HKR-K from the OpenBSD SACK mechanism and firsthand test, and HKR-R because it hits the 'more sampling vs better models' debate in AI security. Not a product, research release, or multi-source event, so it stays mid

Latent Space

[AINews] RIP Pull Requests (2005-2026)

GitHub is, for the first time 21 years after pull requests emerged, letting open-source repos disable PRs; the post frames this as a signal that AI coding workflows are changing collaboration. It gives a 2005-to-2026 timeline and cites agent stacks from OpenAI and Cloudflare as pressure toward prompt-driven contributions and sandboxed execution; the real question is whether Git-based workflows still fit agent collaboration.

Why it matters: This is not a primary GitHub announcement, but it turns one concrete change—open-source repos can disable PRs—into a sharp workflow question for agent coding. HKR-H/K/R all pass; the score stays mid-featured because the excerpt lacks scope, adoption data, and primary-source GitH​

X · @dotey

Recommended reading: Ruoshi's blog argues the model is not dumb, the harness is misconfigured

Ruoshi’s blog attributes multi-step agent failures to harness design, not model ability, and lays out four engineering rules plus a one-day minimum setup. The post cites failures after context exceeds 70%, log compression from 32K to 7K tokens, external state in state.json, schema validation, and local retries; the post does not disclose quantified success-rate gains. What matters for practitioners is execution constraints, externalized state, and independent evaluation rather than more prompt tuning.

Why it matters: HKR-H lands on the contrarian hook: agent failure is blamed on harness design, not model IQ. HKR-K and HKR-R land via concrete knobs—70% context threshold, 32K→7K logs, external state, schema retry—but this is still a reposted recommendation with no disclosed win-rate lift.

最佳拍档 (BestPartners)

Post-AGI may arrive within 50 years: Demis Hassabis on AlphaFold, three AI risk classes, and human value

Demis Hassabis said in a 1-hour interview that post-AGI scenarios can arrive within 50 years, while AGI should stay in labs for another 10-20 years. He cited concrete numbers: AlphaFold has been used by 3M+ scientists, Isomorphic Labs is running 18-19 drug programs, and the most urgent risks in the next 2-4 years are misuse and agent misalignment.

Dwarkesh Patel

Jensen Huang: Will Nvidia's moat persist?

Jensen Huang says Nvidia's moat is the hard-to-copy stack that turns electrons into tokens, plus supply-chain coordination, not chip design alone; the interview cites nearly $100B in disclosed purchase commitments, and a SemiAnalysis report estimating $250B. He grounds that in two mechanisms: explicit and implicit upstream commitments across foundry, HBM, and packaging, and a downstream ecosystem tying model builders, OEMs, and developers together; he also says agent growth will drive more usage of software tools.

Why it matters: Authoritative first-person thesis from Jensen on Nvidia's moat, with a near-$100B commitment figure and a concrete upstream/downstream coordination model; HKR-H/K/R all pass. Score stays at 77 because this is strong commentary, not a new product, earnings, or research release.

Apr 15Wednesday

最佳拍档 (BestPartners)

Will OpenClaw Go Closed Source? Peter Steinberger on OpenClaw at AI Engineer

Peter Steinberger said at the April 9, 2026 AI Engineer event that OpenClaw will not go closed source; the project reached nearly 30,000 commits and almost 2,000 contributors in 5 months. The talk says OpenClaw logged 1,142 security reports, 99 marked critical, 469 public with a 60% closure rate, and Fast Mode cut his parallel sessions from nearly 10 to 5-6. The key signal is the operating model: local-first, model-neutral, and a foundation for security maintenance; the post does not disclose a release date or implementation details for Dreaming.

Why it matters: HKR-H/K/R all pass: the close-source question is a strong hook, and the talk adds concrete stats on contributors, advisories, and Fast Mode. The score stays near the featured floor because this is a YouTube recap, and several teased items lack mechanism or release details.

Apr 14Tuesday

最佳拍档 (BestPartners)

Global GPU shortage worsens: H100 rental prices rose nearly 40% in five months

SemiAnalysis says Nvidia H100 one-year rental pricing rose from $1.70 to $2.35 per GPU-hour between Oct 2025 and Mar 2026, up nearly 40% in five months. The post attributes this to Anthropic-driven demand, multi-agent and media generation workloads, and memory cost spikes, with LPDDR5 and DDR5 contract prices up about 4x and 5x year over year; much new capacity is already prebooked. The key variable is the supply gap, not Blackwell refreshes alone.

Why it matters: Strong HKR-H/K/R: the story has a sharp price-shock hook, concrete market data, and clear resonance with compute-cost anxiety. It stays below P1 because this is a secondary video synthesis of a SemiAnalysis report, not a primary company or product announcement.

X · @dotey

Rather than AI First, this is really Software Engineering First

The post argues “AI First” is an engineering problem: if AI writes code in 2 hours, review, testing, deploy, monitoring, and rollback must also run automatically, with humans kept at key decision points. Its concrete prerequisites are automated tests, CI/CD, A/B testing, production monitoring, task management, and a clear architecture; without them, a 25-person team just shifts bottlenecks from coding to QA and ops. The real boundary is use case fit: API services, data platforms, and internal tools fit better than complex UI, core products, or high-security systems.

Why it matters: This is a strong practitioner commentary rather than a news event. HKR-H lands on the contrarian framing, HKR-K on concrete prerequisites and scope limits, and HKR-R on the bottleneck-shift argument; it stays in the mid-70s because there are no named cases, first-person tests, or

OpenAI News

Trusted access for the next era of cyber defense

OpenAI published an article titled “Trusted access for the next era of cyber defense,” focused on trusted access for the next phase of cyber defense. Only the title is available here and no body text is provided, so the confirmed details are limited to its emphasis on “trusted access” and “cyber defense.”

Why it matters: OpenAI gives concrete TAC scale—thousands of verified defenders and hundreds of critical-software teams—and explicitly ties it to GPT-5.4-Cyber and an upcoming release. HKR is 3/3, but the excerpt cuts off model specs, evals, and access details, so this is strong featured, not p1

X · @dotey

Developer Can Vardar says disabling telemetry in Claude Code cuts prompt cache from 1 hour to 5 minutes

Can Vardar said disabling telemetry in Claude Code drops prompt cache from 1 hour to 5 minutes; Anthropic engineer Boris Cherny said the client then falls back to the 5-minute default because experiment flags stop working. The post says 1-hour cache costs more to write and less to read, so value depends on reuse; Anthropic plans env vars to force 1 hour or 5 minutes.

Why it matters: Strong HKR-H/K/R: the privacy-vs-performance tradeoff is a sharp hook, and the post adds concrete TTL and cache-cost mechanics. It scores as high featured because it affects real Claude Code usage decisions, but not P1 because this is an engineer clarification on X, not a formal,

Apr 13Monday

最佳拍档 (BestPartners)

2027 Is the Enterprise AI Singularity Year: Sundar Pichai on 10 Years as Google CEO, Transformer and Search

Sundar Pichai said in a Stripe interview that Alphabet plans $175B-$185B in 2026 capex and that 2027 will be the breakout year for enterprise AI agent workflows. He said Google cut Search latency by 30% over five years while adding AI features, manages teams with 10 ms or 30 ms latency budgets, and sees 2026-2027 constrained by wafers, memory, power, and permitting. The point to watch is not search replacement but search evolving into an agentic manager, while TPU allocation has become Google's scarcest internal resource.

Why it matters: High-signal executive commentary rather than a product launch. HKR-H/K/R all pass on the 2027 agent call, concrete capex and latency details, and the search-plus-compute nerve hit; score stays below P1 because this is a second-hand recap, not the primary interview.

Apr 11Saturday

X · @dotey

OpenAI Codex team's Nick Baumann: build dedicated CLI tools for AI instead of feeding messy data repeatedly

OpenAI Codex engineer Nick Baumann says teams should wrap repeated data access into parameterized CLI tools with JSON output instead of repeatedly dumping logs, docs, and API responses into Codex. The post lists 3 examples in daily use: codex-threads for past sessions, slack-cli for threaded Slack search, and typefully-cli for posting workflows; access still goes through the existing auth gateway. The point for practitioners is narrower interfaces: models handle focused commands more reliably than raw, noisy source data.

Why it matters: This is a practical workflow note from an OpenAI Codex team member, not a formal launch, but it offers a reusable mechanism: wrap noisy context behind parameterized JSON-returning CLIs and shows 3 live examples. HKR-H/K/R all land; no benchmark, scale, or major product release,so

Apr 8Wednesday

MIT Technology Review · AI

Mustafa Suleyman: AI development won’t hit a wall anytime soon—here’s why

Mustafa Suleyman argues frontier AI training compute rose from about 10^14 to over 10^26 FLOPs since 2010, a 1 trillion-fold increase, so AI development is not near a wall. He cites a 7x Nvidia chip gain in six years, 3x more HBM3 bandwidth, and Epoch AI estimates that compute needed for fixed performance halves every eight months. The piece is commentary from Microsoft AI’s CEO, not an independent study; the post does not disclose a reproducible basis for the 200GW-by-2030 claim.

Why it matters: HKR-H/K/R all pass: Suleyman takes a hard line in the scaling-wall debate and cites 10^26 flops, 7x chip gains, 3x bandwidth, and 8-month efficiency halving. Held at 82 because this is executive commentary, not independent research, and the 2030 200GW math is not disclosed.

Latent Space

Extreme Harness Engineering for Token Billionaires: 1M LOC, 1B toks/day, 0% human code, 0% human review

OpenAI Frontier says it built an internal beta over five months with a repo above 1M LOC, over 1B tokens per day, and 0% human-written or human-reviewed code before merge. The post says the team treated failures as missing capability, context, or structure, then used Symphony orchestration, specs, tests, observability, and sub-1-minute build loops to constrain Codex. The shift to watch is from humans reviewing code to humans designing the harness; the $2k-$3k/day cost is cited secondhand in the post.

Why it matters: HKR-H/K/R all pass: the headline is clickworthy, and the piece includes concrete workflow details plus scale numbers. It stays below p1 because this is an interview-style report, not an official launch, and key claims like 1B tokens/day and cost lack independent verification.

Apr 7Tuesday

MIT Technology Review · AI

The one piece of data that could actually shed light on your job and AI

University of Chicago economist Alex Imas argues that AI job displacement depends less on task exposure and more on industry-level price elasticity data; the piece cites OpenAI estimating real estate agents as 28% exposed. It adds that the US task catalog started in 1998, and Anthropic compared it with millions of Claude chats in February. The key variable is whether lower prices raise demand enough, and the post does not disclose any economy-wide dataset yet.

Why it matters: Strong HKR-K: it reframes job impact around price elasticity, with concrete anchors like OpenAI's 28% exposure for real-estate agents and Anthropic's O*NET-to-Claude mapping. HKR-R is clear because it hits job displacement anxiety, but this is commentary, not a fresh dataset or a

Apr 6Monday

X · @dotey

Xiaomi MiMo lead Luo Fuli on token costs in the Agent era

Luo Fuli said Agent workloads can resend 100k+ tokens across repeated tool calls, and global compute cannot keep up with that burn. She said OpenClaw makes several times more requests than Claude Code and can push real API cost to tens of times the subscription price; the post does not disclose a pricing formula.

Why it matters: A named Xiaomi MiMo lead makes a concrete, testable critique of agent cost: 100k+ token context replay, multi-tool-call overhead, and several-times request inflation vs Claude Code. HKR-H/K/R all pass, but missing public benchmark setup and pricing keeps it at the low end of the

Apr 4Saturday

Latent Space

Marc Andreessen introspects on The Death of the Browser, Pi + OpenClaw, and Why “This Time Is Different”

Marc Andreessen argues in a 76-minute interview that this AI cycle differs from 2016 because of reasoning, coding, agents, and recursive self-improvement. The post gives one concrete mechanism: Pi/OpenClaw as LLM + shell + filesystem + markdown + cron loop; it mentions “death of the browser,” but does not disclose a verifiable timeline or product plan. The sharper point is his Unix-like framing of file-backed agent state and portability.

Why it matters: This is a strong commentary piece, not a market-moving event. HKR-H comes from the browser-death hook, HKR-K from the Pi+OpenClaw mechanism, and HKR-R from the interface/distribution nerve; lack of roadmap, metrics, or launch details keeps it at the low end of featured.

Apr 3Friday

X · @op7418

Karpathy shared how he builds a local AI knowledge base

Karpathy uses Obsidian and local Markdown to build a personal wiki, stores source material in a RAW folder, then has an LLM generate summaries, indexes, concept pages, links, and visualizations. The setup can answer questions over the wiki and write reports or new files, but the post also says AI-generated content can pollute the corpus and should be separated from trusted sources; the post does not disclose the model, scale, or automation details.

Why it matters: HKR-H and HKR-R land because Karpathy’s local-first wiki workflow is inherently clickable and discussable for AI practitioners. HKR-K lands on the RAW→LLM→summary/index/link mechanism, but missing model, corpus size, and automation details keep it in the mid-70s.

X · @dotey

LatePost on DeepSeek before V4: traits, organization, and Liang Wenfeng's goals

LatePost says DeepSeek has confirmed 4 core departures, and V4's large model slipped from around Lunar New Year to April; the report says it will likely remain open source. The snippet cites 2x-3x recruiting offers, some 8-digit packages, a 100-plus research team, and a shift from CUDA/Triton to TileLang for domestic GPU adaptation. The real signal is strategy: DeepSeek had spent less on agents and coding, but now names an agent product role; the post does not disclose V4's size, price, or benchmarks.

Why it matters: This is not the V4 launch, but it carries real signal: four confirmed departures, an April delay, a 100+ research team, and partial migration from CUDA/Triton to TileLang. HKR-H/K/R all pass; missing V4 specs, price, and benchmarks keeps it below launch-tier or p1.

Apr 1Wednesday

MIT Technology Review · AI

The gig workers who are training humanoid robots at home

Micro1 hires thousands of contractors across 50+ countries to film chores at home with iPhones and sell that real-world data to humanoid robotics companies. The piece cites $15/hour pay for one worker, says robotics firms spend over $100 million a year on such data, and notes $6 billion+ went into humanoids in 2025. The real issue is data governance: workers know the footage trains robots, but the post shows they often do not know how it is stored, shared, or deleted.

Why it matters: This clears HKR-H/K/R: at-home chore videos are a strong hook, and the piece adds numbers on scale, pay, and spend. The sharper industry signal is the hidden data pipeline and weak governance on storage, sharing, and deletion, so it merits featured, not p1.

TheValley101 (硅谷101)

E231 | From B2B to A2A: What Agent Infrastructure Could Do for a One-Person Global Business

Alibaba International president Zhang Kuo said procurement agent product Accio reached 10 million MAU in March and is still growing quickly month over month. The interview’s clearest metric: AI cuts procurement communication time to one-fifth, from about one week to one day, by chaining research, design-pack generation, cross-language communication, and supplier screening into an agent workflow. The real point is A2A: the post frames it as agents restructuring buyer, seller, and platform flows, not just a better chat box.

Why it matters: This is not a major launch, but it is a primary-source exec interview with concrete numbers: 10M MAU and a 1 week→1 day cycle cut. HKR-H/K/R all pass, yet the event is still below a model release or major product update, so it lands in featured, not p1.

Mar 31Tuesday

OpenAI News

Accelerating the next phase of AI

OpenAI published a post titled "Accelerating the next phase of AI." The provided content includes only the title and URL, with no body text, so no specific product, research, or policy details can be verified.

Mar 26Thursday

TheValley101 (硅谷101)

E230 | Behind the $1 trillion revenue forecast: NVIDIA's peak and weak spots

Jensen Huang said at GTC that NVIDIA expects at least $1 trillion in cumulative orders for Blackwell and Vera Rubin by the end of 2027, above the roughly $600B global semiconductor market in 2024 cited in the episode. The discussion adds that Vera Rubin launched 7 chips at once, NVL72 delivers 10x inference efficiency over Blackwell, cuts cost per token to one-tenth, and improves token per watt by 35x; the real constraint discussed is CoWoS, HBM4, and power capacity, not demand alone.

Why it matters: This is a solid GTC follow-up, not a pure keynote recap. HKR-H comes from the '$1T vs weak spots' frame, HKR-K from concrete figures and bottleneck details, and HKR-R from infra-cost and supply-chain nerves; featured, but not p1, because it is commentary rather than a new product

Mar 25Wednesday

MIT Technology Review · AI

The AI Hype Index: AI Goes to War

An MIT Technology Review Hype Index item says Anthropic, OpenAI, and the Pentagon are competing over military AI use, with “AI goes to war” as the core claim. The RSS snippet names Claude, ChatGPT, OpenClaw, Moltbook, and RentAHuman, but the post does not disclose deal size, timeline, protest scale, or contract terms. The real signal is how fast model vendors are binding themselves to defense systems.

Why it matters: Featured at the floor on HKR-H + HKR-R: frontier model vendors tied to Pentagon use is a strong hook and a real industry nerve. HKR-K is thin because the summary gives no contract value, timeline, or cooperation terms.

Mar 24Tuesday

Lex Fridman (YouTube RSS)

Jensen Huang: NVIDIA - The $4 Trillion Company & the AI Revolution | Lex Fridman Podcast #494

Jensen Huang said on the Lex Fridman podcast that NVIDIA uses “extreme co-design” for AI clusters, aiming to beat linear scaling across 10,000 computers. The interview cites Amdahl’s Law, model and data sharding, networking, power, and cooling as hard constraints; Huang also said he has 60+ direct reports. The key shift is that NVIDIA now competes at rack and data-center level, not only at single-GPU level.

Why it matters: A strong primary-source interview with clear HKR-H/K/R: a high-click hook, concrete system-scaling details, and direct relevance to the infra moat debate. It stays below 85 because this is analysis from a podcast, not a new product, personnel move, or fresh market-reported data.

Mar 19Thursday

Ben's Bites

What makes a good AGENTS.md?

Ben's Bites says AGENTS.md should keep only behavior preferences, not tech-stack maps or key files; the post cites a study saying that hurts performance and raises cost by 20%. It recommends symlinking AGENTS.md to CLAUDE.md, using conditional blocks, and relying on folder-level dynamic loading; the study name and setup are not disclosed. The real point is not more context, but smaller persistent instructions.

Why it matters: This is a practitioner explainer for coding-agent users, not a product launch. HKR-K and HKR-R pass on the concrete 'keep AGENTS.md small' claim, the 20% cost figure, and usable patterns; HKR-H is weak, and the cited study name and setup are not disclosed, so it sits at the low '

TheValley101 (硅谷101)

Web3 101 Crossover: How to Prevent System-Level Risks Behind the OpenClaw Craze

Yuxian said OpenClaw has issued about 250 security advisories, and v3.2 added stricter defaults, yet broad permissions, network access, and Skill installs still expand risks like file deletion, data leaks, and loss of control. The discussion breaks risk into layers: readable local files, chat data sent upstream, logged-in browser sessions, malicious links or Skills, and automated tasks that fail repeatedly. The practical rule is isolation: separate devices or networks, local-only access or Tailscale, and strict caution with external inputs.

Mar 17Tuesday

MIT Technology Review · AI

Where OpenAI’s technology could show up in Iran

Just over two weeks after OpenAI’s classified-use deal with the Pentagon, MIT Technology Review outlined three places its tech could surface in Iran-related conflict. The post names target prioritization, Anduril counter-drone analysis, and GenAI.mil back-office use; it does not disclose when classified integration will finish or confirm deployment in Iran.

Why it matters: MIT Technology Review maps OpenAI’s classified-defense deal to 3 Iran-linked scenarios, giving it strong HKR-H and HKR-R. HKR-K is weaker because the piece does not confirm deployment, integration timing, or system limits, so it lands at the featured floor.

Mar 16Monday

MIT Technology Review · AI

Nurturing agentic AI beyond the toddler stage

The article says no-code tools and the open-source agent OpenClaw pushed agentic AI into a more autonomous stage between Dec. 2025 and Jan. 2026. It cites California AB 316 taking effect on Jan. 1, 2026, so firms cannot dodge liability by blaming AI, and an IDC survey sponsored by Data Robot reporting 96% of generative AI deployments and 92% of agentic AI deployments cost more than expected. The real issue is workflow-level governance: permission drift, orphaned agents, long-lived tokens, and sessions that can reach $100,000.

Mar 13Friday

Ruan YiFeng's Weblog

Tech Enthusiast Weekly #388: Testing Is the New Moat

A Cloudflare engineer used AI to reimplement Next.js as vinext in 1 week, with $1,100 in token cost and 94% API coverage. The post cites early benchmarks: 4x faster builds and 57% smaller client bundles, with production Next.js apps already running on it. The sharper point is testing: SQLite has 156k lines of code, 92.05M lines of tests, and keeps its core TH3 suite closed.

Mar 11Wednesday

MIT Technology Review · AI

Hustlers are cashing in on China’s OpenClaw AI craze

Beijing engineer Feng Qingyang turned OpenClaw installation support into a 100+ person business after starting in January, handling 7,000 orders at about RMB 248 each. Taobao and JD now show hundreds of related listings priced at RMB 100-700; the real story is setup friction and data-isolation risk turning an open-source agent into a service market.

Why it matters: Featured. HKR-H/K/R all pass: the side-gig-to-100-person-team angle is clickworthy, the piece adds hard market numbers, and the data-isolation risk gives it real industry resonance. This is not a product launch, but it is strong field reporting.

Mar 9Monday

MIT Technology Review · AI

How AI Is Turning the Iran Conflict Into Theater

The author reviewed more than a dozen Iran-war dashboards in one week and argues they turn satellite data, ship tracking, AI summaries, and betting links into a real-time war spectator interface. The post cites a dashboard built by two Andreessen Horowitz staffers that pulls in Kalshi bets, while Craig Silverman has logged 20 similar dashboards. The point to watch is information quality: the piece cites Financial Times reporting on AI-generated satellite images spreading online, while these dashboards lack the human vetting and historical context used by intelligence agencies.

Why it matters: HKR-H lands on the war-dashboard-plus-betting hook; HKR-K lands on the named examples, counts, and Kalshi mechanism; HKR-R lands on reliability and ethics nerves for AI builders. Strong reported commentary, but not a product, model, or research milestone, so it ranks as featured,

Mar 6Friday

Ruan YiFeng's Weblog

Technology Enthusiast Weekly Issue 387: You Are Ahead

Ruanyifeng says that, out of 8.1 billion people, only 1.38 billion have used AI, or 16%; just 15 to 25 million pay for AI services, or 0.3%. The post adds that only 2 to 5 million people have used AI to create their own coding projects, or 0.04%. The real signal is the adoption gap, not the idea that everyone already uses AI.

Why it matters: This is data-backed commentary, not a product launch or primary reporting. HKR-H/K/R all pass: the angle punctures the 'everyone uses AI' narrative and supplies 16% / 0.3% / 0.04% adoption estimates, but the source basis is unclear here, so it sits at the low end of featured.

Mar 5Thursday

36Kr (direct RSS)

Alibaba Denies Mass Departure From Qwen Team, Says Team Stable and Services Normal

Alibaba said on March 5 that reports of a mass departure from the Qwen core team were false, adding that the team is stable and products and services are operating normally. It also said Qwen will keep its open-source strategy; the post does not disclose the rumor source, team size, or future investment amount. The key signal is Alibaba's statement that its foundation model team has never been given DAU-style commercialization KPIs.

Why it matters: HKR-H lands on the 'mass resignation' denial hook; HKR-K lands on three concrete signals: Qwen stays open-source, service is normal, and no DAU KPI is set. HKR-R is strong on talent and strategy nerves, but this is still a company rebuttal with no team-size or attrition data, so