<html><head><style type="text/css"></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;">We are now several dimensions off topic ... Cheers, Alan <div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ---- From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> To: Bert Freudenberg <bert@freudenbergs.de> Cc: Education <its.an.education.project@tema.lo-res.org>; OLPC Devel <devel@laptop.org> Sent: Friday, May 9, 2008 4:59:04 PM Subject: Re: [Its.an.education.project] An OLPC Development Model On 10.05.2008 00:13, Bert Freudenberg wrote: > On 09.05.2008, at 20:31, <a ymailto="mailto:david@lang.hm" href="mailto:david@lang.hm">david@lang.hm</a> wrote: >  >> Bert, >>  if you try and say that the entire world is wrong in how it writes  >> software, >>    > > Actually, that's exactly what I think, and "entire world" includes  > yours truly ;) > But this isn't the place to talk about that (if you're curious, visit  > VPRI [*]). > > No, it's not foremost about how the software is written, but about how  > it is presented to the user. Unfortunately, interface design is much  > harder than just writing software. >  The VPRI stuff is scary because it proposes the equivalent of using assembler code to speed up C programs. Performing model checking against one piece of code, then replacing that piece of code with another one for speed reasons in production is really a horrible plan. It also makes it obvious that the mathematically correct code is expected to be unusably slow. > [...] > For example, the fastest way for me to retrieve a file is typing it in  > the system-wide search box on my machine, or into google. It doesn't  > matter where in the file system hierarchy or on which server it is  > stored. That is pretty much what the Journal would do, too. Also, the  > Journal will allow tagging, which is equivalent (but more powerful) to  > a directory hierarchy. Etc. >  Actually, tags are just the equivalence of file names and they are more efficient to use than simple searches. If you know exactly what you want and where to find it, searching for it is one of the worst choices possible besides random walking and active avoidance. With Mozilla/Firefox/Seamonkey, typing in the first few letters of the URL takes you faster to an often-used site (due to autocompletion) than using any search engine. In real life, searching is a last resort if direct access is impossible. If you keep your bike at a fixed location you can remember among other bikes in a bike shed, you walk straight to your bike and don't search for it. > [*] see <a href="http://vpri.org/html/work/ifnct.htm" target="_blank">http://vpri.org/html/work/ifnct.htm</a> >  Regards, Carl-Daniel _______________________________________________ <a target="_blank" href="http://Its.an.education.pro">Its.an</a>.education.project mailing list <a ymailto="mailto:Its.an.education.project@tema.lo-res.org" href="mailto:Its.an.education.project@tema.lo-res.org">Its.an.education.project@tema.lo-res.org</a> <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> </div></div></div> <hr size=1>Be a better friend, newshound, and know-it-all with Yahoo! Mobile. <a href="http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ "> Try it now.</a></body></html>