Year and years have passed by. There's something else going on here. I'll keep my speculations to myself.
On Fri, Dec 17, 2010 at 10:40 PM, Julian Leviston <[email protected]> wrote: > Usually, when I'm working on a development of any kind, I don't release my > half-baked ideas. > This has a two-fold advantage. Firstly, it means that when I *do* release > what I have to share, it's at a level that I'm prepared for people to > comment on - it's in a state that I'd consider developed enough that it can > be understood... and secondly, it stops people from "muddying up" my ideas. > I'm just not clever enough to put a pre-baked idea out there for "general > populace comment" until I'm at the point where I am sure I can pull the idea > off. In exactly the same way, I won't send this email that I'm writing until > I feel it's finished. > This is especially useful for times when I'm working very hard at something > - I don't have time to explain myself to people who aren't working at the > same level that I'm working. > I don't think we should be under any illusion that just because VPRI has all > of our best interests at heart means that they're going to release something > as open source before it's finished being "baked" at least to a certain > degree. To do so before it's ready would be irresponsible to both the > project and its intentions. It would water it down. When you're dealing with > powerful ideas, you really don't want them to be watered down. (ie > misunderstood). > > Julian. > On 18/12/2010, at 5:14 AM, Ken Ritchie wrote: > > I enjoy *both* the "writings" and the code. Bring it *all* on! > And the "active essays" are a great way to integrate them. > > Why? > [Writings] share vision, intent, possibilities, analysis, and background > stories. > [Codings] implement specific realizations and demonstrations of dynamic > concepts. > I am interested in both aspects, taken together when possible. > And, one can interact with, and explore an "active essay." > > Viz., "active essay." E.g., http://tinlizzie.org/jstile/#TileScript > Kudos!!! > > Cheers, > --Ken Ritchie (Atlanta) > > > PS, What was I thinking...? > > I used to say, "the code is the *ultimate* 'documentation' [of a program]" > ;-) > Now, I'm attracted to a more holistic embodiment, including code...and more. > > Historically, the world's code bodies have all too often been separated from > "the rest of the story" (to borrow a phrase from the late Paul Harvey). > > In recent years, the notion of "active essays" and other *integrated* > writing and coding systems have been promoted by members of the VPRI > community. > > I acknowledge that it requires significant effort to craft an active essay, > just as it does to form "code" or any other form of "writing." > > Please know that I appreciate the static writings, too. > E.g., VPRI Memo M-2003-002, "Background on How Children Learn" (Alan Kay). > > So, y'all keep on PLAYING, SAYING, *and* WRITING! > > Thanks again, > --Ken > ;-) > > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc > > > _______________________________________________ > fonc mailing list > [email protected] > http://vpri.org/mailman/listinfo/fonc > > _______________________________________________ fonc mailing list [email protected] http://vpri.org/mailman/listinfo/fonc
