> In most languages there’s a sharp distinction between programs, and data, and the output of programs. Not so in the Wolfram Language. It’s all completely fluid. Data becomes algorithmic. Algorithms become data. There’s no distinction needed between code and data. And everything becomes both intrinsically scriptable, and intrinsically interactive. And there’s both a new level of interoperability, and a new level of modularity.<p>Sounds like Lisp :p
If you don't have time to read all of the way through, the "coming soon" portion is ready to take your e-mail at <a href="http://www.wolframcloud.com" rel="nofollow">http://www.wolframcloud.com</a>.
Reminds me of Brett Victor's “The future of programming” (<a href="http://vimeo.com/71278954" rel="nofollow">http://vimeo.com/71278954</a>), “Learnable Programming” (<a href="http://worrydream.com/LearnableProgramming/" rel="nofollow">http://worrydream.com/LearnableProgramming/</a>) and “Inventing on principle” (<a href="http://vimeo.com/36579366" rel="nofollow">http://vimeo.com/36579366</a>)
I remember wolfram alpha being marketed pre-release as something that would make Google obsolete. The only reason I ever use this is for math when I do not have access to a native alternative such as matlab. Considering that I use less math than I used to, I wonder why it is still relevant.