Quote:
Originally Posted by Graham
You've described the use case for a Chromebook perfectly here. The only thing that a tablet does better in the above list is reading books.
|
Size matters. My 7" tablet is a good size to be an eBook viewer. The larger one I want down the road for other uses would be too big to do that conveniently.
No matter. I never assumed I would have a "one-size-fits-all" device, and assumed there would be more than one in the mix.
Quote:
|
What's more, a Chromebook can be used for light development and design - particularly if you're working with web technologies - and even light video editing.
|
There are plenty of folks using Chromebooks for development (like about half of Google's developers, as far as I can tell.) It doesn't even have to be web technologies. There's no reason a developer can't check out code from a repository, edit it locally, check it back in, then kick off a test build on a build server to see if it works.
Video editing is trickier, but I suspect if you have sufficient bandwidth, you could do heavier video editing - the work would be done on a server. The results would be displayed on your screen. You would just need a fat enough pipe that the fact the CPU doing the heavy lifting didn't happen to be in your machine didn't matter.
Quote:
|
I was amazed the other day to find that I could use it for music notation as well, something that I was sure I'd need to return to my Windows desktop for.
|
<blink> I'm amazed as well. I suppose I shouldn't be surprised in retrospect
Quote:
|
It'll be interesting to see how soon a touchscreen convertible Chromebook appears on the market.
|
Fairly soon, I should think.
The main issue with a Chromebook is that assumption that you are connected to the network and the data you are working on resides elsewhere. If you
aren't connected, the equation changes.
I don't have a Chromebook, but if I got one, it would need a reasonable amount of local storage for those occasions where I wasn't connected.
______
Dennis