Jean-Paul Van Belle responded to Kevin Osborne: >> as a techie: scepticism. I think the 'small code' >> and 'small hardware' people are kidding themselves. > Kevin, you're most probably right there. > But remember that us small code people *have* to > have this belief in order to justify ourselves > working as individuals / tiny teams often during > spare time and snatched moments. As a small code > person I think the chance of a small code > project achieving AGI is probably <1% > (still probably an optimistic estimate) that > that of a larger, coordinated, well-funded and > focussed research group. But some of us are loners, > like it that way, keep dreaming and thinking away.
Right on, Bro! (mon frere). Here is my small code, small hardware work of today: Today we gear up to do our first Mind.Forth programming since the 18jun06C.F version that has been on the Web since 18 June 2006. Back then, we switched to coding the JavaScript AI Mind that had not been updated since two years earlier, in 2004. Initially we worked on the timing problems of the main JSAI aLife loop, and then we worked on bringing the JSAI up to par with Mind.Forth AI. We were especially concerned with porting the Mind.Forth dynamic tutorial mode into the JavaScript AI, which had previously only a rotating tutorial message display and now has both the static but rotating message display and the impressively dynamic display. After coding the dynamic JSAI tutorial, we set about fixing bugs that had long been hidden in the JavaScript AI code, and were probably hidden also in the Mind.Forth code. At the same time, we were trying hard to implement slosh-over in the JavaScript AI, which we finally achieved in the 20mar07A.html version of the JSAI. Afterwards we made plans to further improve the JSAI before moving on to resume coding Mind.Forth, but yesterday we realized that the time to update Mind.Forth is now, when the JSAI has taught us what to do. It would be too risky and too imprecise to try to perfect the JSAI in advance of upgrading the Forth AI. Something could happen that might long or forever prevent us from getting Mind.Forth to work right, and it would be hard to know precisely when to stop improving the JSAI. The success of slosh-over in the JSAI is precisely when to code in Forth. We may find that we once again get far advanced in Forth, or we may be able to code Mind.Forth and the JSAI simultaneously now that since 20.MAR.2007 we finally know what we are doing in either language. Today we are running out of time and we have only just begun. First we spent precious time compiling a C:\MAR01Y07\JSAI\chglog01.txt file of "Changelog entries of the JavaScript Mind.html AI program." We need such a summary of our JSAI work so that we will know what we need to code in Forth. We may not have to repeat the exact order of the JavaScript changes, since the languages are different and since we may be able to take short-cuts & achieve slosh-over quicker in Forth. Next we spent quite some time updating our C:\MAR01Y07\JSAI\mfpjtemp.html file today so that it will be easier to do Mind.Forth coding from now on. We were updating the template file & this "fp070328" page simultaneously as we saw exactly what we needed to change to make our work easier. Upshot: We ran out of time for now & we need to monitor our Web situation. Arthur -- http://mind.sourceforge.net/Mind.html P.S. Ben Goertzel runs a big team but he has to clean the turtle tank and do other jobs in his embourgeoisement. ----- This list is sponsored by AGIRI: http://www.agiri.org/email To unsubscribe or change your options, please go to: http://v2.listbox.com/member/?list_id=303
