Re: [Sugar-devel] [DESIGN] XO1 | Same hardware, slower internet
[cc+=olpc-devel] Hmm, it'd be interesting to see how much of a performance improvement webkit offers. Also, should we consider loading mobile versions of websites on the XO-1? I don't know how good an alternative that might be. Could be leverage the school server in some way? Any other ideas? On Mon, Mar 28, 2011 at 19:25, Lucian Branescu lucian.brane...@gmail.com wrote: On 28 March 2011 23:01, Anish Mangal an...@activitycentral.org wrote: Hi, With time, as hardware gets more complex, software gets bloated up to use the excess processor cycles available. A part of it is the websites that get more content heavy, bulky and slow with time. Considering that the hardware on the XO-1 is not going to get any faster, and websites _are_ going to get bulkier, I see a problem gradually arising. For example, Google image search, blogger and other similar services have recently refreshed their websites to be more user friendly at the cost of being heavier. I have seen kids trying to use these heavier websites in the classroom and it results in more time being wasted because of a overall slower computer. I would like to get opinions on what will be an increasingly significant issue, as websites get more complex and the hardware essentially remains the same. -- Anish Webkit should help somewhat. Once the XO 1 gets a reasonably recent OS, Surf can be finished (in fact the porting could happen earlier, but I don't have time for it until late summer). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] XO1 | Same hardware, slower internet
Hmm, it'd be interesting to see how much of a performance improvement webkit offers. It's no big deal to run webkit-based browsers on the XO. For instance, all of my XO-1s have Midori installed. The question is - what is this performance improvement that you are looking for? I believe that in practice, it is the usability of a browser that is noticed the most, not the performance. What Midori has is a smaller footprint - what it does not have is a richer experience than Firefox - the result is that I myself prefer using Firefox on the XO-1 to using Midori on the XO-1. [In my opinion, the performance of the two is roughly equivalent (e.g., in showing YouTube videos).] It is worth noting that the Google Chrome browser, which *does* have the reputation (in the general public) of better performance, does not stand out on the XO (perhaps because its footprint is large). should we consider loading mobile versions of websites Regarding creating websites suited to web clients without much computational power -- why should the typical internet website owner bother? I'm going to assume there might be 100 users in the worldwide audience who are looking for glitz for every one user who is looking for fast rendition -- just look at the size of the images transmitted by the typical internet website -- in my opinion any image greater than 40KB will slow down a web client which does not have considerable computational power -- yet monster images abound. Regarding a project providing web transmissions specifically aimed at a classroom - the phrase mobile versions of websites is often applied to video information formatted to be displayed on phones - yet if there are XOs in the classroom, they have a significantly larger screen than phones. I expect what you are looking for is video information formatted to be displayed on *tablets* - it will come, but I don't know if it is available just yet. What is definitely useful is an aimed-at-classroom setup, where a teacher's (or lab experimenter's) mobile system broadcasts to multiple (pupils') XO *clients* in that classroom. [Think of it as a website aimed at XOs.] This setup ideally would use an XO for the system from which the video transmissions originate. The simplest way to provide such functionality appears to be a slimmed-down web *server*. [I've seen descriptions of such, but at the moment can't remember the name of that software (might have been proprietary).] Since such a website would be viewed at XOs, the webpages created for that site definitely need to take into account the limited computational power of the XO. mikus ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] XO1 | Same hardware, slower internet
Hi, With time, as hardware gets more complex, software gets bloated up to use the excess processor cycles available. A part of it is the websites that get more content heavy, bulky and slow with time. Considering that the hardware on the XO-1 is not going to get any faster, and websites _are_ going to get bulkier, I see a problem gradually arising. For example, Google image search, blogger and other similar services have recently refreshed their websites to be more user friendly at the cost of being heavier. I have seen kids trying to use these heavier websites in the classroom and it results in more time being wasted because of a overall slower computer. I would like to get opinions on what will be an increasingly significant issue, as websites get more complex and the hardware essentially remains the same. -- Anish ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] XO1 | Same hardware, slower internet
On 28 March 2011 23:01, Anish Mangal an...@activitycentral.org wrote: Hi, With time, as hardware gets more complex, software gets bloated up to use the excess processor cycles available. A part of it is the websites that get more content heavy, bulky and slow with time. Considering that the hardware on the XO-1 is not going to get any faster, and websites _are_ going to get bulkier, I see a problem gradually arising. For example, Google image search, blogger and other similar services have recently refreshed their websites to be more user friendly at the cost of being heavier. I have seen kids trying to use these heavier websites in the classroom and it results in more time being wasted because of a overall slower computer. I would like to get opinions on what will be an increasingly significant issue, as websites get more complex and the hardware essentially remains the same. -- Anish Webkit should help somewhat. Once the XO 1 gets a reasonably recent OS, Surf can be finished (in fact the porting could happen earlier, but I don't have time for it until late summer). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
