Quote:
Originally Posted by tubemonkey
My Acer isn't on that list either. That means when my Chromebook gives up the ghost, I'm switching back to Windows. I'm getting very tired of the "file type not supported" messages.
|
Yeah, I guess us C7-series early adopters don't get in on the fun.
I hope my Chromebooks don't give out soon, because I'm pretty happy with that they do, and don't want to spend real money to replace them (I just manually repaired the fan in one of ours.)
Of our three chromebooks:
#1 has a re-flashed bios and a native linux install, so is technically no longer a Chromebook.
#2 is almost never used, except once a month it's plugged into my TV to show chords and lyrics at my guitar jams. It's in dev mode with Crouton for occasional use.
#3 is a purely stock Chromebook here on my desk at work for personal stuff, like email and this post.
That article says the Android apps on the Chromebooks will be "fully native, not emulated." I wonder if that statement has any significance, considering that "native" Android itself is bytecode translated, JIT compiled (no?), based on a framework, in a JavaVM, atop an OS. Really, what harm could "emulation" do? It might even help in some implementations....