I'm really not for anything that can't readily be done in HTML5+CSS3+JS atm. Especially If i need to make people _download_ a 'player'. What is this, 1999 all over again (some might say yes ha).
I can see big corp. getting excited over this just like 99% of the crap they buy and don't use.
That said, this doesn't exactly move forward with global progress on the problem or solution (as well it shouldn't wolfram is a corp after all... in the business to make money).
I don't think the average person on HN is the target audience for this in the first place. If you know HTML5 and Javascript and work in a web-based environment most of the time, then this probably won't help you much.
On the other hand, if you are, like me, one of the many people in academia who would love to have a way to embed interactive graphs and tables into your papers to make them more understandable for the reader, then this is potentially very useful. Especially since very few people in academia (outside CS departments anyway) know or have any interest in learning HTML5, and many already use or have easy access to Mathematica to begin with.
Also, Wolfram being a corporation is irrelevant. Some problems are best solved by large corporations trying to make money. That may or may not be the case here, but they definitely have an incentive to keep the format open (in some sense) and promulgate the free CDN reader (much like Adobe has done in the past).
For sure, web developers and programmers can do most of what CDF can do, on their own, in HTML5. It might take them a lot longer, but they could certainly end up with a nice finished product.
This doesn't solve the problem. The problem is neatly illustrated by the fact that news organizations, which have a huge incentive to make compelling, sticky interactivity that wraps their news properties, haven't gone for it. I've only seen two non-trivial uses, the NYT and BBC News, and its clear these were bespoke jobs that cost them a lot of money.
The same goes for textbook publishers, scientists, NGOs, etc, anywhere were technical communication could be significantly improved with interactive documents. This problem remains unsolved.
CDF aims to make it possible for someone to crank out an interactive figure or document in a matter of hours, not weeks, with very little code.
A side comment: I say this without any real proof, but WRI specializes in doing interesting things that are economically self-sustaining, rather than things that make a lot of money. Mathematica is far from a cash cow, and WRI is a small company (~500 people), but it has lasted 25 years, and it regularly adds cutting edge technology to its portfolio. Obviously, it gets to balance profit with "interestingness" mainly because it is privately owned, and Stephen likes collecting interesting people and interesting projects for them to do.
I think a better solution is to develop a standard HTML5, CSS and JavaScript combo that researchers can use to publish articles online. The requirements are that using it should be no more difficult than writing papers in Latex, and the layout results should be equally as good.
I've thought about this for a while now. It seems terribly silly for us to spend so much time formatting our papers as pdfs when people mostly read them on a computer anyway. I've been to conferences that - smartly - don't even print the proceedings. They just hand you a USB key with all of the papers and a table of contents in HTML that has authors and titles that links to the correct file.
What we really need is a latex compiling tool like pdflatex except the output is a series of HTML files. And while I know that there exists some versions out there, we really need one that doesn't suck, along with internet appropriate style files, that just spits out html+javascript+css.
But as an end-user, I don't want a series of files. Source code is a major pain in the ass if you're not actively working on it. the whole win of PDF for most people, including me most of the time, is that I don't want to edit the document, but everything is neatly contained within a single file that is ready for printing or viewing with no additional libraries, dependencies, or anything else but a PDF viewer.
I have a few thousand pdf files on my hard disk and already find it hard to manage the collection. If every single on of them had a source tree it would make me cry.
If you're willing to go through a build step, it's fairly easy to get everything into a single document. Sproutcore does it today with no special configuration. There are tricks to getting large amounts of content to load in a performant manner and you'd have to do history API to get transparent support for an entire site but neither hurdle is particularly high. You don't even have to invent a new format for specifying what makes up the site since the web archive standard already exists.
Multiple files is an implementation detail. When navigating through Finder in OSX, "applications" appear to be monolithic, and double-clicking on them will launch the application. But, they are actually just directories with the .app extension. You can navigate through them and inspect the files and subdirectories they contain. But you don't have to.
I know. I rather miss the option to just save a web page as a self-contained file in Chrome, because I used to use that all the time. It's not that you can't do the same things with web technologies, but that it's so much less convenient to do so. I think this is why Instapaper and Readability have become such big hits, because they offer simplicity and one-step document management. PDF does the same thing for more complex documents that need to be presented in a consistent fashion. This CDF format looks like it could be ideal for textbooks, instruction manuals and the like.
There's another comment downthread where I talk about why I don't actually want all the possible editing capabilities to be available most of the time. Sometimes you want to maximize convenience rather than control.
Maybe that's what you really need. CDF goes way beyond latex -- the idea is not to try to replicate ordinary paper-papers in a digital format. But to have programs that explain things through interactivity.
One (of the many i'm sure) problems here you defined are:
"...who would love to have a way to embed interactive graphs and tables into your papers to make them more understandable for the reader..."
The solution however may not necessarily be a private 'reader', 'player', or 'binary'. Though the 'format' may be 'open' this single implementation isn't.
You bring up Adobe which isn't a very good business case to follow as the very reasons I brought up are pressing the industry to move toward open implementations[1][2], away from 'free' binary distributions and plugins (for a various list of reasons from security[2], to access on other systems/apps).
This really isn't 1999, and CDF isn't yet a popular nor a de-facto standard[1] much like PDF was. Besides you and I are much more capable these days with newer and _open_ technologies are we not (browser, linux, open documents, etc...)?
Speaking of documents, other examples of 'perceived' open standard files are Microsoft's ill faded OSP[3] promise which spawned traction for OD/F[4] and other.
These reasons are why HTML5/CSS3/JS as a basis to create an open two way street for 'documents' and/or formats are so powerful. It is not enough to only provide an 'open' format, but also an open implementation. This way both use of and implementation of such product be beneficial toward academic progress. Why wouldn't that alone be worth it?
Thus a likely more popular solution I am proposing to your problem could be a service that uses HTML5/CSS3/JS in the delivery which solves your problem in a WYSIWG general user manner. Especially so as the very tools (your browser, and a million libraries must I really list them all?), UIX experience, and entrepreneurs (HN! Y-comb!) already exist!
To your quote "Some problems are best solved by large corporations trying to make money" I would say the same to "Some problems are best solved by small groups of entrepreneurs or open source developers trying to make money and/or looking for peer fame."
I would go further in saying that for 'open' standards and implementations, that small group of entrepreneurs or open source developers are the ones carrying the torch of open-ness [5][6][7][8][and on and on...] and innovation.
Additionally, the CDF player desktop app for Linux is a 200 MB behemoth. When I saw this, I immediately canceled the download. (For comparison: Adobe Reader is about 70 MB.)
I can see big corp. getting excited over this just like 99% of the crap they buy and don't use.
That said, this doesn't exactly move forward with global progress on the problem or solution (as well it shouldn't wolfram is a corp after all... in the business to make money).