Sources: Google is in talks with Marvell Technology to develop a memory processing unit that works alongside TPUs, and a new TPU for running AI models (Qianer Liu/The Information)
THE SO WHAT
Google pairing TPUs with a Marvell-built memory processing unit is an admission that the bottleneck is now memory bandwidth and locality, not raw flops. If you're designing AI workloads, architecture decisions around parameter sharding, KV cache, and sequence length are about to be constrained — or unlocked — by how fast your memory fabric evolves, not your GPU count.
READ THE SOURCE
MORE FROM THE WIRE
Applied AI'They are not human': Why AI has 'predictable and systematic biases' when it comes to judging people
Structured trust models mean AI will discriminate the same way, every time — demographic bias becomes an engineered property, not a side effect. If you're using AI for hiring, lending, or moderation, you now own a repeatable bias function that regulators and plaintiffs can interrogate line by line.
Applied AIApple’s Revamped Siri Interface in iOS 27 Is Hidden in WWDC Teaser
If Apple is teasing a revamped Siri UI while warning about memory shortages delaying Macs, assume the real constraint on on-device AI is DRAM, not model quality. Hardware roadmaps and AI UX are now coupled — if you're building on Apple platforms, align your product bets with their memory and silicon cadence, not just iOS release notes.
Applied AI'75% of resumes never reach a human': Here’s the hidden reason your application is getting rejected by AI
Hiring is quietly becoming an NLP problem—if your org is still reading PDFs manually, you're losing talent to whoever is tuning their filters and prompts. Treat your ATS like a search engine: own the schema, keywords, and models, or accept that your best candidates never clear the machine gate.
Applied AISalesforce Announces Huge AI Initiative and Calls It ‘Headless 360’
Salesforce going 'headless' is a declaration that the CRM front-end is now a commodity surface and the real control point is data and orchestration. If your product depends on owning the UI layer around Salesforce data, assume you're being routed around and re-anchor on workflow depth or proprietary data.