> A Chromebook can only be used to surf the web. It's the polar opposite of what an educational institute needs.
Chrome OS is a highly customized version of Gentoo at its core. When you activate developer mode, you get access to a full Linux distro. Some people use Portage to install extra tools, some use Crouton to install Ubuntu alongside Chrome OS (they share the same kernel as opposed to dual-booting).
Heck, even if you don't use developer mode, there are some cool JavaScript programming tools that you can download and run locally in the browser.
A decent screen, a decent keyboard, comes with a word processor, is low maintenance, doesn't get viruses (theoretically at least) and it can access the web. That sounds pretty good to me.
If I'm a college student, I really don't want to deal with OS upgrades, malware and other things. I just want something that works out of the box and Chromebook does that perfectly. If I really want to tinker, it's not that hard to install a linux distro in a Chromebook and not everyone desires to tinker with their computers.
The comment "I really don't want to deal with OS upgrades...", does not make sense, as I would think a student (at least when I was one) we wanted to upgrade our OS and for free made it even better. You can also customize a Linux REALLY easy, and that is something as a student I was looking for. So low cost and great power is what at least a tech student would be looking for.
And, if you use Linux, 1. Update regularly, again I guess most distros have a default option to check for updates on boot. And, you don't need to upgrade your OS unless you want/have to.
How much more do you want to dumb it down? For basic use as you mentioned, to research and write articles, you are almost doing nothing already with windows/linux
I know this is an aside, but one of the things that irritates me most about the modern web, and Google's "solution" especially, is photo management. Picasa on the desktop is simplistic but generally 100% ok, but Google+ Photos leads to horrifically unpleasant workflows, and god help you if you want print anything or share on non-Google properties.
Recently I discovered that Google+, Facebook etc. all like to interpret "sharing" a photo to mean sharing a link to the page with the photo on it, not to actually share the photo, which is what the user really wants to have happen, not to mention the PITA this is to automate because it suddenly means these photos are behind authorisation walls. (This is on top of how aggressively Google tries to get any photos you take, or send via Gmail, into G+ in the first place).
Quite honestly I've had it with any cloud service that acts like this, and now choose to spam them with irrelevant nonsense of no consequence.
As for Linux, it's great, doesn't even need to boot to check for updates (I never turn my laptop off, just suspend - doesn't get rebooted for weeks), and you can lock it down sufficiently to prevent tampering/breaking, but there's not many consumer computers with a full Linux distro other than the Raspberry Pi - which would be great, but still 30 dollars each + peripherals is much more than $0.
One lingering unease I have about the first use-case, though, is that it forecloses some unplanned exploration. I largely got into tech by fiddling around with lightweight programming on machines that weren't explicitly bought to teach programming. Perhaps web-based dev environments will fill that gap, though; someone with a Chromebook can still experiment with anything from Codeacademy to jsFiddle to sketchpad.cc.
- repl for a handful of languages from javascript to haskell with lisps in between.
- jsfiddle to learn ~basic client-side webdev.
- canvas/webgl to learn ~basic graphic programming.
- if you dig deep enough you have VPRI OMeta for parser/metaprogramming.
- if you're not in a hurry you can even learn ~basic unix (busybox, gcc 4.3) on Fabrice Bellard's jslinux
I don't think you can learn prolog easily though.
There's HTML5/Javascript IDEs which run entirely client-side which you can install in the browser's cache, or keep the file in your file system. You can give web apps native features and define how it installs/behaves using the App Manifest.
A browser nowadays can do nearly as much as a full OS, even within a full OS.
Why? It's a much more limited device with much less potential for learning essential skills.
A Chromebook can only be used to surf the web. It's the polar opposite of what an educational institute needs.