AI Weekly Malaysia

Simon Willison argues that pay-by-usage APIs and services need default hard budget caps — the kind that cut off usage and return errors once a monthly limit is hit — rather than soft caps that only send a warning email. He points to AWS, which on 16 September launched a new experience where a project that reaches its monthly spend limit is paused for the rest of the month, and notes Google Cloud shipped similar 'Spend Caps' in July. Willison wants hard caps to be the default, with an explicit opt-in checkbox to remove them for people who accept the risk of a runaway bill.

Why: If you let coding agents or personal agents spin up paid APIs, hosted apps, or storage/compute on your behalf, check today whether your provider's cap is hard or soft — a warning email at midnight does not stop the meter. AWS's new spend limit pauses the project for the month, which protects your wallet but breaks your app, and the settings page warns the feature is only being released to a limited number of customers, so existing accounts likely cannot rely on it yet; Google Cloud's Spend Caps can be set per service within a project. Decide per project which you want: a hard stop, or an uncapped account you actively monitor.

Tom's Hardware reports that Micron now earns an 88% margin on consumer (client) memory, with profit driven by price hikes rather than volume. The same report notes Micron's client business was its only unit that shipped less memory this quarter, so revenue rose while units fell. Only the headline figures are visible in the supplied text — the rest of the page is paywall and newsletter boilerplate, so the underlying earnings numbers, segment definitions, and timeframe can't be verified from this excerpt.

Why: The profit is coming from price, not units shipped — fewer client memory units moved yet margin hit 88%. If that holds, the cost of DDR5 kits, SSDs, and the RAM tiers behind cloud and VPS instance pricing probably won't come down soon, so anyone speccing a dev machine, a local inference box, or a multi-year cloud commitment should assume current memory pricing is closer to a floor than a spike. Treat the 88% figure as a supplier-margin signal when you negotiate or budget, not as evidence of a demand boom.

Public backlash against power-hungry data centers has spread from the U.S. to Europe and Asia, with communities objecting over electricity, water and land use, and that opposition increasingly turning into project delays, tighter local regulation and financial risk for developers and investors. CNBC cites STL Partners research putting roughly $42 billion of European data center investment affected by delays and cancellations, versus about $77 billion in the U.S. In South Korea, opposition to data centers near residential areas is growing alongside proposals for tighter local restrictions, even as the national government pushes to accelerate development.

Why: If you buy cloud or GPU capacity, the concrete input here is that capacity growth is being slowed by local permitting fights in dense, high-electricity-price markets, not by chip supply alone — so multi-year commitments and spot pricing assumptions should carry some permitting/power risk. The article names no Malaysian or Southeast Asian market, so there is no local-specific number to act on; treat the $42 billion European figure as the only quantified signal and do not extrapolate a Malaysia figure from it.

AMD has published full specifications and pricing for its EPYC 9006 "Venice" (Zen 6) server CPU lineup, with the range running from $700 at the bottom to $14,904 for the top part — headlined as a 256-core chip at roughly the $15,000 mark. The excerpt itself contains only the headline claim; no core counts per SKU, clock speeds, TDPs, memory or PCIe details, benchmarks, or availability dates are included in the text provided.

Why: This is a pricing reference point, not a decision you can act on yet: a 256-core server part at about $14,904 implies roughly $58 per core at the top of the stack, which is the number to compare against your current cloud or bare-metal per-core rates when you next size an inference or build fleet. Because the article text carries no TDP, memory bandwidth, or availability details, do not plan a migration off this item alone — wait for independent benchmarks, since per-core price says nothing about per-token throughput.