Those days are over.

The problem is that most of the people running legacy news sites today are way older than I am, and still can’t get their arms around the fact that the world has fundamentally and irreversibly changed. Today I get my non tech news via scores of sources. I’m led there via social sites like Twitter and Facebook, and from aggregators like Google News and Memeorandum. Most of my tech news comes, of course, via my phone and email inbox.

It’s ok that the legacy guys don’t understand that, because when they erect paywalls it just stokes TechCrunch, which isn’t behind a paywall. Live and let live, I say. Far be it from me to talk them off the ledge. Paywalls kill social links and aggregators unless they are specially designed to allow them via a set number of free views. But even then there’s enough friction that most people won’t bother.

But when Mark Cuban starts saying aggregators are bad, that’s something new. He’s one of the guys that gets it. He’s not supposed to be on the losing

3Crowd’s first product is setting out to help users manage their content across multiple CDNs at the same time, using rule sets to determine which CDNs should be tapped depending on variables like the user’s location and which content they’re accessing.  The product also looks to make it easy to actually deploy your content to these CDNs — you have to create the account with the CDN, but 3Crowd can then walk you through a wizard to get things going. Lyon says that this changes the process from one that would typically require a programmer to one that’s managed through a clickable wizard.

So what’s the benefit from being able to easily spread your content across multiple CDNs? For one, you aren’t dealing with a single point of failure. But the rules-based platform also gives you more flexibility as to how you’d like to distribute your content. If you found a CDN based in the United States that was cheaper than the alternatives, you could

Facebook Senior Open Programs Manager David Recordon kicked off the event by walking the audience through some of the challenges Facebook faces, particularly with the dynamic pages it has to generate. He spoke about some of the benefits of various programming languages, and also the CPU costs of each. As it scaled, Facebook encountered problems with PHP, including high CPU and memory costs and difficulty developers faced to build extensions. But Facebook has a slew of talented PHP developers, and it didn’t make sense to rewrite the site.

The solution Facebook came up with is HipHop for PHP, which started as a hackathon project from a single developer named Haiping Zhao (though he had some team members as the project progressed). The technology transforms PHP into C++, using g++ to compile it.

Facebook has found that the technology uses 50% less CPU with equal traffic on its web tier, and 30% less CPU usage with doubled traffic on its API tier.

Facebook started deploying HipHop six months ago (initially it was only on internal servers). It’s now been ramped up to 90% of Facebook’s production servers.

Zhao took the stage to give a highly technical walkthrough of the benefits of the technology (watch the video below for the