<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">To: all the parties who are worrying about this ...<br><br>Given the history (not just PARC but going all the way back to the enormous differences of style and results from the ARPA community compared to the Bell Labs community), why is there any burden of proof here? <br><br>For example, we published in 1983 a still readily available (including online) book (Smalltalk-80 and its implementation) about how Smalltalk is implemented and bootstrapped, and there is a readily available paper about the more recent Squeak version which was built on that. And there is ample information available at the Squeak site.<br><br>Folks who are "willing to understand" actually put some effort into it instead of jumping to conclusions
based on internal logic and scant information rather than available external evidence. We have seen many claims about many things -- for example, where the "source code" might or might not be -- but scant evidence that any effort was made to find out. <br><br>As I mentioned previously, this seems more like "stories than reality". And it seems like a culture clash, where one culture thinks it is somehow "standard", and other ways are not.<br><br>The use of an "image" goes back further than Unix and C text files (one of the earliest good versions of this was BBN Lisp, which became Interlisp, in the latter part of the 60s), so this is at least as standard as any other way to build things. At PARC, this idea went further, because Smalltalk served as the entire environment of the PARC computers, and there was no separate OS, file system, etc. If you think about it this way, then you can see that the Smalltalk image is simply the entire virtual environment
for Smalltalk computing. So it is quite equivalent to the package of stuff in the Unix world that includes text files, OS, tools, etc.<br><br>The "sources" and "changes" files (the changes are the incremental history to the sources) don't have to be external to the image, but they have been made so since Smalltalk started to be implemented on computers that had fallen back to the bad old idea of operating systems and file systems. This is easy to find out about in a variety of ways.<br><br>But there is something further to ponder about this method from the 70s. And that is the idea that as scaling advances under Moore's Law, it will be less and less a good idea to rebuild from scratch (and more and more difficult). For example, the most comprehensive object oriented system on the planet is the Internet itself, with the hardware computers as the objects, and TCP/IP as the underlying messaging system. This was invented and built by the very same computer
research community (ARPA/PARC) that invented and built Smalltalk, the personal computers, GUI and Ethernet, etc., at PARC. <br><br>Part of the idea here was that computing is going to have to learn how to completely build and completely change all computer systems <span style="font-style: italic;">while they are running and without being able to take them down for maintenance</span>. This was done successfully for the Internet and for Smalltalk. Another part of the idea is that if you have a really strong and better system, why not be able to use it to improve itself (why go back to decontextualized editors and simplistic systems builds, etc.)?<br><br>In any case, all of this has been well documented and available for decades. I, for one, am happy to answer any questions put to us about how our system works (why it bootstraps so well and completely), but I have no interest in spending any time defending against opinions that are not well
informed.<br><br>Best wishes to all,<br><br>Alan<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Edward Cherlin <echerlin@gmail.com><br>To: Yoshiki Ohshima <yoshiki@vpri.org><br>Cc: its.an.education.project@tema.lo-res.org; devel@lists.laptop.org<br>Sent: Friday, June 27, 2008 6:44:26 PM<br>Subject: Re: [IAEP] etoys now available in Debian's non-free repository<br><br>
I am no slouch at understanding a bootstrap process, but it has taken<br>me a few days to find the information I'm trying to understand by<br>myself, given the refusal to even consider that someone might need<br>this information in order to answer Debian's concerns, and thus the<br>refusal to provide the pointers to it. So it is no surprise to me that<br>Debian still has those concerns. It is no good being right if you<br>can't explain or demonstrate _why_ you are right in terms that make<br>sense to someone else who is willing to understand, but doesn't know<br>how.<br><br>On Fri, Jun 27, 2008 at 11:17 AM, Yoshiki Ohshima <<a ymailto="mailto:yoshiki@vpri.org" href="mailto:yoshiki@vpri.org">yoshiki@vpri.org</a>> wrote:<br>> At Thu, 26 Jun 2008 23:43:45 -0700,<br>> Edward Cherlin wrote:<br>>><br>>> I think that the result of all this is that we can produce all of the<br>>> C (or some other language, maybe CLOS) and Smalltalk
source files that<br>>> Debian wants (even if we think of the C as compiler output, we don't<br>>> have to bother them with that interpretation.) One of the compilers<br>>> translates a subset of Smalltalk to C, but I gather that other<br>>> compilers can translate all of Smalltalk/Squeak/Etoys/what you like to<br>>> their chosen target language.<br><br>Now I see that this is unnecessary. We have the directly executable<br>Smalltalk source for the VM, including memory management and graphics<br>primitives written in Smalltalk. It is already in the .sources files.<br>We can therefore provide all of the source code for Etoys in a<br>conventional file system in the way that users of compiled languages<br>expect. This may be necessary in order to educate the Debian license<br>people. It might even be useful to somebody who wanted to base another<br>language on Smalltalk. Yes, they should probably modify the
Smalltalk<br>interpreter in the image instead, and use Smalltalk to run, test, and<br>debug it, and export/translate/compile everything necessary once it's<br>all working. But it's their choice.<br><br>>> As I understand it, Debian wants to see<br>>> a commented set of semi-human-readable code in ASCII files (although<br>>> we can discuss using Unicode source) together with various multimedia<br>>> files in known open formats, from all of which an Etoys image can be<br>>> constructed, and they don't care how we generate them, or what mix of<br>>> languages we use, as long as there are Free/Open Source compilers and<br>>> any other needed apparatus for them.<br>><br>> As Alan precisely put it ("we are dealing with stories, not<br>> reality."), this seems to be a backward way to work on this problem.<br>> When (if) Debian guys asked something based on wrong understanding,<br>> what we should
do is not to cater the wrong story, but have them have<br>> real understanding.<br><br>Right. So that means we have to educate them. Which means, just as in<br>Piaget's research, we have to educate ourselves first about how the<br>Debian people have constructed their understanding of the programming<br>process, and how we can assist them to construct an improved model.<br>Saying, "We're right! What's the matter with you people?" doesn't cut<br>it.<br><br>I find it useful to meet people half way in such a situation. Well, we<br>don't have to have our code in a conventional file system, but here is<br>how you can fairly trivially create such a file system and rebuild an<br>image, even though we never do this in practice. Well, almost never.<br>Aha! You can do it that way, somebody might need to do it that way,<br>that's what I'm looking for in the first place. So give. Don't tell me<br>I don't need to know.<br><br>I want to _see_ that fairly trivial
script. I want Debian to see it<br>and to be able to run it and examine its output. Once they understand<br>how one can generate "source code" in the traditional form whenever<br>desired from the real source, and where that real source lives, they<br>may be able to believe in using the code in the image and not<br>bothering with generating a conventional representation. They seem to<br>want proof that we can do something unnecessary but comforting. Well,<br>it shouldn't be any real effort, so why not give them that<br>demonstration?<br><br>We had an issue like this in the IETF on multilingual URIs in<br>ASCII-encoded UTF-8. It was claimed that this would break everything,<br>so we showed how to translate between this form and normal UTF-8 in<br>two or three lines of Perl for each direction. The final question was<br>whether Japanese users would be able to type a mixed ASCII-Japanese<br>URL containing Katakana, Hiragana, and Kanji. So I didn't just
say,<br>"Motiron dekiru naa! Nihonjin wa baka da to omou desyou ka nee?" I<br>gave it to them, keystroke by keystroke, with the keyboard layout and<br>IME switching and the conversions to Kana and Kanji. And then they<br>said, Oh, of course. Now I can see that there isn't a problem. OK, we<br>can make a standard for this.<br><br>> The reality is that the all description of classes and methods are<br>> already accessible (even in text files like .sources and .changes) and<br>> anyone can see all the code, and modify in the way the core developers<br>> do. That is the equal basis we provide to the world. Giving the<br>> translated stuff, except the C code for the virtual machine that is<br>> needed for bootstraping purpose, is wrong.<br><br>Somebody, somewhere, gave Debian the impression that .sources and<br>.changes do not contain the code for everything. I don't know how this<br>happened. You are almost correct that
we don't need to show them the<br>translated stuff. But given the damage that has been done, we now have<br>to show them the entire process from full Smalltalk source to<br>generated code to new image, and the generated C is part of that<br>process, even if not source.<br><br>So let's just show them where all the code is and how to get at it in<br>a way that they already understand, so that they can begin to<br>understand why they don't need to do it that way.<br><br>Who here is with Debian? Whom do we have to convince?<br><br>> David, Antoine, and Jonas, thank you for the comments. But let us<br>> not take this way anyway.<br>><br>> (Still I see some comments that says "the source code is in the<br>> image" but it is absolutely false. In the image, the compiled result<br>> of source is stored, and the texual code is always kept outside of the<br>> image.)<br><br>Yes. Good. Show them.<br><br>>
David:<br>> ----<br>> breaking out the .source and .changes files that have been referred to in<br>> this thread and having the build process create the resulting blob that<br>> you use would probably be acceptable (and far more useful as people can<br>> then send out patches to those files)<br>> ----<br>><br>> We are already sending out textual files called "changesets" to<br>> people. That is the way we work.<br><br>That does not answer the question asked.<br><br>> Jonas:<br>> ----<br>> If I understand correctly, the Squeak community accepts patches<br>> generated from their binary images.<br>><br>> So the real question is, if images built from C sources can generate<br>> patches acceptable by the Squeak community.<br>> ----<br>><br>> "Generate" is a wrong word! We write code textually in a text editor<br>> (happens to be written in Smalltalk) and save it. Of course
the<br>> patches ("changesets") are valid, we accept them. We won't notice if<br>> the changesets are written in Squeak, a image running on different VM,<br>> Emacs or vi. It is just text. The only difference is that the effect<br>> of "accepting" (saving) takes effects right away, as it is running in<br>> the same session. Just as same as writing Emacs Lisp in Emacs.<br>> (Think writing lisp-mode.el in Emacs.)<br><br>I think that some people need to see a trivial example worked out step<br>by step. Otherwise they think they are arguing about something that<br>isn't even there.<br><br>So<br>* You open an object that lets you write code as text and run it.<br>* You define an object and its methods, giving the class(es) it<br>inherits from and the rest of the apparatus.<br>* Smalltalk stores this object as an object (duh).<br>* You test your definition.<br>* There is a way to write the code to an external file,
creating a<br>trivial changeset. You do this and quit.<br>* You show Debian or whomever the file.<br>* You open the standard image, which does not contain your new object<br>and methods.<br>* Then you show Debian the command that reads the file in and<br>processes it to create the object and methods.<br>* Then you run some command that sends a message to the object<br>resulting in some visible effect.<br><br>Et voila! Nothing left to misunderstand.<br><br>> The image contains pre-made objects starting from nil, true, false,<br>> etc., to the Compiler and beyond. It also contains pre-loaded artwork<br>> and user contents. But all of them can be modified, and accessed<br>> fully.<br>><br>> -- Yoshiki<br>> _______________________________________________<br>> Devel mailing list<br>> <a ymailto="mailto:Devel@lists.laptop.org" href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>> <a
href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>><br><br><br><br>-- <br>Edward Cherlin<br>End Poverty at a Profit by teaching children business<br><a href="http://www.EarthTreasury.org/" target="_blank">http://www.EarthTreasury.org/</a><br>"The best way to predict the future is to invent it."--Alan Kay<br>_______________________________________________<br><a target="_blank" href="http://Its.an.education.pro">Its.an</a>.education.project mailing list<br><a ymailto="mailto:Its.an.education.project@lists.lo-res.org" href="mailto:Its.an.education.project@lists.lo-res.org">Its.an.education.project@lists.lo-res.org</a><br><a href="http://lists.lo-res.org/mailman/listinfo/its.an.education.project" target="_blank">http://lists.lo-res.org/mailman/listinfo/its.an.education.project</a><br></div></div></div><br>
</body></html>