Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Pixel C

pixel.google.com

Post reply on HN
Print view View original

51–60 of 88 posts

Re: Introducing Pixel C

#51

Post by morpher »

nfoz wrote: post #47
davvid wrote: post #37

Earlier 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.

In the nexus presentation, they mentioned that a few symbol keys were moved up to soft keys to fit the keyboard while keeping a laptop-like distance between keys. So, it might not be super convenient, but you can likely still type your passwords.

Re: Introducing Pixel C

#52

Post by Hydraulix989 »

bsimpson wrote: post #6

The 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's no SafariOS.

Re: Introducing Pixel C

#55

Post by andybak »

nfoz wrote: post #47
davvid wrote: post #37

Earlier 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've switched to longer passwords but all lower-case - mainly to ease the pain of entering them on a phone.

On a proper keyboard it takes the same amount of time to type, it's easier on my brain and you can achieve the same entropy with just a few more characters.

(And then some f%£$ing website will tell me my 16 character password is insecure because it's all lower case.)

Re: Introducing Pixel C

#56

Post by ISL »

nfoz wrote: post #47
davvid wrote: post #37

Earlier 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.

It looks like there's a new meta key "..." immediately to the left of the directional arrows. Perhaps there's a chording mechanism to bring back the symbols?

I've been surprised how well I've been able to adapt to the Chromebook keyboard; my daily-driver notebook is a Chromebook with crouton. I think I miss having delete the most. The loss of the windows key as a user-defineable meta key was offset by the fact that I never use caps-lock for anything...

Re: Introducing Pixel C

#57

Post by aceperry »

zmmmmm wrote: post #23
bergie wrote: post #16

Earlier quoted context omitted.

Devtools and Crouton would make this a pretty interesting device

Key problem is it's ARM and not Intel processor. How much of a real developer experience a crouton style solution enables on ARM, I'm not sure. But I'm guessing it's a lot more limited.

How do you know that it runs ARM?

Re: Introducing Pixel C

#58

Post by nfoz »

ISL wrote: post #56
nfoz wrote: post #47

Earlier quoted context omitted.

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.

It looks like there's a new meta key "..." immediately to the left of the directional arrows. Perhaps there's a chording mechanism to bring back the symbols? I've been surprised how well I've been able to adapt to the Chromebook keyboard; my daily-driver notebook is a Chromebook with crouton. I think I miss having delete the most. The loss of the windows key as a user-defineable meta key was offset by the fact that I…

Fair enough, but the keyboard is why I regret my Chromebook which I also use daily. I thought it would not be a big deal (and I did manage to remap Power to Del -- just don't hold it too long!). But missing F11/F12, home/end/pgup/pgdn, meta, insert, etc. annoys me constantly.

Re: Introducing Pixel C

#59

Post by aceperry »

nfoz wrote: post #47
davvid wrote: post #37

Earlier 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.

Interesting, what other characters are in your password?

Re: Introducing Pixel C

#60

Post by nekkoru »

wingerlang wrote: post #45
fernly wrote: post #36

Earlier quoted context omitted.

Right. Could you POSSIBLY design a less-helpful, less-informative page?Maybe one with even more annoying keyhole-cropped images? Maybe! But you could not possibly under-improve on the random little rainbow bug bottom right that does nothing and says nothing.

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.

Sneak peek.

http://theoatmeal.com/comics/sneak_peek

Post reply on HN