Named and Unnamed state.<p><i>"It seems that we need to have and not have named state at the same time. How do we solve this dilemma? One solution is to concentrate the use of named state in one part of the program and to avoid named state in the rest. The bulk of the program is a pure function without named state. The rest of the program is a state transformer: it calls the pure function to do the actual work. This concentrates the named state in a small part of the program."</i><p>This very closely resembles the philosophy behind Clojure.
Anyone used Mozart/Oz for anything?<p>This chapter is fascinating. Or rather has me fascinated with Oz. However, I see that Mozart was last updated in 2008.
This is Oz's set of primary datatypes: <a href="http://www.mozart-oz.org/documentation/tutorial/node3.html#label14" rel="nofollow">http://www.mozart-oz.org/documentation/tutorial/node3.html#l...</a><p>This is a god damned nightmare if you want to actually use the language. Why? Because each of these types has separate methods and syntaxes that are used for manipulation.<p>Go on, try to write something that is generic, I dare you.<p>Oz is, without a doubt, the best example of why you should not try to be everything to everyone that I have ever seen.
Mmm... Computer Science... 39 pages of things that have no bearing whatsoever on what I do every day while building a startup.<p>Does anybody here really care about any of this stuff? I program computers for a living, and I couldn't even muster the energy to page-down through that mess of tables and graphs.