The MIX '09 conference site has announced the panel I'll be moderating at this year's conference in the post titled Opening the “Walled Garden” of Social Networks which is excerpted below

As social networking sites become more and more numerous, and consumers are looking to simplify their online lives,  providers are scrambling to define the path forward for social network aggregation.  Join us at MIX for a special guest panel on “Standards for Aggregation Activity Feeds and Social Aggregation Services”. 

Check out this killer line-up of panelists - big names and leading companies in the online and social networking space:

Dare Obasanjo (Moderator) – Microsoft

Kevin Marks – Software Engineer at Google; formerly principal engineer for Technorati; one of the founders of Microformats

Marc Canter – CEO at Broadband Mechanics; founder of Macromedia

Monica Keller – Dev Manager at MySpace; formerly Architect at SumTotal

Joseph Smarr – Chief Platform Architect at Plaxo

If you haven’t registered for MIX09 by now, what exactly are you waiting for, an invitation?  Consider it delivered.

This should be a fun panel and if you'll be at MIX and are interested in where activity streams and social network interoperability is going then you should attend.

PS: I believe John McCrea may be replacing Joseph Smarr on the panel due to scheduling issues.

Note Now Playing: Wu-Tang Clan - Reunited Note


 

Categories: Social Software

This past weekend, I bought an Apple iPhone as a replacement for my AT&T Tilt which was slowly succumbing to hardware glitches. As a big fan of Windows Mobile devices and their integration with Microsoft Exchange I was wary of adopting an iPhone. I was concerned about it not having all of the features I'd gotten used to but on the other hand I was looking forward to replacing my iPod+AT&T Tilt combination with a single device.

Here are my positive and negative impressions of the device after five days

The Good

There are lots of things I like about the iPhone experience. Below are my favorite aspects of the experience thus far

  • Visual Polish: The visual polish of the 1st and 3rd party applications on the iPhone is amazing. There are so many nice touches in the phone from the coverflow browsing experience when playing music to the transparent pop over windows when you receive an SMS text. The few 3rd party applications I've used have also seemed similarly polished although I've only downloaded less than ten apps. It's like using a futuristic device that you see in movies not an actual phone from real life. 

  • Browsing and Purchasing Applications: As someone whose used Handango and ActiveSync to install applications on my Windows Mobile device, I have to say that experience pales in comparison to being able to browse, search, purchase and install apps directly from my phone. Having the app store integrated into iTunes actually seems superfluous.

  • It's also an iPod: I used to think my iPod classic was a fantastic music playing device until I got my iPhone. Now it seems rather primitive and ugly. I shocked at how much better the music playing experience is on my iPhone and have tossed my iPod classic into our junk drawer.  Now my pockets are lighter and I got an iPod upgrade. Nice. 

  • The Web browser: The browser supports multi-touch for zoom and it does AJAX. Hell, yeah.

  • Autocomplete when sending emails: When sending a mail, it uses autocomplete to fill out the TO/CC/BCC line by looking in your contact list and the email addresses of people in your inbox. This is a very nice touch.

The Bad

There are also a number of features I miss from owning a Windows Mobile device which I hope are addressed in the future or I might eventually find myself switching back

  • Email Search: Windows Mobile devices can search emails in your Exchange inbox by sending a query to the server. Using this functionality you aren't limited to searching the emails on your device but can search at least month of emails and get the results sent down to your phone. The iPhone has no email search functionality.

  • No integration with the Global Address List: On my AT&T Tilt I often needed to send emails to co-workers whose email addresses weren't in my contact list. All I needed to do was type out their names and then I could pull up their information (email address, phone number and office location) down to my phone to either add them as a contact or insert their email address into an email. I've felt rather handicapped without this functionality.  The autocomplete feature which uses all the email addresses from your local inbox has been a slight mitigation.

  • No Flash in the browser: After getting used having a Flash-capable browser on my AT&T Tilt via Skyfire it is rather irritating that I've now lost that functionality by switching to an iPhone. You don't really notice how much Flash video content there is on the Web until you start missing it. My last post was of a Flash video which is a broken link when I browse my blog from my iPhone. Lame.

  • Managing meetings is awful: As a program manager at Microsoft I schedule a lot of meetings. Every once in a while I may be running late for a meeting and have to either send a mail out to the attendees telling them I'll be late or cancel the meeting. Neither of these options is available on the iPhone.

  • Reply flags not set in Exchange: With a Windows Mobile phone, when you respond to a mail via the phone it is properly marked as a mail you've replied to when you view it in Outlook on the desktop. The iPhone developers remembered to track which emails you've responded to on the device but failed to propagate that information back to Exchange. For a while, I thought I was going senile because I remembered responding to mails but they weren't marked as being replied to in my inbox. After I found my replies in my Sent mail folder, I realized what was wrong. 

  • Tasks: Although I've never tried Getting Things Done, I am a big fan of Outlook Tasks and often add new tasks or mark them as complete from my phone. The iPhone does not synchronize your Outlook tasks from Exchange which is a glaring oversight. For now, I've gotten around this by spending $10 on KeyTasks for the iPhone which is somewhat hacky but works. 

The Ugly

So far there have been two aspects of the user experience that have been facepalm worthy

  • Ringtones: On my AT&T Tilt it was pretty straightforward to make any MP3 snippet eligible to be used as a ring tone simply by dropping it in the right folder. The iPhone requires that I pay $0.99 for a song I already own to use it as a ring tone. Seriously?

  • Using your iPhone on multiple computers: I typically purchase music and burn CDs on my home computer while using my iPod as a music library at work. This functionality is disabled out of the box on the iPhone. You can only sync your iPhone to one computer which includes only being able to play music off of your iPhone on a single computer. This is pretty ridiculous given multicomputer households and people who use their iPhones at home and at work. Thankfully, the Internet is full of workarounds to this foolishness on Apple's part. 

Despite what looks like a long list of complaints this is probably the best mobile phone I've ever owned. It just isn't perfect.

Note Now Playing: Jay-Z - Can't Knock the Hustle Note


 

Categories: Technology

February 9, 2009
@ 03:03 PM
<a href="http://video.msn.com/?playlist=videoByUuids:uuids:533e05d2-9f12-4a86-bdda-efd0455fcd36&amp;showPlaylist=true" target="_new" title="Kylie uses Windows Live Photo Gallery">Video: Kylie uses Windows Live Photo Gallery</a>

Note Now Playing: Cranberries - Linger Note


 

Categories: Windows Live

There used to be a time when all you needed when building a Web site was a relational database, a web server and some sort of application server or web framework (terminology depending on whether you are enterprisey or Web 2.0) that acted as a thin layer to translate requests into database queries. As we've grown as an industry we've realized there are a lot more tools needed to build a successful large scale modern web site from messages queues for performing time consuming tasks asynchronously to high availability cloud management tools that ensure your site can keep running in the face of failure.

Leonard Lin has a [must bookmark] blog post entitled Infrastructure for Modern Web Sites where he discusses the underlying platform components you'll commonly see powering a large scale web site in today. The list is included below

I’ve split this into two sections. The first I call “below the line,” which are more system level (some things straddle the line):

  • API Metering
  • Backups & Snapshots
  • Counters
  • Cloud/Cluster Management Tools
    • Instrumentation/Monitoring (Ganglia, Nagios)
    • Failover
    • Node addition/removal and hashing
    • Autoscaling for cloud resources
  • CSRF/XSS Protection
  • Data Retention/Archival
  • Deployment Tools
    • Multiple Devs, Staging, Prod
    • Data model upgrades
    • Rolling deployments
    • Multiple versions (selective beta)
    • Bucket Testing
    • Rollbacks
    • CDN Management
  • Distributed File Storage
  • Distributed Log storage, analysis
  • Graphing
  • HTTP Caching
  • Input/Output Filtering
  • Memory Caching
  • Non-relational Key Stores
  • Rate Limiting
  • Relational Storage
  • Queues
  • Rate Limiting
  • Real-time messaging (XMPP)
  • Search
    • Ranging
    • Geo
  • Sharding
  • Smart Caching
    • dirty-table management

Leonard Lin's list comes from his experience working at Yahoo! but it is consistent with what I've seen at Windows Live and from comparing notes from publications on the platforms behind other large scale web services like Facebook, eBay and Google. This isn't to say you need everything on the above list to build a successful web site but there are limits to how much a service can scale or the functionality it can provide without implementing almost every item on that list.

This brings me to Google App Engine (GAE) which is billed as a way for developers to build web applications that are easy to build, maintain and scale. The problem I had with GAE when I took an initial look at its service is that although it handles some of the tough items from the above list such as the need for high availability cloud management tools, deployment tools and database sharding, it was also missing some core functionality like message queues. These oversights made it impossible to build large classes of Web applications such as search engines or email services. It also made it impossible to build asynchronous workflows in ways that improve responsiveness of the site from an end user's perspective by reducing request latency.

So it was with some interest I read Joe Gregorio's post on the Google App Engine blog entitled A roadmap update! where he updates the product's roadmap with the following announcement

The App Engine team has been plugging away and we're excited about some pretty big announcements in the near future. In the meantime, we decided to refresh our App Engine roadmap for the next six months with some of the great new APIs in our pipeline:

  • Support for running scheduled tasks
  • Task queues for performing background processing
  • Ability to receive and process incoming email
  • Support for sending and receiving XMPP (Jabber) messages

As always, keep in mind that development schedules are notoriously difficult to predict, and release dates may change as work progresses. We'll do our best to update this roadmap as our engineers continue development and keep you abreast of any changes!

The ability to send email and the ability to perform background processing tasks are key features you'd need in any modern site. I've been wanting to try out GAE as a way to keep my Python skills fresh but have balked at the lack of background tasks and message queues which artificially limits my creativity. Once these announced features are done, I may have to take back my comments about GAE being only useful to toy applications.

Maybe next time C|Net asks Is Google App Engine successful? the answer will be "Yes".  Or at least the possibility that the answer will be "Yes" will go up a few orders of magnitude since it definitely doesn't seem to be successful today.

Note Now Playing: Playa Fly - Feel Me Note


 

Categories: Web Development

Alex Payne has a great criticism of both Web and desktop email application in his post The Problem With Email Clients which accurately captures some of the frustrations I've had with both classes of email clients. The entire post is a must read if you've ever thought about how email can be improved. Some key passages from his post are 

Anyone who’s given Gmail a fair shake will quickly find conversations indispensable. Going back to any other email client is agonizing and disorienting, like being knocked around and dumped out of the back of a pickup on the outskirts of a strange town. In desktop email clients, new messages arrive completely bereft of context. The only way to orient yourself is to either remember what the conversation was about or read through the mess of quoted text that may or may not be present at the bottom of the message, depending on what kind of email client or prefences the sender has. You could try searching to re-orient yourself, but good luck with that in Outlook or Mail.app.

With conversations, Google has offered the only advancement in the information architecture of email clients in decades. Apple, on the other hand, has given us basically bupkiss, rendering Neven’s defense a bit silly.

This is probably heresy coming from a web application developer, but I think web applications are mostly ghastly. I hate using them. When I’m faced with a computing problem, I want to solve it with a polished, stable, native application for my operating system that looks and feels like it belongs on my computer. I don’t believe in Rich Internet Applications — they’re a boogeyman that I keep hoping will disappear.

The problem with Gmail is that it could be a “real” application. While its conversations and search-that-actually-works are (sadly) innovative, they’re not impossible to implement as part of a platform-native email client. I enjoy using Gmail, but I’d enjoy it even more if it obeyed the rules of my operating system, not the rules of the web. The web has a lot to offer certain types of problems, but I’m not convinced that email is one of them.

The problem with desktop email clients is that they’re not webmail. The problem with webmail is that it’s not a desktop email client.

I think Alex is on to something here. I prefer to read read my Hotmail account in Outlook via the Microsoft Outlook Connector because I'd rather read my email in a desktop app than in a Web app trying to look like a desktop app. On the other hand, I read my RSS feeds in RSS Bandit even though Outlook is an extremely popular RSS reader because I'm dissatisfied with how Outlook presents messages and feel an app I wrote myself does it more effectively.

Clearly there is room for a revolution here.

Note Now Playing: R.E.M. - Everybody Hurts Note


 

Facebook made two interesting announcements this week in the area of making their platform more open. The first announcement was made by Mike Shroepfer in the developer blog post Next Steps in Openness where he writes

Enabling social information to flow through the Web is one of the core goals of Facebook. In the two months since Facebook Connect became generally available, over 4,000 sites and desktop applications have gone live with the service. Users can now log into sites across the Web using their Facebook account, bring their identity and friends with them, and share information and experiences using the same features as they would with applications on Facebook.

As we've launched and built Facebook Connect, we've been participants in OpenID efforts. One of our user experience experts, Julie Zhuo, presented at the UX Summit in October. Several of our engineers have been participating in meetups, and one of them ran as a community member for a board seat. We're happy to announce today that we are formalizing our support of the OpenID Foundation by officially joining the board.

At first glance it seems contradictory for Facebook to join the OpenID foundation given that many people view Facebook Connect to be a competitor to OpenID as a single sign-on solution albeit a centralized one. The confusion from pundits around this announcement from Facebook is summarized in the Ars Technica article Facebook's "next steps in openness" raises questions which openly questions why the company needs to join the OpenID foundation when Facebook Connect seems to be enjoying broader deployment across the Web.

The reason seems quite straightforward to me. Right now, Facebook has created a situation where web sites that want to enable their users log-in with credentials from third party sites need to implement two solutions; an OpenID consumer and Facebook Connect. This places a burden on web sites which now either have to chose to adopt one solution over the other or create a user experience problem by offering users both options. It's bad enough that there is now a market for companies who wrap both solutions in a single package like JanRain and Clickpass. I wouldn't be surprised if Facebook has been getting an earful from some of their larger Facebook Connect partners about being a competing offering to OpenID.

That said, I doubt that a generic solution like OpenID will ever beat the ease of use and value added functionality that Facebook has created with Facebook Connect. By supporting OpenID, Facebook gets to silence the sites who simply want single sign-on solution that is built on standards so they can implement one solution to get access to users of Facebook, Google, Yahoo!, Windows Live, MySpace, and AOL's services among others. However anyone who wants the richer integration that comes with integrating with the Facebook mini-feed and live feed will still need to adopt the proprietary Facebook Connect.

The second interesting announcement about Facebook opening up comes from Chris Putnam in the post titled Opening Up Facebook Status, Notes, Links, and Video to Facebook Platform which is excerpted below

We've seen increasing engagement with over 15 million users updating their status each day and sharing over 24 million links per month. We wanted to make sure this content and the ability to share this content was available through our standard APIs.

Specifically, your applications can now directly access all of a user's status, links, and notes via new methods and FQL calls. Your application will have access to any status, notes, or links from the active user or their friends that are currently visible to the active user. In addition, we're opening new APIs for you to post links, create notes, or upload videos for the current user, and we've made setting a user's status easier.

We're pretty excited to see what kinds of ideas you can come up with to help users create and share more content.

Like Facebook Connect, this is a further step away from the walled garden approach that characterized the Facebook platform of 2007. In 2007, the goal of Facebook's platform efforts was to tell websites to re-implement themselves as Facebook apps (e.g. iLike website vs. iLike Facebook app). With Facebook Connect and the changes to their APIs announced above, Facebook is now acknowledging that their users use other websites and integration with those sites doesn't require these sites to become sharecroppers on the digital farmland that is the Facebook canvas page.

Twitter has shown the value of having open APIs for link sharing and status updates which isn't lost on Facebook given their failed attempt to acquire Twitter. Sharing status updates is a powerful way for humans to connect in social contexts and given Facebook's goal to be the world's social operating system we can expect them to make more moves in this space. It's particularly interesting to see how people use status updates as a way to communicate and share experiences during news events such as President Obama's inauguration. Facebook saw this first hand with their integration of Facebook's status updates with the CNN website where Randi Zuckerburg wrote

Over 2 million status updates were posted through the CNN.com Live Facebook feed with 4,000 status updates per minute on average and a huge spike of 8,500 updates when President Obama began his speech. We're thrilled that you and so many others chose to actively participate as history was being made—by sharing the experience with the people that matter most to you.

Similar surges were seen on Twitter as evidenced by the chart below. The thing that is interesting to note is that while status updates increased during the most exciting part of the inauguration other forms of Web traffic declined at the same time.

Similar traffic drop on Last.FM seen on the right

Traffic Drop to Last.FM during Obama inauguration on right

Google saw a similar drop as well

Traffic Drop to Google during Obama Inauguration

Was it because everybody went to Twitter?

Traffic Spike on Twitter during Obama Inauguration

Charts taken from the post Understanding Web Operations Culture - the Graph & Data Obsession on the O'Reilly Rader blog.

UPDATE: I've been playing around with the APIs announced and it looks like there actually isn't an API to get your friends' status updates included in the announcement. The status.get method only returns the status updates posted by the currently user. The closest I could get was trying the query below via fql.query but it never returned results

SELECT uid, message FROM status WHERE uid IN (SELECT uid2 FROM friend WHERE uid1=$userid)

So much for the claims that this is a Twitter killer.

Note Now Playing: Eminem, Dr. Dre & 50 Cent - Crack a Bottle Note


 

This morning I was reading Om Malik's post entitled Google & The Big Ideas where he writes

Earlier today, when I read about Google launching a mobile version of Tasks. I was amazed by the attention being focused on essentially a to-do list website. And while it wasn’t worth a story, I shared my feelings via I sent Twitter. My tweet read:

I think google has no big ideas. this morning they announced a to-do-list. FGS. [For God Sake] Remember the Milk MUCH better.

...
Matt’s comments and the responses both on this blog and FriendFeed resulted in some thoughts about what constitutes a big idea, where Google is right and where it is light. Instead of responding on
FriendFeed, I decided to share my thoughts with you, hoping that we can have a larger conversation about Google and the big ideas.

For me startups and products such as Skype, Flickr and YouTube represent big ideas. Why? Because they not only redefine our notions about certain technologies, but they also change our behavior and cause massive disruption. For instance, Skype redefined our relationship with our phone and in the process put disrupting the telecom industry. Flickr made a largely way web into a dynamic, thriving social community. Today even our friends at Wall Street Journal have comments, and the New York Times is hoping to use LinkedIn to foster a community. YouTube made us rethink television, by making it dead simple not only to consume video but also to broadcast video.

Similarly, Google’s Search changed how we consumed information. Instead of going to destinations, we now consume information by just finding it. What made this “big idea” even more disruptive — Google’s use of data analytics to offer highly focused advertising messages to marry search queries. (Of course, Google wasn’t the one to think of this big idea, but that’s a whole another story.)

The problem with "Big Ideas" is that sometimes people get obsessed with how game changing or disruptive their product is instead of focusing on making it the best at what it does.

I remember a few years ago when every other article out of the technology press was about how innovative every product Google created was. For a while, this created a scramble amongst various Web companies to show that they could be just as innovative as Google. Yahoo! tried to do this by buying innovation in the form of every hot startup they could get their hands on (Flickr, del.icio.us, Jumpcut, Webjay, Konfabulator, Upcoming, etc) which only led to spreading itself too thin as eloquently captured in Brad Garlinghouse's Peanut Butter Manifesto memo.

On the other hand, there are lots of products that have been unoriginal ideas now seen as game changing because of how these ideas have been executed. One example is the iPod + iTunes which started of as yet another MP3 player with a proprietary music player but has grown to be a cultural force and the number one retailer of music in the United States. When Facebook launched it plowed ground that had already been covered by MySpace, Orkut and Friendster yet today it is the number one social networking site in the world. In both cases, these have been very focused products that have been careful to grow their feature set in a limited way but have done an excellent job in providing a very user-centric experience. This isn't to say that there aren't any innovations in Facebook or in iTunes+iPod but instead that they are examples of products that have been game changing not by being a "big idea" but instead by being full of lots of good ideas.

Being original or innovative is nice but even better is building a product that your customers love. Never forget that.

Note Now Playing: Justin Timberlake - What Goes Around.../...Comes Around Interlude Note


 

From the Live Search team blog post entitled Live Search autosuggestions come to Firefox we learn

We're happy to report that we've officially integrated Live Search into Firefox by popular demand.
...
The Live Search add-on for Firefox is available to install at
https://addons.mozilla.org/en-US/firefox/addon/10434. It's based on the Open Search standard and uses the JSON interface supported by Firefox to retrieve autosuggestions.

Image of Live Search autosuggestions in Firefox

I'm glad to see this finally get out there since I was one of the popular demanders at work. If you're a Firefox user who's also a fan of Live Search then this is a must have extension. It's definitely improved my browsing experience when I've had to use Firefox.

By the way, it's an interesting insight into the different user bases to compare the suggested searches from Google with those from Live Search for a particular phrase.

Note Now Playing: Kelly Clarkson - My Life Would Suck Without You Note


 

Categories: MSN

From the blog post on the Office Live team blog entitled Looking ahead and bringing you even more we learn

Today, I wanted to share with you some exciting news about Office Live: To simplify and improve the customer experience around our Live services, we’ve made the decision to converge Windows Live and Office Live into an integrated set of services at one single destination. We think that just makes a ton of sense and goes a long way toward giving you a simpler, richer, better service that allows you to do more with one account.

Every day, more and more people are signing up for Office Live Workspace and Office Live Small Business (4 million of you so far!), as well as Windows Live (460 million to date!).

Secondly there’s the MSDN forum post entitled Working Together: Live Mesh and Windows Live by the Live Mesh team which informs us that

For some time now, many of you have expressed interest in seeing some sort of combination of Live Mesh and other Microsoft services. In order to further explore these ideas we would like to ask you to share with us the scenario(s) that you have in mind. 

What combination(s) are you interested in, and why? Whatever your interests, whatever problem you’re trying to solve or scenario you want to enable, we’d like to hear the details – and the more specific you can be, the better.

We know you have ideas – this is the place to share them!

Thank you,

The Live Mesh Team

I love it when things come together this way. There's been a lot of choice in Web-based storage solutions offered by Microsoft and some would argue that it's been too much choice. It will be good to how the cross pollination of ideas ends up working out between these various products over the coming months and years.

If you are interested in developer or end user scenarios around Web-based storage I recommend chiming in on the MSDN forum post linked above. It's your chance to give your feedback to Microsoft and help influence the direction of the most innovative technology product of the past year

Note Now Playing: Amy Winehouse - You Know I'm No Good Note


 

Categories: Windows Live

Sarah Perez over on ReadWriteWeb has a blog post entitled In Cloud We Trust? where she states

Cloud computing may have been one of the biggest "buzzwords" (buzz phrases?) of this past year. From webmail to storage sites to web-based applications, everything online was sold under a new moniker in 2008: they're all "cloud" services now. Yet even though millions of internet users make use of these online services in some way, it seems that we haven't been completely sold on the cloud being any more safe or stable than data stored on our own computers.
...
Surprisingly, even on a site that tends to attract a lot of technology's earliest adopters, the responses were mixed. When asked the question: "Do you trust the cloud?," the majority of responses either came back as a flat-out "no" or as a longer explanation as to why their response was a "maybe" or a "sometimes." In other words, some people trust the cloud here, but not there, or for this, but not that.

The question this article asks is pointless on several levels.  First of all, it doesn't really matter if people trust the cloud or not. What matters is whether they use it or not. The average person doesn't trust computers, automobile mechanics or lawyers yet they use them anyway. Given the massive adoption of the Web from search engines and e-commerce sites to Web-based email and social networking services, it is clear that the average computer person trusts the cloud enough to part with their personal information and their money. Being scared and untrusting of the cloud is like being scared and untrusting of computers, it is a characteristic that belongs to an older generation while the younger generation couldn't imagine life any other way. It's like Douglas Adams wrote in his famous essay How to Stop Worrying and Learn to Love the Internet back in 1999.

Secondly, people are often notoriously bad at assessing risk and often fail to consider that it is more likely that data loss will occur when their personal hardware fails given that the average computer user doesn't have a data backup strategy than it is likely to occur if their information is stored on some Web company's servers. For example, I still have emails from the last decade available to me in my Hotmail and Yahoo! Mail accounts. On the other hand, my personal archive of mail from the early 2000s which had survived being moved across three different desktop PCs was finally lost when the hard drive failed on my home computer a few months ago. I used to have a personal backup strategy for my home desktop but gave up after encountering the kinds of frustrations Mark Pilgrim eloquently rants about in his post Juggling Oranges. These days, I just put all the files and photos I'm sure I'd miss on SkyDrive and treat any file not worth uploading the cloud as being transient anyway. It is actually somewhat liberating since I no longer feel like I'm owned by all my digital stuff I have to catalog, manage and archive.

On a final note, the point isn't that there aren't valid concerns raised whenever this question is brought up. However progress will march on despite our  Luddite concerns because the genie is already out of the bottle. For most people the benefits of anywhere access to their data from virtually any device and being able to share their content with people on the Web far outweighs the costs of not being in complete control of the data. In much the same way, horseless carriages (aka automobiles) may cause a lot more problems than horse drawn carriages from the quarter ton of carbon monoxide poured into the air per year by an average car to the tens of thousands of people killed each year in car crashes, yet the benefits of automobiles powered by internal combustion engines is so significant that humanity has decided to live with the problems that come along with them.

The cloud Web is already here and it is here to stay. It's about time we stopped questioning it and got used to the idea.

Note Now Playing: Amy Winehouse - Love Is A Losing Game Note


 

Categories: Cloud Computing