Sunday, June 21, 2015

6 weeks with my Chromebook Pixel

I have some complaints and while I would like to elaborate in painful detail I just don't have it in me. My point of view starts with a few expectations and for the most part I get a lot of work done and the notion that I need a functioning replacement up and running with little or no effort is at the core. But it's the edge cases that I swore I was not going to let bother me.... and yet they do.
  • bluetooth support sucks
  • video player sucks (no mkv support)
  • cannot rename a USB or SD card.
  • only formats intro the default format (probably FAT; which means there is no support for my huge media??)
  • no containers like docker or rocket
  • channels is fine; devmode and crouton are a FAIL
  • cannot mount remote file systems
  • Google Play apps have some serious security flaws
  • I have not been able to find a way to work the touch screen into my workflow
I'm not going any deeper than this. I've had great success developing my code on this Pixel because I'm using a remote system.  I also have 7 Chrome devices in close proximity and I regularly switch between machines. I'm also developing an IDE that will work the way I want it to. And I have a reliable network.

I think I can do well with both or just the MacBook. Maybe even an iPad if they ever close the loop there too.

UPDATE: I'm starting to feel the pain of not being able to connect to my peers without all the usual software. If I had not paid $1200 for my Pixel-2 I'd likely set it aside except it's also my primary development console with it's awesome display (I have yet to use the touch).

UPDATE:  I just came back from 3 days at a client site. The only time I used my MacBook was to have a facetime with my family back home. For that matter I could have use my spare Chromebook and thus hangouts instead.

No comments:

Post a Comment

dead pixels

I have never had a dead pixel so when I read: Small numbers (1-3) of stuck or dead pixels are a characteristic of LCD screens. These are n...