Coding

Apple, Intel have reached preliminary chip-making deal

A major shake-up in the global semiconductor landscape is underway as Apple and Intel reportedly reach a preliminary agreement to collaborate on custom chip design and manufacturing, potentially upending the traditional foundry model and redefining the boundaries between fabless and foundry operations. Under the proposed deal, Apple would gain access to Intel's advanced 3nm process technology, while Intel would tap into Apple's expertise in system-on-chip (SoC) design.

Apple and Intel have reportedly reached a preliminary agreement to collaborate on custom chip design and manufacturing, according to a report by the Wall Street Journal. The deal, if finalized, would mark a significant shift in the semiconductor industry by blurring the traditional lines between fabless chip designers and foundry operators.

Under the proposed arrangement, Apple would gain access to Intel's advanced 3nm process technology for manufacturing its custom chips. In return, Intel would tap into Apple's expertise in system-on-chip (SoC) design. This reciprocal exchange could allow both companies to leverage each other's strengths: Apple's proven ability to design high-performance, power-efficient SoCs for its devices, and Intel's manufacturing capabilities, which have been undergoing a turnaround effort under CEO Pat Gelsinger.

What it means for the industry

The semiconductor landscape has long been divided between fabless companies like Apple, AMD, and Qualcomm, which design chips but rely on third-party foundries like TSMC and Samsung for manufacturing, and integrated device manufacturers (IDMs) like Intel, which both design and fabricate chips. A deal between Apple and Intel would represent a hybrid model: Apple would remain a fabless designer but gain access to Intel's foundry services, while Intel would expand its foundry business by securing a major customer.

For Apple, this could reduce its dependence on TSMC, which currently manufactures the majority of Apple's custom chips, including the A-series and M-series processors. Diversifying manufacturing sources could provide supply chain resilience and potentially better pricing leverage. For Intel, landing Apple as a foundry customer would be a significant validation of its foundry strategy, which has been a key pillar of Gelsinger's turnaround plan.

Tradeoffs

The deal is not without risks. Intel's 3nm process is still in development and has faced delays in the past. Apple would need to ensure that Intel's manufacturing yields and performance meet its stringent standards. Additionally, the collaboration could create tensions with TSMC, which has been Apple's primary foundry partner for years. Apple would likely maintain a multi-sourcing strategy rather than fully switching to Intel.

From Intel's perspective, working with Apple could expose its manufacturing processes to a competitor that designs chips for devices that compete with Intel's own products. However, Intel has been moving toward a more open foundry model, where it manufactures chips for other companies without competing in their markets.

When to use it

This deal is still preliminary and subject to negotiation and regulatory approval. If finalized, it would likely take several years to implement, as both companies would need to adapt their design and manufacturing processes to work together. For now, the report signals a potential realignment in the semiconductor industry, but concrete details remain scarce.

Bottom line

The Apple-Intel chip-making deal, as reported, represents a potential strategic pivot for both companies. Apple gains a second foundry source, while Intel gains a marquee customer for its foundry business. The outcome will depend on execution, but the preliminary agreement already highlights the shifting dynamics in chip manufacturing.

Similar Articles

More articles like this

Coding 1 min

Open Source Resistance: keep OSS alive on company time

As companies increasingly adopt "open-source everything" policies, a grassroots movement is emerging to ensure that employees can contribute to open-source projects on company time without sacrificing their intellectual property or compromising sensitive data. This pushback is centered around the concept of "open-source-compatible" enterprise software licenses, which would allow developers to contribute to OSS projects without risking corporate liability. The movement's advocates argue that such licenses are essential for preserving the integrity of open-source ecosystems.

Coding 2 min

The limits of Rust, or why you should probably not follow Amazon and Cloudflare

Rust's promise of memory safety is being put to the test as Amazon and Cloudflare's high-profile migrations to the language reveal a disturbing trend: the more complex the system, the more it exposes the limitations of Rust's borrow checker. Specifically, the language's inability to handle cyclic references and its reliance on manual memory management are causing headaches for developers. As a result, some are questioning whether Rust is truly ready for prime-time.

Coding 1 min

The AI Backlash Could Get Ugly

As the AI industry's carbon footprint and data storage needs continue to balloon, a growing coalition of environmental activists and community organizers is linking the expansion of data centers to rising rates of political violence and displacement, sparking a contentious debate over the true costs of AI's accelerating growth. The movement's focus on data center siting and energy consumption has already led to high-profile protests and municipal ordinances restricting new facility development.

Coding 1 min

Software Developers Say AI Is Rotting Their Brains

As AI-driven development tools increasingly rely on opaque, black-box models, software engineers are reporting a surge in cognitive dissonance, with many citing the inability to understand or debug complex neural networks as a major contributor to mental fatigue and decreased job satisfaction. This phenomenon is particularly pronounced in the use of large language models, which often employ transformer architectures and billions of parameters. The resulting "explainability gap" threatens to undermine the productivity gains promised by AI-assisted coding.

Coding 2 min

My graduation cap runs Rust

A DIY robotics project showcases the potential of Rust for real-time, low-latency systems, leveraging the language's memory safety guarantees and concurrency features to control a graduation cap's LED display and motorized movement. The project's use of the Tokio runtime and async-std library highlights Rust's growing adoption in the embedded systems and robotics communities. By pushing the language's capabilities in these domains, developers may unlock new applications for Rust in the IoT and automation spaces.

Coding 1 min

When "idle" isn't idle: how a Linux kernel optimization became a QUIC bug

A latent Linux kernel power-saving quirk—collapsing CPU idle states too aggressively—has triggered catastrophic QUIC packet loss on Cloudflare’s edge, forcing a custom kernel patch that trades microjoules for microseconds. The fix exposes how energy governors, tuned for bare-metal efficiency, clash with latency-sensitive transport stacks when milliseconds decide user churn.