But if you also have ~20 tabs open in your browser, and are streaming music etc... I am doing a thin client setup of sorts, and by the end of the day things start slowing down quite a bit.
I do agree that $1300 is too much, at that price range you might as well get a mac. If it was 600-800 i'd probably jump on it. However, I think the curve ball here is the touch screen. I'd be willing to bet that Google's strategy for this laptop is to do a smaller production run, and get these in the hands of tech/programmer types, and then use the lessons learned to develop a model targeted toward a wider audience.
> I'd be willing to bet that Google's strategy for this laptop is to do a smaller production run, and get these in the hands of tech/programmer types
If that's the case, pull an Apple and ship great dev tools on the installation disk. As far as I can tell, there are no top-notch Chrome OS development tools, just various ways to remote into a real machine to do that work.
Pretty sure Square disagrees, and they know what they're talking about when it comes to XCode. See PonyDebugger, a tool they wrote to pipe iOS apps' network connections and debug information through Chrome to take advantage of the developer tools: https://github.com/square/PonyDebugger
Now, you'd never write code in the Chrome Developer Tools (except maybe the occasional one-liner in the REPL). But the Chrome Developer Tools are great — best in class even — for profiling, visualizing, and debugging.
I do agree that $1300 is too much, at that price range you might as well get a mac. If it was 600-800 i'd probably jump on it. However, I think the curve ball here is the touch screen. I'd be willing to bet that Google's strategy for this laptop is to do a smaller production run, and get these in the hands of tech/programmer types, and then use the lessons learned to develop a model targeted toward a wider audience.