<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
My dream is that someone ports gnu/linux to run on low-cost tablets.
Rabi Karmacharya, with lots of experience, believes we need at least
a 10in screen. <br>
I think the tablet needs to be in a leather (or substantially
ruggedized) case with a keyboard (wired usb or wireless).<br>
<br>
Suppose someone approached you with the idea of sponsoring a one
laptop per child deployment in the developing world. This would <br>
require 200 laptops. What platform would you recommend? <br>
<br>
How would an Android tablet work without any possibility of
connection to the internet?<br>
<br>
I believe that a deployment is a system. Tediously, I have claimed
the essential need of a school server to provide the content which <br>
is not available without the internet. The deployment must have a
way to charge the laptops and to power the server and its local
network. <br>
<br>
For me, the most difficult thing has been to find a way to inform
non-technical users on how to take good advantage of the laptops in
the absence of an on-site system adminstrator. Addressing the
problem was why I was so intrigued by the 'onboarding' idea.
Typically, I get 1-2 weeks at a deployment per year. My model is a
ball which needs a shove periodically to counter friction and keep
it moving.<br>
<br>
Luckily there is no pressure to move away from standard software on
the server side (CentOS). <br>
<br>
Tony<br>
<br>
<div class="moz-cite-prefix">On 04/06/2016 02:59 PM, <a class="moz-txt-link-abbreviated" href="mailto:sam@sam.today">sam@sam.today</a>
wrote:<br>
</div>
<blockquote cite="mid:1459925969.1726.0@smtp.gmail.com" type="cite">
<div>Hi Dave,</div>
<br>
On Wed, Apr 6, 2016 at 10:46 AM, Dave Crossland
<a class="moz-txt-link-rfc2396E" href="mailto:dave@lab6.com"><dave@lab6.com></a> wrote:<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_extra">
<div class="gmail_extra">I would be happy if by 2020 the
"classic" Sugar desktop was totally gone. Zero Python!
In its place could be a laptop OS derived from
ChromiumOS, plus a nodejs web server serving on
localhost that is stuffed full of activities and
content. </div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>Why? Why do we throw out the great technologies we have now?
Why do we waste out time replacing Telepathy (amazing back end
for collaboration)? Why do we waste our time replacing
GtkSourceView? AbiWord? WebKitGtk? Gtk? These are great
technologies. Sure they are not the current trend. But unlike
your proposed nodejs server, we don't end up in callback hell.</div>
<div><br>
</div>
<div>We have a technology stack that we have used for over 10
years. Those people who OLPC paid to start writing sugar made
good choices; they left us with a great foundation even as OLPC
down sizes. It works great across keyboard, mouse and touch
(can sugarizer even show a tooltip on long touch?). It works
great on slow computers (my trusty old Core2Duo laptop runs
sugar faster than Sugarizer/webkit). It works great off-line
(collaboration over salut doesn't need a centeral server). And
all the activities are written in python now.</div>
<div><br>
</div>
<div>Why waste time to javashit it? You can install GNU on a
chromebook, you can install GNU on computer, you can install GNU
on some tablets. Those are the pedagogic devices of now and the
future. Those run faster with Gtk than with WebKit.</div>
<div><br>
</div>
<div>Don't waste time.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Sam</div>
<div><br>
</div>
<div>[GNU in this post refers to GNU/Linux]</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Sugar-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>
<a class="moz-txt-link-freetext" href="http://lists.sugarlabs.org/listinfo/sugar-devel">http://lists.sugarlabs.org/listinfo/sugar-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>