The December 2022 issue of IEEE Spectrum is here!

Close bar

Hawk-Eye in the Crosshairs at Wimbledon Again

Cardiff University researchers question how the technology is used; inventor pushes back

4 min read

23 June 2008--When Roger Federer and Rafael Nadal took to Centre Court for the Wimbledon men's singles final in July 2007, the last thing they expected was a controversial line call. The tournament organizers had introduced Hawk-Eye, an automated line-call system, which its makers claim can decide whether a ball is in or out of play with an average accuracy of 3.6 millimeters, or about the width of the fuzz on the ball.

In the fourth set, Nadal asked for Hawk-Eye's judgment on a shot that looked to all and sundry as if it had landed beyond the baseline and was out. But Hawk-Eye said it had hit the line and called it in by a single millimeter. That gave Nadal the point, which he went on to convert into a three games to nil lead in the set. It was an angry Federer, however, who went on to win the match and his fifth consecutive Wimbledon title.

Keep Reading ↓Show less

This article is for IEEE members only. Join IEEE to access our full archive.

Join the world’s largest professional organization devoted to engineering and applied sciences and get access to all of Spectrum’s articles, podcasts, and special reports. Learn more →

If you're already an IEEE member, please sign in to continue reading.

Membership includes:

  • Get unlimited access to IEEE Spectrum content
  • Follow your favorite topics to create a personalized feed of IEEE Spectrum content
  • Save Spectrum articles to read later
  • Network with other technology professionals
  • Establish a professional profile
  • Create a group to share and collaborate on projects
  • Discover IEEE events and activities
  • Join and participate in discussions

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
A plate of spaghetti made from code
Shira Inbar

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less