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

Googlebook

googlebook.google

Post reply on HN
Print view View original

311–320 of 1001 posts

Re: Googlebook

#311

Post by wffurr »

whodidntante wrote: post #59
jerojero wrote: post #14

I think if I wanted a cheap laptop I'd probably get the macbook neo, and if i wanted a non-gaming expensive one i'd get a macbook pro. I really don't see the market fit for this, I guess the android integration. But my god, I'd die of cringe if someone asked me about my laptop and I had to say "googlebook". Believe it or not, these things matter a lot, particularly if you're trying to target a young audience.

Chromebook users. I loved my Pixelbook, fantastic piece of hardware. When that ended, I went with an Acer Chromebook. Works fine, just not the same. I would go for a Mac Air or Neo, but only if I could install ChromeOS. I will most likely get a Googlebook, and would be more likely to do so if it was not named Googlebook and did not have Gemini built in.

The HP Dragonfly Chromebook is pretty good. The Asus models are also very nice. The Acers are hit or miss; quality is iffy on those and there's a zillion models so it's impossible to find a specific one.

I wish Framework would keep supporting ChromeOS but alas. You could put ChromeOS Flex on one - it doesn't have Android apps, which is fine for me, and it does support the Linux environment, which is excellent.

Re: Googlebook

#313

Post by jeroenhd »

deckar01 wrote: post #128
achow wrote: post #27

Google seems to have made an official post on Reddit describing the feature set in detail: https://www.reddit.com/r/Android/comments/1tb8xls/introducin... [Edit] And, the feature set references the 'AI mouse pointer' from this Deepmind blog.. https://deepmind.google/blog/ai-pointer/

Wiggling the mouse is what people do involuntarily when the computer isn’t working right. They are setting themselves up for Gemini to be the uninvited Clippy, except this will send everything you are working on to Google to harvest data from.

The video they show (which is probably exaggerated by cutting out LLM generation time) is pretty sci-fi. I don't know how it works in practice, but it looks fun to try out. If this could run locally, I'd love to have a feature like that.

Most people don't really seem to care about data collection when it comes to AI usage. A lot of people who will feed Gemini/ChatGPT/Bing/Claude/shady clusters across the internet for bargain bin prices/Mistral every detail of their lives will probably be fine with Gemini as long as it doesn't interfere unnecessarily.

Re: Googlebook

#314

Post by dmonitor »

deckar01 wrote: post #128
achow wrote: post #27

Google seems to have made an official post on Reddit describing the feature set in detail: https://www.reddit.com/r/Android/comments/1tb8xls/introducin... [Edit] And, the feature set references the 'AI mouse pointer' from this Deepmind blog.. https://deepmind.google/blog/ai-pointer/

Wiggling the mouse is what people do involuntarily when the computer isn’t working right. They are setting themselves up for Gemini to be the uninvited Clippy, except this will send everything you are working on to Google to harvest data from.

It's the unofficial "where's my mouse pointer" macro

At least one DE I've used (MacOS? KDE?) even had it as an official macro that would make the pointer 10x bigger when you shook it

Re: Googlebook

#315

Post by medhir »

It’s amazing to scroll through this whole product page and leave feeling like I don’t know what it really does / who it’s for.

Why are these features compelling? I went through the whole page and still don’t know what OS runs on this laptop… the value prop for this is incredibly unclear.

Re: Googlebook

#316

Post by treexs »

jeroenhd wrote: post #291
spiralcoaster wrote: post #280

What's funny is that these days if I see a Google product that I'm even remotely interested in, I just immediately write it off because I know it's something they will kill in a very short time frame. It's just never worth the hassle of buying/using a Google product. Never.

Their hardware is usually fine when it comes to support. Google announces the support lifetime of their devices and sticks to it, with feature updates coming to things like phones even after the support period ended through things like app stores. Just check the support lifetime of the device before buying (early Pixels only had 2 years of support, as was announced at release). Their cloud services are nothing but ho…

I thought Apple does tell you how long they'll support hardware.

For example: https://support.apple.com/en-us/102772

Re: Googlebook

#317

Post by esseph »

spiralcoaster wrote: post #280

What's funny is that these days if I see a Google product that I'm even remotely interested in, I just immediately write it off because I know it's something they will kill in a very short time frame. It's just never worth the hassle of buying/using a Google product. Never.

I've had great luck with their hardware (phones / tablets) and they get updates frequently and for quite a long time.

Re: Googlebook

#319

Post by jadbox »

spiralcoaster wrote: post #280

What's funny is that these days if I see a Google product that I'm even remotely interested in, I just immediately write it off because I know it's something they will kill in a very short time frame. It's just never worth the hassle of buying/using a Google product. Never.

I argue this is both true and not true in stark ways with Google. Just look at Google Groups listserv, it's been running forever and arguably mosts used neighborhood listservs globally and has been very stable.. all largely for free. On the other hand, new experiments get chopped very quickly at Google. So, it's more like if the service can survive 2 years, then Google generally keeps it around*.

* unless it gets merged dozens of times into other similar projects.

Post reply on HN