Urgent.News

What's breaking now, across thousands of outlets.

Tech

John Ternus is Now Apple's CEO

Apple's former hardware engineering chief John Ternus officially became CEO of the company today, with the change now reflected on Apple's leadership page . Ternus joined Apple in 2001, became a vice president of hardware engineering in 2013, and became senior vice president of hardware engineering in 2021. He is 51, so he could serve as CEO for 10 to 15 years before reaching typical retirement…

John Ternus is Now Apple's CEO

John Ternus officially assumed the role of CEO at Apple today, as stated on the company's leadership page. Ternus began his tenure at Apple in 2001, swiftly advancing to become a vice president of hardware engineering in 2013 and a senior vice president of hardware engineering in 2021. At 51 years old, Ternus has a potential 10 to 15-year tenure as CEO before reaching conventional retirement age.

Tim Cook, who previously held the position of CEO for 15 years, has been appointed as the executive chairman of Apple's board of directors. His primary responsibilities in this role will include engaging with policymakers worldwide. During his final day as CEO on Monday, Cook visited the Apple Park Visitor Center in Cupertino, California, where he interacted with various retail employees from different Apple stores.

The visit, complete with photos and a video, is now available on Instagram. On the eve of his departure, Cook penned a letter to the Apple community, which was shared in April. Tags mentioned in the article include John Ternus and Tim Cook.

Written by urgent.news from MacRumors's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at macrumors.com →

More in Tech

Agent Skill 開發:用 lets-social 自動將文章轉化為 IG、Threads、FB 社群貼文

本篇要解決的問題 以前流行手寫套件,分享到 GitHub 上讓人取用,現在似乎…流行的是 Skill 了。 因為來自 Google 的流量一直在下降,所以 Let's Write 也建了 Instagram、Threads 想增加導流的平台。 為了讓一篇文章出來後,可以針對不同的平台,給不同的貼文,所以讓 AI 建立了本篇的 Skill,看能不能有效的增加本站流量。 這是公開的…

Low Latency and “Fast Enough”

What is low latency? Why is it different from domain to domain? And what is “fast enough”? Everybody wants their application to have low latency. This is obvious. The real question is: how low ?

  • Low latency varies by application and business case
  • Latency-sensitive flows divided into user experience, backend processes, and competing systems
  • Goal is to be "fast enough" for specific business case

What Is a Flaky Test? Why It Costs More Than the Bug It Was Meant to Catch

A flaky test passes and fails on the same code. Nothing changed between the two runs except timing, ordering, or something outside the test that nobody was thinking about.

  • Flaky tests pass and fail unexpectedly on same code.
  • Caused by timing issues, order dependence, shared state.
  • Addressed by fixing underlying issue, not just increasing timeouts.

More from Tuesday 1 September →