You're looking at Less Wrong's discussion board. This includes all posts, including those that haven't been promoted to the front page yet. For more information, see About Less Wrong.

Ritalin comments on A website standard that is affordable to the poorest demographics in developing countries? - Less Wrong Discussion

10 Post author: Ritalin 01 November 2014 01:43PM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (58)

You are viewing a single comment's thread. Show more comments above.

Comment author: Ritalin 02 November 2014 11:33:35AM 0 points [-]

I'm just reporting my own problems the way they happen.

But back to the overall point, I thought the issue was about information availability, and not really personal apps. Do you have a major information site that is a problem?

Pretty much any site that employs graphic ads or that is otherwise graphic-heavy; wikias, news sites, fora... even dictionaries like thesaurus.com, wordreference, or leo.org can be a pain to load. The little menus that appear when one is making a search are especially sensitive to network lag. Thankfully there are offline, command-based equivalents to several of these dictionaries, but you have to look for them.

Plus, personal apps are extremely useful tools. To give just one simple example, why spend phone credit on calling or SMS when you can What's App? I'm sure we could come up with several app ideas that would have excellent time-saving or resource-saving capacities... and, once they learn how to code, who knows what the local whiz kids might come up with?

Comment author: buybuydandavis 02 November 2014 10:20:51PM 1 point [-]

Are you running ad block? That might help with the graphic ad loads.

Again, I'd guess it's latency and not speed that's causing you problems with menus. Looks like interaction is the issue, not bulk data download. For general browsing, I don't know that you can do much about latency, but for particular apps. sites, if they've got an android app, you use it.

Seems like android apps are much better about all that stuff, and they'll be more generally available for chrome os soon, and I see some windows methods for this as well.

There are serious and well funded grownups working on this at Google.

Interesting to hear about the issues, though. You encouraged me to test out the chrome book I'm working on for my mother. Still slow by my standards, but I think it will be fine for her.