Quantum Computing: Atomic Clocks Make for Longer-Lasting Qubits

Cesium atoms and laser traps offer a more robust type of quantum computer

4 min read
Image: Weiss Laboratory/Penn State
Bright Qubits: Lasers hold cesium atoms in place in a 5-by-5 grid for a neutral-atom quantum-computer prototype built at Penn State. The atoms’ quantum states can be used to store information.
Image: Weiss Laboratory/Penn State

A decade ago, quantum computing was still something of a parlor game. Quantum-computer advocates could make bold claims about one promising technology or another because no one had yet figured out how to string together more than a handful of quantum bits (qubits).

Times have changed. IBM now has a 50-qubit machine, Intel is at 49 qubits, and Google has developed a 72-qubit device. And in September, Pennsylvania State University researchers announced they’d built the framework for a 125-qubit compute engine.

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
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

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
{"imageShortcodeIds":["31996907"]}