Urgent.News

What's breaking now, across thousands of outlets.

Tech

John Ternus Officially Becomes Apple CEO After 15 Years of Cook’s Tenure

Apple has entered a new era as Tim Cook steps down as CEO and John Ternus takes over the company’s … Read More The post John Ternus Officially Becomes Apple CEO After 15 Years of Cook’s Tenure appeared first on ProPakistani .

John Ternus Officially Becomes Apple CEO After 15 Years of Cook’s Tenure

Tim Cook has departed from his position as Apple CEO after a 15-year tenure, with John Ternus officially assuming the role on September 1. Cook joined Apple in 1998 and took over as CEO in 2011 following Steve Jobs' resignation due to health issues. Cook will continue with Apple as executive chairman. Throughout his leadership, Cook oversaw the development of the iPhone 5, 5s, and 5c, as well as Apple's expansion into new product categories.

Prior to becoming CEO, Ternus served as Senior Vice President of Hardware Engineering, where he managed teams responsible for various Apple products such as the iPhone, iPad, Mac, Apple Watch, AirPods, and Apple Vision Pro. His appointment marks Apple's first CEO change since Cook succeeded Jobs in 2011, and positions him to lead the next generation of Apple products.

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

Read the original at propakistani.pk →

More in Tech

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.

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

More from Tuesday 1 September →