[deleted]
Introducing Pixel C
61–70 of 88 posts
Re: Introducing Pixel C
#62The rumors expected this to run ChromeOS because its codename is apparently Ryu. If that's true, there are still changes being pushed to the ChromeOS codebase regarding this device: https://chromium.googlesource.com/chromiumos/platform/ec/+/1... which tells me there's still more to know about this device. I'm curious what it is. Even though I'm typing this on my first generation Pixel, is there really enough of a dif…
I never understood why ChromeOS existed in the first place. To me, it would make much more sense if these devices ran Android. After all, there's no apps for ChromeOS -- other than glorified Chrome extensions, and it's not easy for developers to create ChromeOS apps (whereas if I could recycle my Android app, life would be good). Arc welder doesn't seem to work very well either. Analogously, Apple only has iOS. There…
Because it's the perfect Enterprise OS for companies, schools and other organizations that have moved to the web. Currently there's just no OS that would rival ease of deployment for large scale thin clients.
Android on the other hand has very limited provisioning tools and even iOS/OS X is orders of magnitude more expensive and harder to provision, keep updated and running.
Re: Introducing Pixel C
#63There seems to be an Ars Technica coverage of it http://arstechnica.com/gadgets/2015/09/google-pixel-c-hands-...
Re: Introducing Pixel C
#64Earlier quoted context omitted.
If only it had an ESC key (vim), and backtick (markdown) above the Tab key. I don't get it.. they had me for a second, but then that kind of ruins using it for anything "serious". I know, I know.. I'm probably not the target market...
It's missing: `~[]{}|\ I wouldn't be able to type some of my passwords or URLs on this thing. I thought the Chromebook keyboards were bad enough.
I think the presentation mentioned that the keyboard is extended by another row of keys on-screen. Not great, but that is how they intended to fix that.
Re: Introducing Pixel C
#65The rumors expected this to run ChromeOS because its codename is apparently Ryu. If that's true, there are still changes being pushed to the ChromeOS codebase regarding this device: https://chromium.googlesource.com/chromiumos/platform/ec/+/1... which tells me there's still more to know about this device. I'm curious what it is. Even though I'm typing this on my first generation Pixel, is there really enough of a dif…
I never understood why ChromeOS existed in the first place. To me, it would make much more sense if these devices ran Android. After all, there's no apps for ChromeOS -- other than glorified Chrome extensions, and it's not easy for developers to create ChromeOS apps (whereas if I could recycle my Android app, life would be good). Arc welder doesn't seem to work very well either. Analogously, Apple only has iOS. There…
> Analogously, Apple only has iOS. There's no SafariOS.
I'd say the Apple analogy would be iOS vs.MacOS. One could argue that the iPad Pro makes more sense if it ran MacOS.
Re: Introducing Pixel C
#66The only thing I took away from that page was the fact that they removed the pipe symbol. Basically rendering 20 years of linux programs garbage. (I guess we can remap it, but wtf).
The pipe symbol is like the windows-button of linux – except way more powerful.
Re: Introducing Pixel C
#67No function keys? C'mon, the keyboard 'looks' good, but lacks the keys you need for work.
Re: Introducing Pixel C
#68And there I was excited for a minute of a new C language variant focused on graphics...
me too!
Re: Introducing Pixel C
#69Earlier quoted context omitted.
You guys are misunderstanding the purpose of the page. It clearly says this is a SNEAK PEAK. It's like a teaser instead of a trailer. Obviously it will suck if you look at it as a product page, because it simply isn't one.
Exactly. The point of the page is to pique your interest, ideally to the point where you decide to sign up for email updates. In many ways, giving more concrete information works against that goal, so the page doesn't do that.
But we don't want that, hence the complaints. Sign up for a newsletter just to get the technical specs for a random tablet? Come on. Marketers needs to stop taking drugs.
Re: Introducing Pixel C
#70Earlier quoted context omitted.
I never understood why ChromeOS existed in the first place. To me, it would make much more sense if these devices ran Android. After all, there's no apps for ChromeOS -- other than glorified Chrome extensions, and it's not easy for developers to create ChromeOS apps (whereas if I could recycle my Android app, life would be good). Arc welder doesn't seem to work very well either. Analogously, Apple only has iOS. There…
Because it's the perfect Enterprise OS for companies, schools and other organizations that have moved to the web. Currently there's just no OS that would rival ease of deployment for large scale thin clients. Android on the other hand has very limited provisioning tools and even iOS/OS X is orders of magnitude more expensive and harder to provision, keep updated and running.
> Android on the other hand has very limited provisioning tools
But Google could have improved Android provisioning instead of pushing another OS.
(Which would probably be sensible either way. There's billions of Android devices in enterprise environments that'd benefit from it.)