Archives : applications

three cloud services trends for 2012

published on 2012/01/23 by Stewart Baines

Is this the year of the Cloud, like 2011 or 2010 before it? The difference is that it's on the verge of a typing point. Microsoft, Google and Amazon have already nailed their flag to the mast of cloud services, and with iCloud, Apple has joined the club....

three cloud services trends for 2012

which applications can access your Facebook, Twitter, LinkedIn and/or Google+ accounts?

published on 2012/01/10 by Jean-François Audenard

Social networks like Facebook, Twitter, LinkedIn and Google+ make it easy to share information with people from different personal and professional circles. Users can access these networks from standard PCs or specific applications on their smartphones or tablets. So how can you find out - and control -- which applications are able to access your Facebook, LinkedIn, Twitter and Google accounts?...

which applications can access your Facebook, Twitter, LinkedIn and/or Google+ accounts?

ciao Knowledge11 ... looking forward to Knowledge12

published on 2011/12/21 by Sebastien Rivory

Summary of Knowledge event around ServiceNow SAAS ITSM platform...

ciao Knowledge11 ... looking forward to Knowledge12

Is this the end of email?

published on 2011/12/19 by Stewart Baines

Thierry Breton, CEO of Atos and formerly CEO of France Telecom, believes that email is clogging up Atos' arteries. He plans to ban staff from using emails internally within just 18 months, arguing that they waste time and that most messages sent and received are irrelevant. Breton would prefer his staff to use instant messaging and a social networking-style interface instead....

Is this the end of email?

should software companies be liable for the code that they create?

published on 2011/11/28 by Stewart Baines

Today, software vendors are largely protected from the adverse effects of any software that they write. End-user license agreements are notoriously draconian. These long swathes of legalese are designed to get software developers off the hook. They effectively make users accept that they're running the software at their own risk. It imposes a 'sold as seen' approach, even though the code is, for the most part, unseen by the user....

should software companies be liable for the code that they create?