Skip to main content

Apple's Stock Drops Nearly 10%. How Will It Respond to Memory Shortage?

1 month ago
Apple's stock "fell just shy of 10% on Friday," reports Yahoo Finance, "after CEO Tim Cook warned about the impact of the global memory shortage on the company's business." During Apple's third quarter earnings call, Cook said the company paid significantly more for memory in the quarter and expects that to further increase in the current period. And while Apple is able to offset some of that price jump, it won't be able to tackle it all... The CEO said that iPhone and Mac sales outpaced Apple's own expectations and that a lack of flexibility in the supply chain is making it more difficult to keep up with demand. Yahoo Finance cited an investment analyst who predicts overall gross margins for Apple's iPhone could drop from 38% to 34.5%. But another analyst sees a scenario where Apple "raises iPhone prices, unit growth will slow, and as unit growth slows, so will user growth, which we think ultimately will slow Services growth." (Still, Yahoo Finance predicts Apple's new leasing program "could help address those concerns.") Apple has another controversial option, according to the blog 9to5Mac: Bloomberg reports that US senators from both sides of the aisle are urging Apple CEO Tim Cook to commit by August 21 to not using memory chips from Chinese suppliers CXMT and YMTC.... Apple is not required to obtain U.S. government approval to purchase chips from the companies, but doing so without the administration's support could expose it to significant political ramifications. Which is why, in an interview with The Wall Street Journal ahead of Apple's recent price hikes, Tim Cook said that "everything needs to be on the table," adding that "we should look at all supply...." More recently, the Journal reported that Apple's use of Chinese memory chips could extend beyond China, with the company seeking the administration's blessing to use components from CXMT and YMTC in products sold elsewhere outside the US. The report also detailed Micron's efforts to persuade the administration to reject Apple's request, arguing that allowing Chinese suppliers into Apple's supply chain could undermine domestic memory production... [Bloomberg's reported that U.S. lawmakers warned] other companies could follow Apple's lead, potentially undermining domestic memory production and planned investments in states such as Indiana, Idaho, New York, and Virginia... [T]he senators sought details about any information Apple has shared with CXMT during the component qualification process, noting that the transfer of controlled technical information to advanced chipmaking facilities in China may require a Commerce Department license. The blog MacRumors notes that Apple has already increased prices for Macs and iPads in June because of surging memory prices. Apple CEO Tim Cook said Thursday "we did it because we're in what I would characterize as a 100-year flood on memory pricing with exponential increases in memory prices." Cook did not comment on whether Apple plans to raise iPhone prices when the iPhone 18 Pro models and first foldable launch this September, but multiple analysts believe prices will go up. Cook said Apple is expecting to pay higher memory costs in the September quarter, though Apple will be able to partially offset it with lower costs on some non-memory components and a stockpile of inventory. Sky News points out that "It was Tim Cook's final earnings appearance before his retirement after 15 years at the helm of the company." Apple, which recently topped Nvidia as the most valuable listed company, has been largely spared the volatility in share price seen by chipmakers and big spenders on artificial intelligence. Apple continues to generate cash without the huge investment spending that its Wall St peers are dealing with "and that showed across most parts of the operation," said Thomas Monteiro, an analyst at Investing.com.

Read more of this story at Slashdot.

EditorDavid

Hamburg Is Replacing a Bridge In One Huge Piece

1 month ago
Long-time Slashdot reader Qbertino writes: The northern German City of Hamburg is currently in the process of replacing one of its bridges in one single gigantic piece. The new replacement weighs 3700 metric tons and was carefully moved into place over a stretch of 500 meters, requiring extreme patience and precision maneuvering. Some places leave only 40 cm of room to neighbouring buildings.

Read more of this story at Slashdot.

EditorDavid

New GitHub, PyPI Policies Hope to Boost Supply Chain Security

1 month ago
"GitHub and the Python Package Index (PyPI) have introduced new policies meant to boost supply chain security," reports SecurityWeek, "by preventing the fast propagation of poisoned package versions and the poisoning of old and long-stable releases." To prevent the fast delivery of malicious code through the immediate fetching of brand-new releases, GitHub has introduced a Dependabot cooldown, where the automation tool waits for at least three days after a release has been published before opening a pull request. "Waiting a few days before adopting a new release gives maintainers, security researchers, and automated scanners time to spot a malicious version and get it pulled before it ever reaches your pull requests," GitHub explains. The three-day cooldown only applies to non-security version bumps, and the behavior can be modified through the configuration option in the dependabot.yml. "Three days as the default balances two goals: it pushes you past the window where most of these attacks live, and it doesn't hold your dependencies back longer than necessary," GitHub notes. And the Python Package Index (PyPI) "now rejects new files being uploaded to releases that are older than 14 days," according to a recernt blog post from the Python Software Foundation's security developer-in-residence Seth Larson: This restriction was put in place to prevent old and long-stable releases from being poisoned in case publishing tokens or workflows of PyPI projects were compromised... The discussion of this behavior began during PEP 740 (Digital Attestations) back in January 2024. The discussion was restarted in March 2026 after the popular packages LiteLLM and Telnyx were compromised. These packages were compromised due to a "mutable reference" in these projects' usage of the Trivy GitHub Action... To quantify how disruptive this change would be to existing workflows, the PyPI database was queried for projects that have published new files to old releases... [O]nly 56 projects of 15,000 had published a [Python] 3.14-compatible wheel more than 14 days after a release was available. This topic was brought to the Packaging Summit at PyCon US 2026 by PyPI Safety & Security Engineer, Mike Fiedler. The rough consensus of the discussion was that the summit attendees thought it was "acceptable to require users to bump to the next version" to support new Python versions. With the data and consensus in hand, Seth moved forward with a patch to reject new files on old releases which was merged July 8th, 2026.

Read more of this story at Slashdot.

EditorDavid