ReadingResearchRadarInvestment framework
Sign in / Sign up
AllTechnologyProductsInvestingPublic marketsOther

Reading

2026-11-1517 posts

Refresh

Asian Governments React to Nvidia CEO Jensen Huang's Exit: Confirming Supply and Monitoring Investigations

Material
2026-11-15 00:34 GMT+8

The departure of Nvidia CEO Jensen Huang has triggered widespread reactions across Asia. Some governments have moved quickly to confirm chip supply commitments, while others are monitoring the impact on local projects or addressing ongoing investigations.

In South Korea, the Ministry of Science stated that Nvidia had reaffirmed its plan to supply 260,000 advanced GPUs to the country and to continue joint AI projects. Samsung Electronics and SK Hynix, major suppliers of memory chips for Nvidia's AI processors, maintain close ties with the company. Additionally, South Korea's government AI strategy council held an emergency meeting on Friday to assess the potential impact of Huang's departure on the country's AI industry.

In Singapore, the Ministry of Home Affairs confirmed that the investigation into Alice Huang, former CEO of Megaspeed, remains ongoing. Authorities seized her passport in June 2025 to investigate possible false declarations regarding server purchases. In February 2026, police found insufficient evidence to establish offenses related to these declarations but noted she knowingly provided inaccurate information about her role at Megaspeed. She was issued a warning and barred from re-entering Singapore. Singapore also mentioned receiving limited assistance from U.S. authorities despite repeated requests for information about server maker Supermicro.

In China, the Foreign Ministry rejected allegations linking a Chinese businesswoman to espionage as "groundless." A Reuters review indicated that Huang's exit has raised uncertainty over more than $3 billion in Chinese AI computing projects reliant on Nvidia's restricted processors. Many of these chips are subject to U.S. export controls, making them difficult for Chinese companies to obtain.

In Taiwan, Economy Minister Kung Ming-shin said Huang's departure was unlikely to significantly change the growth of the global AI industry. The Taipei city government stated that Nvidia's planned overseas headquarters in the city remained on track despite the leadership change, noting the company has met its contractual obligations so far.

In Japan, the Industry Ministry said the government would closely monitor Nvidia, describing the chipmaker as an important player in Japan's AI semiconductor industry. Deputy Chief Cabinet Secretary Masanao Ozaki said it was too early to assess the impact on the global AI industry, while stressing Japan's commitment to ensuring a stable supply of semiconductors.

Sources:TechCrunch

Research

Roundhill Investments CEO Dave Mazza and Yorkville Ives Partner Dan Ives: Nvidia Turmoil and Data Center Restrictions Boost Value of Compute and Alternative Chips

Material
2026-11-14 23:50 GMT+8

In the week when Nvidia founder and CEO Jensen Huang resigned, AMD shares rose nearly 13%, Broadcom posted similar gains, and the Nasdaq Composite recorded its best single-week performance since August. When one company encounters trouble, the entire sector strengthens—a seemingly contradictory market reaction that two AI-themed ETF managers view as an investment thesis worth explaining, rather than simple panic-driven rotation.

Dave Mazza, CEO of Roundhill Investments, proposed a core mechanism on CNBC's "ETF Edge": if investors lose trust in Nvidia, they will not stop buying AI chips but will instead turn to other suppliers for compute power. This means Nvidia's trust crisis creates a window for demand transfer to competitors in the short term. The Magnificent Seven ETF (MAGS) managed by Mazza closed the week up less than 1%, while the Roundhill Neocloud ETF (NCLD), which focuses on small- and mid-cap specialized cloud computing companies, rose more than 1%, despite having fallen cumulatively by 39% since its launch in August 2026.

Mazza further pointed out that hyperscale cloud service providers may benefit from Nvidia's difficulties because they already possess available compute infrastructure. With demand remaining constant and new supply constrained, the value of existing compute capacity rises.

Dan Ives, partner at Yorkville Ives, added a political dimension to the analysis. Following the U.S. midterm elections on November 3, 2026, where the Democratic Party gained control of Congress, Ives estimated that this political shift could prevent 10% of planned data centers from being built, with high-end estimates ranging from 15% to 20%. However, his conclusion was not bearish on AI compute; rather, he reasoned inversely: given that demand still exceeds supply by approximately four to one, tighter regulation makes existing compute scarcer and therefore more valuable. Before Nvidia's Q3 earnings report, Ives lowered his price target on Nvidia from $300 to $225 but maintained a buy rating, arguing that a valuation of roughly 10 times 2028 earnings per share remains too low.

The applicability of this argument comes with important caveats. First, the 4:1 supply-demand ratio is Ives' personal estimate and has not been independently verified. Second, the Neocloud ETF fell 39% just three months after its launch, indicating that not all market participants accept the linear logic that compute scarcity equals value enhancement—balance sheet pressures and ongoing concerns about Nvidia's role in financing AI infrastructure building may offset premiums derived from scarcity. Third, Nvidia's Q3 earnings are due soon; if its data center revenue is not significantly impacted, the urgency of the substitution logic will be weakened. Essentially, the managers' argument is a bet on asset repricing under supply constraints, not a denial of Nvidia's long-term competitiveness. Ives explicitly stated that Nvidia remains about two to three years ahead of competitors, and its strategic roadmap and chip development pace driven by 42,000 employees will not change due to the founder's departure.

Sources:CNBC

Research

Anthropic Expands into Enterprise Software, Raising Developer Concerns That the Platform Provider Is Becoming a Competitor

Material
2026-11-14 23:15 GMT+8

Scott Stevenson, CEO of legal AI company Spellbook, recounted an experience in a November 2026 interview with Forbes: Anthropic employees had assured him that the company had no plans to compete directly in the legal software market, before Anthropic launched Claude for Legal, which includes contract review features overlapping with Spellbook's core business. Stevenson did not abandon Claude—Anthropic still showcases Spellbook on its customer page today, reporting that its Claude-powered agents perform approximately 530,000 contract reviews per month. However, he drew a conclusion: 'Anthropic has been a great partner, but it made us realize they are a massive company and two parts of the org can have conflicting mandates.'

Gerald Zingraf, President and COO of GlacierGrid, expressed similar concerns on LinkedIn, comparing Anthropic's strategy to Amazon's private-label business. His worry is that Anthropic can see which third-party integrations customers use most frequently and potentially leverage that information when deciding which capabilities to build itself. 'Makes me nervous for wrappers and pure SaaS companies,' he wrote, citing his own experience selling design products on Amazon and then watching the retailer launch competing products.

Todd Saunders, CEO of Dalton Mills, posted on X after Anthropic launched Claude Code Review, directly stating that 'Anthropic is the new Amazon,' warning developers building on the Claude SDK that the company could observe application usage and eventually incorporate competing functionality into Claude.

These concerns point to a specific mechanism: Anthropic controls the interface between users and third-party applications. The November 10, 2026 announcement introduced Claude Sheets, Claude Whiteboards, and Claude Data, while previewing Claude Meetings. Expanded interactive connectors allow partners to embed applications directly inside Claude, with software from Adobe and Atlassian already included. This means Anthropic acts simultaneously as a technology supplier, an owner of the application distribution channel, and a potential functional competitor—the tension among these triple roles is structural, regardless of any single decision-maker's goodwill.

However, the article itself remains cautious regarding the strongest allegations. Regarding Zingraf's concerns, the author explicitly states that 'he provided no evidence that the company uses integration data to identify competitors or guide its product roadmap.' Regarding Stevenson's experience, the author similarly notes that 'Stevenson’s account does not establish that Anthropic used Spellbook’s proprietary information to develop its legal product.' Anthropic’s commercial terms stipulate that customers retain rights to their inputs and own their outputs, and the company agrees not to use customer content to train models; its commercial privacy documentation also clarifies that feedback data excludes content pulled through connectors (including local and remote MCP servers) unless users paste it directly into a conversation.

Sources:The New Stack

Research

DuckLake Lead Developer: Treat Metadata as a Relational Database Problem, and Lakehouse Queries Become Just Catalogs and Parquet Files

Material
2026-11-14 23:45 GMT+8

Traditional lakehouse formats split metadata into numerous manifest files scattered across object storage. For every query, the engine must traverse these files to determine which Parquet data files to read. Pedro Holanda, lead developer at DuckLabs, argues that this is essentially a relational database problem that does not need to be solved using file system methods.

His explanation is straightforward: you issue a query, and the server answers with which Parquet files to read. The Parquet files themselves do not change; only the catalog changes. This is why DuckLake stores table metadata in a standard SQL database rather than scattering manifest files. Users are already familiar with SQL and schemas, so they do not need to learn an additional logic for traversing metadata.

DuckLake 1.1 was released in October alongside DuckDB 2.0.0 LTS, bringing file compaction and inline/flush mechanisms tailored for streaming data lakes. Regarding file compaction, when the number of files becomes excessive, DuckLake can merge multiple files into one to reduce request counts; this operation can span multiple snapshots, further compressing the total file volume. Regarding inlining, actual data representations are stored directly as tables within the catalog. Holanda stated that while building DuckLake, they realized that since they already had a database system and a catalog, why not store the data itself in tables?

This resolves the small-file problem in streaming scenarios. When multiple data sources write simultaneously, traditional lakehouses generate a large number of fragmented files. Queries then require traversing metadata and reading many small Parquet files, slowing down both processes. DuckLake absorbs these fragments into the catalog through inlining and flushing, deferring compaction operations until they are needed.

Weston Pace, an engineer at LanceDB, supplemented DuckLake's design trade-offs from the perspective of concurrent writes in another technical blog post. He categorized table-format coordination mechanisms into two types: zero-infrastructure atomic operations (relying on cloud storage's 'put-if-not-exists' semantics, requiring no extra services but limited to approximately ten commits per second) and centralized coordination (where DuckLake uses a Postgres instance as a commit coordinator, synchronizing writers via mutexes or CAS primitives). Centralized schemes may achieve higher transaction rates and apply to filesystems that do not support atomic creation, at the cost of maintaining a long-running service.

Both DuckDB and DuckLake are open-source under the MIT license, overseen by the independent DuckDB Foundation. DuckLake can run without massive server clusters, partly because the Parquet and DuckDB storage formats are naturally similar—both are columnar and organized by row groups, minimizing data movement steps.

Sources:The New Stack

Research

US Treasury Secretary Questions Whether Nvidia Knowingly Sold AI GPUs to Shell Companies, Calls for Internal Accountability

Material
2026-11-14 23:35 GMT+8

US Treasury Secretary Scott Bessent recently questioned in a CNBC interview whether Nvidia knowingly sold restricted AI graphics processing units (GPUs) to shell companies. He pointed out that despite strict US export controls, a significant amount of restricted hardware still reaches competitors like China through intermediaries.

Bessent emphasized that the issue should not focus solely on the personal actions of Nvidia CEO Jensen Huang, but rather on whether Nvidia knew its clients and had robust internal measures to prevent such "leakage." He stated, "I think it is important that anyone at the company there be held accountable for that."

He also criticized Nvidia's General Counsel Timothy Teter, who reportedly contacted the US Department of Commerce to inquire about authorities' involvement in detaining Megaspeed's Alice Wong in Singapore. Bessent argued that Teter should have focused on strengthening internal oversight rather than haranguing government officials. However, Bessent acknowledged that it remains unclear whether Huang himself was aware of these potentially illicit activities.

Additionally, Bessent revealed that the Departments of the Treasury, War, and State, along with the Office of the US Trade Representative (USTR), had supported adding Megaspeed to the Entity List for months. However, the Bureau of Industry and Security (BIS) under the Department of Commerce delayed this action due to concerns about worsening trade tensions with China.

Sources:Tom's Hardware

Research

You’re all caught up in this view

Sign in / Sign up
ReadingResearchRadarInvestment framework

However, these terms do not answer a critical question: how Anthropic uses aggregated integration data. The privacy policy acknowledges the company's right to access information about how customers interact with third-party apps and services, but does not explain whether this data influences product decisions. The article concludes that developers accept a trade-off: gaining access to Anthropic’s expanding enterprise customer base comes at the cost of Anthropic controlling the interface, allowing it to introduce competing features without consulting the developers who depend on it.

For developers evaluating whether to build products on frontier models, this article provides not a conclusion but a framework: platform risk depends not on the supplier's current promises, but on its capability structure and incentive direction. Stevenson’s judgment that 'ultimately this is inevitable' is worth incorporating into decision-making considerations more than any specific product release.