Info World

In a litany almost as old as software development itself, a Windows kernel developer posted a scathing rebuke of the way kernel development is being managed.

iPhones and other smartphones have led to a wave of violent crimes commissioned by those seeking to steal cellphones Welcome to San Francisco: Here's where the cellphone thefts are iPhones and other smartphones have led to a wave of violent crimes commissioned by those seeking to steal cellphones

By Martyn Williams, IDG News Service

iPhones and other smartphones have led to a wave of violent crimes commissioned by those seeking to steal cellphones Welcome to San Francisco: Here's where the cellphone thefts are iPhones and other smartphones have led to a wave of violent crimes commissioned by those seeking to steal cellphones

By Martyn Williams, IDG News Service

iPhones and other smartphones have led to a wave of violent crimes commissioned by those seeking to steal cellphones Welcome to San Francisco: Here's where the cellphone thefts are iPhones and other smartphones have led to a wave of violent crimes commissioned by those seeking to steal cellphones

By Martyn Williams, IDG News Service

Size (and mobility) matters.

Credit: iStockphoto

On Feb. 27 in the middle of the afternoon, a 16-year-old girl was walking through San Francisco's Mission District when she was ordered at gunpoint to hand over her cellphone. The robbery was one of 10 serious crimes in the city that day, and they all involved cellphones. Three were stolen at gunpoint, three at knifepoint, and four through brute force.

Building a resilient, high-capacity WAN has never been what I'd call simple. In the old days (you know, 10 years ago), it was typically a mishmash of frame-relay and point-to-point leased line circuits mixed with ATM in higher-end, converged applications. Today, those technologies and their successors are being displaced by a variety of IP-based Ethernet circuits. Although I think this shift to Ethernet-based WAN implementations is hugely liberating when it comes to WAN design, it has its drawbacks.

Saar Gillai, named head of Hewlett-Packard's cloud operations in January, is on the hot seat.

Size (and mobility) matters.

Credit: iStockphoto

On Feb. 27 in the middle of the afternoon, a 16-year-old girl was walking through San Francisco's Mission District when she was ordered at gunpoint to hand over her cellphone. The robbery was one of 10 serious crimes in the city that day, and they all involved cellphones. Three were stolen at gunpoint, three at knifepoint, and four through brute force.

I spent part of today like I do many other days: I sat in a meeting where people discussed technology and how to deploy it. It was a conversation that, while not above my head, had me swimming in daydream land. It wasn't the first time this discussion had been had, and it wouldn't be the last.

Building a resilient, high-capacity WAN has never been what I'd call simple. In the old days (you know, 10 years ago), it was typically a mishmash of frame-relay and point-to-point leased line circuits mixed with ATM in higher-end, converged applications. Today, those technologies and their successors are being displaced by a variety of IP-based Ethernet circuits. Although I think this shift to Ethernet-based WAN implementations is hugely liberating when it comes to WAN design, it has its drawbacks.

Saar Gillai, named head of Hewlett-Packard's cloud operations in January, is on the hot seat.

Size (and mobility) matters.

Credit: iStockphoto

On Feb. 27 in the middle of the afternoon, a 16-year-old girl was walking through San Francisco's Mission District when she was ordered at gunpoint to hand over her cellphone. The robbery was one of 10 serious crimes in the city that day, and they all involved cellphones. Three were stolen at gunpoint, three at knifepoint, and four through brute force.

I spent part of today like I do many other days: I sat in a meeting where people discussed technology and how to deploy it. It was a conversation that, while not above my head, had me swimming in daydream land. It wasn't the first time this discussion had been had, and it wouldn't be the last.

Building a resilient, high-capacity WAN has never been what I'd call simple. In the old days (you know, 10 years ago), it was typically a mishmash of frame-relay and point-to-point leased line circuits mixed with ATM in higher-end, converged applications. Today, those technologies and their successors are being displaced by a variety of IP-based Ethernet circuits. Although I think this shift to Ethernet-based WAN implementations is hugely liberating when it comes to WAN design, it has its drawbacks.