AI Weekly Malaysia

Alphabet shares sank 10% as the company held 2026 capex unchanged and said it expects a significant increase in 2027. The Q3 2026 report arrived with consensus at $3.02 EPS and $128.2B revenue, up 25% year over year, while July capex guidance was $195B–$205B and free cash flow had turned negative for the first time.

Why: If you are planning AI features or cloud commitments, the key detail is that Alphabet is not pulling back 2026 infrastructure spend—$195B–$205B—and expects to spend significantly more in 2027, so do not bank on a near-term compute glut or cloud price relief from this signal.

Google said on its Q3 2026 earnings call that it is expanding ads in AI Mode and AI Overviews to international markets for the first time, alongside multi-turn ads in the U.S. Alphabet reported $127.6B revenue, up 25% year over year, but Search ad growth slowed to 12% from 17% in Q2 and 19% in Q1, and shares fell 8%. Google says sponsored product listings in AI Mode already have click-through rates comparable to organic listings, and AI Mode queries are three times longer on average than traditional search.

Why: If you buy Google search traffic or depend on search acquisition, this signals new sponsored placements inside AI answers beyond the U.S.; test whether AI Mode placements add incremental conversions or cannibalize existing campaigns, and prepare for longer conversational queries rather than short keyword-style ones. Check your own Google Ads account for country availability before budgeting, since the text says international markets but does not name Malaysia.

Apple’s new 14-inch and 16-inch MacBook Pro with touch-enabled PROLED XDR OLED display, M5 Pro/M5 Max chips, thinner design, and returning illuminated Apple logo starts from RM11,999 in Malaysia. Pre-orders open at 9am on Friday, 30 October 2026, with availability from Friday, 6 November 2026. The new OLED models cost RM1,700 more for the 14-inch and RM2,000 more for the 16-inch versus the still-sold mini-LED MacBook Pro, while base configurations include 24GB unified memory and 1TB SSD.

Why: If you are choosing a Mac for local development in Malaysia, the concrete decision is whether the touch/OLED premium is worth RM1,700–RM2,000 over the existing mini-LED models, which Apple will keep selling. The base 24GB/1TB configuration matters for local builds and agent workloads, and the top 16-inch spec reaches RM64,174, so budget allocation between display, RAM, and SSD is the practical trade-off.

According to Tom's Hardware, Amazon has issued new internal guidelines telling engineers to stop "tokenmaxxing" — inflating AI token consumption to appear productive — while stating that AI will remain central to software development and that usage volume is not the goal. The item as supplied is headline-level only: the article body available here is site navigation and subscription boilerplate, so there are no specifics on which metrics Amazon substitutes, which teams the guidelines cover, or any quoted numbers.

Why: If your team has been treating token counts, AI-seat adoption, or prompt volume as a productivity signal, this is a direct counter-signal from a large engineering org: consumption is not output. Concretely, that means don't put API spend or token totals on a performance dashboard — and if you're a founder justifying AI tooling cost, tie the spend to shipped artifacts and review throughput instead, since per-token billing is a real line item for teams paying in USD. Beyond that headline, this text gives you nothing to act on; we can't say what Amazon measures instead.

Claire Vo ran what the episode calls the first 'How I AI' personal-agent benchmark: Grok Bot, Dot, Meta Muse, and Claude Duet each attempted nine real tasks — a Slack reply written in her voice, cutting short-form video from raw Dropbox footage, fixing a bug from Sentry, building a Figma thumbnail, inbox triage, a family newspaper, a fourth-grade physics homework explanation, shoe shopping, and a ChatPRD launch video. The harness was itself agent-operated: Claude ran Dot while Codex ran the other three and scored the results live. The text provided is show notes only — no per-task scores, final totals, or named winner appear in it, so the title's ranking is not substantiated here.

Why: The copyable asset is the harness, not the verdict: nine specific, checkable tasks plus the rule that a different agent operates each contestant is a template you can run against your own two-or-three agent shortlist instead of trusting a headline ranking. The scoring setup is also a caution — Codex graded every agent except the one Claude operated — so before you switch tools off any benchmark, check who ran and who graded the contestants. This excerpt gives you zero numbers to act on, so treat it as a methodology pointer only.

In Latent Space's AINews briefing, Anthropic hiring manager Felix Reiseberg says he "laid the traditional coding interview to rest" this month, arguing there is no more point giving a React challenge than quizzing people on assembly because Claude is now better at both, and that "our most impactful builders are successful regardless of how good they are at these tests." His advice for juniors: optimise for business impact over clearing a backlog, pitch a few ideas that would dramatically move organisational goals, skip the PRD/buy-in/designer-lobbying cycle by building a working prototype over a weekend, and focus on one good idea. The same briefing notes smaller items — Google Genie, Artificial Analysis and FrontierCode shipping major version bumps, and math-verification work — flagged as annual incremental improvements.

Why: If you're a junior dev or career switcher, the concrete action here is to stop treating interview drills as your portfolio and instead ship one weekend-sized working prototype aimed at a business outcome — that is the artefact this hiring manager says he now weighs. But be honest about the evidence: this is one hiring manager's practice at one lab, described second-hand in a newsletter, and the excerpt is cut off mid-sentence before explaining what replaces the coding test, so don't restructure your whole job search around it. Malaysian teams hiring juniors should note the claim but keep their own signal for whether a candidate can actually build.

PayNet has switched on outbound DuitNow QR cross-border payments through Alipay+, letting Malaysian travellers pay at merchants in mainland China, Hong Kong SAR, South Korea, the Philippines and Laos using their existing bank app — no Alipay account or extra download needed. At launch only Maybank, CIMB and Hong Leong Bank support it, with Bank Islam flagged as coming soon and PayNet saying other member banks and wallet operators can adopt it. The capability is strictly one-way: the user scans the merchant's QR, and merchant-scans-user is not supported, unlike TNG eWallet.

Why: If you build checkout, POS or expense flows for Malaysian users, this is scan-only and bank-limited today: only Maybank, CIMB and Hong Leong customers can use it across five markets, and there is no merchant-initiated scan, so you cannot design a flow where an overseas merchant or terminal pulls payment from the user's DuitNow QR. Treat it as a travel-spend convenience, not a receivable or refund rail, until PayNet adds more banks and the reverse direction.

LiquidAI released LFM3, a family of six 2B-class models (text, vision, audio, omni, and decision) all trained from a shared LFM3-1.7B-Base backbone. The company claims the new tri-hybrid architecture lets LFM3-1.7B beat its older LFM2.5-2.6B while using 35% fewer parameters, with the text model fitting in roughly 1 GB at 4-bit precision and fine-tuning doable on a single GPU. LFM3 also adds a first omni model and video input for the vision model, plus new in-house vision and audio encoders.

Why: If the 1 GB-at-4-bit and single-GPU fine-tuning claims hold, a small team can specialize a multimodal model on its own data without renting a multi-GPU cluster or paying per-token API costs. The trade-off to decide on: self-reported benchmark wins over LFM2.5 are vendor numbers, so benchmark LFM3-1.7B against whatever API model you currently call before committing to an on-device or self-hosted path.

Google DeepMind released Genie 4 in research preview on Tuesday, adding real-time audio, mid-simulation text prompts, freeform edits like changing weather or camera angle, and up to two minutes of scene consistency — double Genie 3's limit. Gemini is integrated as a director that plans steps and checks frames, and a Gemini Robotics experiment had a Gemini 4 Argon model break tasks into steps that Genie 4 simulated in real time. The article also notes consolidation: Runway shipped GWM Worlds 2 months earlier, AMD is acquiring World Labs, Amazon is in talks to buy Decart, and Rivian acquired Third Dimension.

Why: If you work on robotics/agent simulation or interactive prototypes, the jump from Genie 3's one-minute limit to two minutes plus real-time steering is the concrete detail to evaluate — but this is a research preview with no API, pricing, or general-availability details, so don't make production or budget decisions around it yet. For Malaysian builders, the text gives no local access, pricing, or infrastructure angle.

Apple's iMac page announces an M6-powered 24-inch 4.5K iMac with up to 32GB unified memory and a dual 16-core Neural Engine, claiming up to 5x faster on-device AI than the M4 iMac. Pre-orders open at 10:10 a.m. PT on October 28, with availability November 6; the page lists no prices.

Why: If you are weighing a desktop for local AI models, Claude, or vibe coding, the key spec here is up to 32GB unified memory plus the dual Neural Engine, but the 5x AI speedup is Apple's own claim and no Malaysian pricing or availability is stated. Wait for independent token/sec and memory-pressure tests before budgeting.

Cloudflare Radar logged 49 Internet disruptions in Q3 2026, of which 19 were government-directed shutdowns (18 of them exam-related in Iraq), 14 were power outages, and 5 came from natural disasters. Power-grid failures hit Cuba (four separate outages on July 6, July 14, August 3, and a three-day blackout September 18–20), Honduras, Guam, Ukraine, Nepal, and Colombia, while the US, Japan, and Portugal also saw outages. The post argues that distributed network resilience still collapses when electricity does.

Why: If you run multi-region or DR planning, note that the second-largest disruption category this quarter was power, not attacks or BGP — 14 of 49 incidents. A failover plan that spreads across availability zones but sits behind the same strained grid (Cuba's four outages in one quarter is the extreme case) buys less than you think; worth checking whether your provider's redundancy story mentions generator/fuel contracts or only zone count. There is no Malaysia or SEA-specific data here, so treat this as general resilience context, not a local signal.

Opera announced WebAI, a browser-level standard for running AI models locally instead of in the cloud, shipping first as an opt-in early preview in its flagship Opera One browser, with Opera GX and Opera Neon to follow. Opera says WebAI is model-agnostic and supports open-weight models such as Google's Gemma, plus Apple's on-device foundation model on Macs. The pitch is that developers can add AI features without running inference infrastructure or paying per request, and users need no AI subscription.

Why: The concrete claim to test is cost shape: no per-request inference bill and no cloud subscription, in exchange for a model running on the user's machine. If you are pricing a SaaS feature where inference cost scales with usage, a browser-provided local model changes the unit economics — but this is one vendor's self-declared 'standard' in early preview on one browser, with no spec details, no second implementer, and no performance numbers in the text. Treat it as a prototype target, not a platform commitment.

Open3DLab accuses Roblox of using an automated crawler to download 145GB of 3D assets—over 1,000 files—for AI training, allegedly ignoring the site’s rules and including adult content. The report is an accusation from the asset host, not a court finding or Roblox confirmation.

Why: If you host user-generated 3D assets or build on scraped datasets, this is a concrete case for deciding how you enforce AI-training terms: robots.txt and site rules allegedly did not stop a 1,000-plus-file pull, so plan for authentication, rate limits, audit logs, and per-asset licensing. For teams using scraped 3D data, provenance and adult-content filtering become diligence items, not cleanup.

At GTC Berlin on October 21, Nvidia announced multi-billion-dollar deals with six major suppliers spanning substrates, advanced packaging, semiconductor testing, and optical engines, with commitments and production roadmaps running through 2028. The stated goal is to break the bottlenecks constraining AI infrastructure buildouts and lock in capacity for Nvidia's accelerators, with expanded supply arriving from 2027 through 2028. The available excerpt is a member-exclusive preview, so supplier names, exact figures, and per-deal terms are not in the text.

Why: The timeline is the takeaway: Nvidia is contracting capacity for 2027-2028, not 2026, which implies the current accelerator shortage is being planned around as a multi-year condition rather than a blip. If your roadmap assumes cheaper or more available GPUs/API pricing next year, this is evidence to model tight supply and pricing through at least 2027 - reserve capacity early, or design workloads (agent loops, batch jobs, model size) to be token- and GPU-efficient rather than assuming headroom.

The Malaysian Highway Authority (LLM) clarified that TuJu was built to support its Traffic Management Centre for tolled highways—real-time highway conditions, toll exits, rest stops, enforcement-camera alerts, and emergency contacts—not to replace Waze. After the Prime Minister urged a switch from Waze and civil servants were banned from using it, TuJu drew widespread criticism; developer Prosignal Consortium Sdn Bhd shut down its navigation feature for corrective work that may last until 6 November 2026. LLM chairperson Datuk Seri Utama Ir. Hasni Mohammad said LLM’s mandate covers only tolled expressways, broader federal/municipal/rural expansion is a distant possibility depending on funding and technical capacity, and he raised concerns about how TuJu was framed in the 20 October NSC briefing; the article also notes scrutiny over the direct award to Prosignal without an open tender.

Why: For builders or founders selling into Malaysian government digital services, this is a concrete scope-and-procurement cautionary tale: LLM says the product is an internal tolled-highway operations tool, yet it was publicly pushed as a Waze alternative, and the navigation feature was disabled until up to 6 November 2026. Write the operational mandate into the product scope, separate internal dashboards from consumer navigation promises, and expect direct-award decisions to face governance questions.

Entermind, an AI-native consultancy, published a whitepaper claiming RM190 billion (US$46.5bil) in annual Malaysian consumer spending sits with adults it classifies as 'Savvy' or 'Vanguard' on its proprietary Customer AI Savviness Index. The Sept 2026 survey of 1,300 adult AI users in Malaysia found 43% consult an AI assistant first for important decisions versus 31% for search engines, 41% have made a purchase or financial decision primarily on AI-provided information, and 78% wish company apps and websites made decisions as easily as AI tools do. Inside apps, 42% prefer a search box versus 17% who prefer menus; daily AI users were twice as likely as weekly-or-less users to act on AI advice (52% vs 26%).

Why: It is a single vendor's survey with a proprietary index and no published sampling detail, so treat the RM190 billion figure as directional, not a market size you'd put in a deck. The usable signal is the interface preference split — 42% want a search box, 17% want menus — which is a concrete argument for spending your next sprint on answer-first search over nav/menu restructuring, and for checking whether your product content is quotable when a customer asks an assistant 'which bank/school/holiday should I pick' instead of browsing your site.

Anthropic published a best-practices guide for controlling Claude Code spend on Google Cloud, framing cost management as three levers: control (guardrails), track (granular oversight before the bill arrives), and prove (attributing value). It points at Google Cloud's native tooling — per-project billing, billing budgets and alerts, spend caps (still in Preview), BigQuery exports for joining Claude spend with the rest of cloud costs, and quotas — rather than any new Claude-specific billing product. It also states the cost mechanics plainly: consumption-based pricing, where agentic Claude Code burns more tokens per task than chat because it reads files, runs tools, and reasons across a whole task, with model choice as the second major lever.

Why: If you're putting Claude Code on Google Cloud, the concrete setup decision is to host it in a dedicated Google Cloud project so per-project billing gives you a clean cost line, then layer budget alerts on top — and note that spend caps are only in Preview, so don't treat them as a guaranteed hard stop for a team rollout. The BigQuery export is the piece that lets you actually answer 'which team or task is burning tokens' instead of guessing, and the article's own framing (agentic tasks cost more tokens than chat) means per-seat budgeting will mislead you.

At TechCrunch Disrupt, Databricks co-founder and SVP of field engineering Arsalan Tavakoli-Shiraji said startups selling to large enterprises wrongly assume the best tech sells itself; Databricks is now valued at $190 billion and says more than 70% of the Fortune 500 are customers. He cited early deals stalling on legal, contractual, and security questions, and a prospect who ignored him because they had already bet their career on a competitor. His tip: sell under a bigger tech company's umbrella, as Databricks did by becoming a Microsoft Azure partner after failing to get a UBS meeting.

Why: If you sell SaaS to enterprises, prepare security, legal, and contract answers before the first meeting, and evaluate cloud-partner routes such as Microsoft Azure terms as a procurement shortcut. Do not assume a better product beats a buyer who has already backed an incumbent competitor.

Fanatics says it used OpenAI's Codex to build "Shop the Look," a product-page feature that recommends coordinated, in-stock team merchandise across its league and team e-commerce sites. CNBC reports Fanatics carries more than 1.5 million unique SKUs and that the feature increased product engagement by 10% for team merchandise, its biggest revenue source. The excerpt also quotes Fanatics Commerce CPO Justin Tsai describing the catalog-browsing challenge across hundreds of sites.

Why: There is no Malaysia-specific detail in this excerpt, but for ecommerce builders the concrete benchmark is inventory-aware outfit recommendations at 1.5M+ SKU scale with a reported 10% engagement lift; decide whether that use case is worth testing before generic AI search. Treat the 10% as a company claim, not independent measurement.

Anthropic, PBC filed a Form S-1 registration statement with the SEC on October 26, 2026, listed under Delaware with SIC code 7372 (prepackaged software), signed by CEO Dario Amodei and President Daniela Amodei. The submitted text is only the cover page — no revenue, margins, customer concentration, or risk factors are present in the excerpt. The filing drew 484 points and 391 comments on Hacker News, so the discussion is carrying far more substance than the document text shown here.

Why: The only actionable fact in this text is that the paperwork exists: an AI model vendor is registering for a public offering. Everything builders actually care about — inference gross margins, API pricing pressure, enterprise contract terms, dependency on a small set of cloud or customer partners — would be in the sections not included here. If you're building on Anthropic's API or competing with it, the thing to do is read the actual filing's financial and risk sections when they're readable, not react to the cover page; until then you cannot conclude anything about price changes or terms.

Tom's Hardware reports a firmware exploit that removes a half-speed AI throttle on Nvidia RTX 20-, 30-, and 40-series GPUs. The headline claims the mod doubles the RTX 4090's peak tensor rate and lifts RTX 3090 Ti matrix math by up to 80%. The provided text does not include methodology, stability testing, or distribution details.

Why: If you run local AI inference on one of these consumer cards, the claimed gains are large enough to benchmark on an isolated spare GPU before assuming official-driver performance is the ceiling. But because this is an unsupported firmware exploit with no stated safety validation, do not put it on production or client-facing inference nodes.

TNG Digital says GOfinance, the investing hub inside TNG eWallet, passed 5 million distinct users and RM3.57 billion in processed investments as of 30 September 2026. Selected products start at RM10, and the lineup spans money market funds, Amanah Saham, unit trusts, retirement plans, digital gold, and Malaysian plus international shares. Product-level numbers: over 4.7 million users in the GO+ money market fund and more than 700,000 trading digital gold via e-Mas, with a recent Webull integration letting users trade shares inside the eWallet.

Why: This is TNG Digital's own milestone release, so treat the figures as vendor-reported rather than audited. The concrete signal for builders is distribution: a wallet people already open daily is now the front door to investing at a RM10 entry point, with partners like Webull supplying the products. If you are building a consumer fintech or wealth product in Malaysia, the realistic decision is whether to ship standalone or plug in as a licensed partner behind an app with this reach — going direct means competing for a home-screen slot against an app users already have installed.

Tom's Hardware reports that Reddit's r/opensource has introduced sweeping new rules banning AI-made and AI-focused projects, and also banning non-English speakers, with the headline noting backlash connected to Linux kernel contributions and solo developers. The supplied page text is almost entirely site navigation, newsletter, and membership boilerplate: it contains no rule text, effective dates, moderator statements, comment counts, or named individuals. Treat the specifics as unverified until the actual subreddit rules or moderator announcement is read.

Why: If you publish AI-assisted or AI-focused open source work, the headline claims r/opensource now excludes it — so before your next launch post, read the subreddit's actual rule page rather than relying on this article, and line up an alternative distribution channel (your own repo README/Releases, a project blog, or a different community) so one moderation decision doesn't cut off your announcement. The reported non-English-speaker ban matters for anyone running a multi-language contributor community, but the text gives no wording to check it against.

A Register write-up covers IBM's CEO claiming open-weight models have become compelling enough — and cheap enough — to run on-premises rather than through hosted APIs. The Hacker News thread drew 202 points and 104 comments, but the excerpt supplied here is almost entirely site navigation and contains no quoted figures, model names, hardware costs, or benchmarks from the CEO's argument.

Why: The headline claim is the only concrete thing available: open-weight models are being pitched as on-prem-ready on cost and quality. Without the article's numbers you cannot compute a break-even against your current API spend, so treat this as a prompt to price out your own workload (tokens/month, GPU or server cost, ops time) rather than as evidence that self-hosting is now cheaper for you.

Tom's Hardware reports Nvidia is discussing an annual software fee of $2,000 per GPU for software that 'runs agents on AI factories', with the article noting it is unclear how this overlaps with existing Nvidia software tiers. For comparison, the piece states Nvidia already charges more than twice that amount — so over $4,000 per GPU per year — for its AI Enterprise software platform. No confirmed SKU, launch date, or list of covered hardware is given.

Why: Treat this as a budgeting signal, not a product: if agent-runtime software is licensed per GPU per year, an 8-GPU node would carry roughly $16,000/year at the $2,000 figure — or $32,000+/year if it lands at AI Enterprise's stated 'more than twice' rate — on top of hardware, power, and networking. Before committing to self-hosted or reserved GPU capacity for agent workloads, ask the vendor in writing whether agent tooling is bundled into the existing AI Enterprise entitlement or metered separately, and model the per-GPU line item against renting the same capacity by the hour.