BOTTOM LINE Despite embarrassing disclosures of board member surveillance that cost Hewlett-Packard’s chairman Patricia Dunn her job, the company is on track to surpass IBM this year as the world’s largest tech company. HP’s third-quarter earnings already put it into the No. 1 position on a rolling 12-month basis, and if it keeps up that performance this quarter, it will seize the top spot from IBM for calendar year 2006.

COMPUTING MILESTONE Grid computing, involving global sharing of computational resources, has taken a big step forward with the demonstration of automated interoperability between collaborating systems in two countries. By means of resource management middleware developed by the G-lambda project in Japan and the Enlightened Computing project in the United States, test software in one country was able to reserve and manage computing and network resources across both countries, without human intervention.

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