Concurrent Events

by Peter Coffee on March 27, 2008 at 11:38 AM

It's been at least eight years since microchip gurus noted the growing gap between multi-thread hardware and single-thread tasks. Vendors who've taken the lead in the drive toward hardware parallelism are now looking for ways to bring software developers into alignment with what that technology enables. There are already definite danger signs of diminishing, or even negative, returns.Quadcorecrop

Experts like AMD Senior Fellow Chuck Moore suggest that future development must move upward into the level of the API rather than the instruction set, which is certainly not news to the Force.com developer. The PaaS development community is living that future today.

Force.com developers, I suggest, are already giving the lie to anyone who says that "" The business model is PaaS, and the killer application is Development as a Service.

As William Gibson has famously said, "The future is already here - it is just unevenly distributed." Developing on Force.com gives developers more than their share, and I'm just fine with that.

TrackBack

TrackBack URL for this entry: http://www.typepad.com/services/trackback/6a00d8341cded353ef00e55179bddf8833

Listed below are links to weblogs that reference Concurrent Events:

Post a comment

If you have a TypeKey or TypePad account, please Sign In