Are the data sources for Waffles and the Chrome visualizer different? It sounds like Waffles is real-time and the Chrome visualizer is not real-time. Do they use the same macros and route the buffer differently? Or do they have entirely different systems for gathering the profile data?
Waffles is more than just a profiler. It is a nice, high level interface into our (non-public) debugging API. You are correct that the profiling info there is real-time, while Chrome is post. They all use the same buffers, but just interpret the data a little differently.
There is also other profile info which is gathered by Waffles, stuff like number of visible particles, texture calls, GPU cost per emitter, amongst others, and that information is gathered through another interface.
Part of the value was that the dumps were updated weekly.
Say you're using it to get a list of named entities (proper nouns). The purpose is to cluster news stories about a given entity (if you look at Facebook's Trending News, each headline begins with a proper noun followed by a blurb. Not sure if they use Freebase, but it could be a useful input).
The value of Freebase will decline over time as the content becomes out of date.
The Wikidata dumps are also updated weekly; see [1].
Wikidata RDF exports are made every two months or so from those dumps and are available at [2]. I imagine that frequency will pick up. You can generate your own RDF exports using the Wikidata Toolkit [3, 4].
As always, don't consider this advice to be a golden rule or silver bullet.
Separating fun and addictive can be really tough. I think many people show signs of addiction when playing their favorite games (which are probably the games they say are most fun). Just because you don't think Farmville is fun, doesn't mean it's not fun for someone else. Even if we assume that the tens of millions of Xbox owners all dislike Farmville, that's only a small subset of the hundreds of millions on Facebook.
Also, browser games can sometimes be less complex than a 3d AAA PS3/Xbox game that's built "from scratch". If users need to play it to "get it", you might be better off skipping the video and moving straight to creating a prototype that showcases the addictive features.
And a tool to instantly search and view salary distributions: https://orcahq.com/salaries