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

211–220 of 1001 posts

Re: Googlebook

#211

Post by IshKebab »

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/

> It's really easy to access your phone’s files right from your Googlebook's file browser.

Yeah but what about Windows Explorer? They've been passively blocking SMB access forever at this point (by disallowing ports below 1024).

I would not be surprised if Googlebook's file browser goes via the cloud.

Re: Googlebook

#212

Post by drcongo »

ActorNightly wrote: post #154
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.

>I really don't see the market fit for this, Why pay $500-700 for Mac Book Neo for the same low processing power experience that you can get on a Googlebook for half the price? Especially considering you can install linux on it natively. Other then that, Gemini is the biggest advantage. Google can offer Gemini for free because its TPUs are orders of magnitude more efficient than Nvidia stuff. Even free tier Gemini is…

These things are $250?! Where did you find that info?

Re: Googlebook

#213

Post by cj »

hypersoar wrote: post #151

I attended Google I/O in 2013 and was given a Chromebook Pixel, their $1300 laptop. The hardware was very, very nice, and I quite enjoyed using it for a while. One day, I dropped it and damaged the screen well outside of its warranty period. "Oh no," I thought. "This is probably going to be pretty expensive to fix." So, bracing for the damage, I called up Google and told them what had happened. They replied that ther…

I really miss the Chromebook Pixel / Pixelbook / whatever it was called.

It was my travel laptop for at least 5 years.

It was expensive, but the quality, performance, and durability was top tier. And it lasted 5+ years.

The Pixelbook also had a "Google Assistant" button built in the keyboard. Should be easy enough to relaunch the hardware and swap in a gemini button...

Re: Googlebook

#214

Post by tadfisher »

abirch wrote: post #209
hypersoar wrote: post #151

I attended Google I/O in 2013 and was given a Chromebook Pixel, their $1300 laptop. The hardware was very, very nice, and I quite enjoyed using it for a while. One day, I dropped it and damaged the screen well outside of its warranty period. "Oh no," I thought. "This is probably going to be pretty expensive to fix." So, bracing for the damage, I called up Google and told them what had happened. They replied that ther…

I used to have everything Google. Strata Pixels, Nest Cameras Google Smart Speakers Nest Home Security system but then I broke my Google Pixel 1 watch. I ended up chatting with service in India and they pretty much told me that there was no way to fix it. After that, I quit buying all things Google and switched to Apple. Now I only buy Google software products, no consumer devices.

They completely changed their watch design for the Pixel Watch 4 so that it is actually repairable: https://www.ifixit.com/News/113620/the-pixel-watch-4-is-the-...

Re: Googlebook

#215

Post by BadBadJellyBean »

Wow. That has to be one of the worst announcements I have ever seen. A hardware launch that only talks about software and most of the software is AI. This announcement is nothing. This could have been a ChromeOS update.

Re: Googlebook

#216

Post by Topfi »

ac29 wrote: post #176
Topfi wrote: post #121

I have a hard time seeing how any Chromebook above $ 349,- could still survive in an post-MacBook Neo age. Say what you want, a cheap Windows laptop at least has an edge on obscure software compatibility over MacOS and a notebook running any modern Linux distro gets the luxury of user control. ChromeOS meanwhile has neither. Paying more for worst in class software compatibility inferior build quality, design and rest…

> ChromeOS meanwhile has the worst compatibility off all four ChromeOS can run desktop Linux software and Android software, so it definitely isnt worse than Mac. Its probably even better than Windows. Of course, if you need Mac/Windows software, Web/Android/Linux alternatives might not exist or might be worse. But the devices are hardly lacking software compatibility.

No, ChromeOS cannot. You can only run Linux applications via Crostini. Heavily sandboxed and restricted to limited hardware access, that is not software compatible by any reasonable measure. If that counts, my MacBook is compatible with all software ever made via UTM. Also, lest we forget ISA. If these Googlebooks are arm64, that restricts software compatibility further still as Crostini doesn't translate between arm64 and x86_64, so we are going from poor, limited support, to worse.

For reference:

> Cameras aren't yet supported.

> Android devices are supported over USB, but other devices aren't yet supported.

> Android Emulators aren't yet supported.

> Hardware acceleration isn't yet supported, including GPU and video decode.

> ChromeVox is supported for the default Terminal app, but not yet for other Linux apps.

Source: https://support.google.com/chromebook/answer/9145439?hl=en

Re: Googlebook

#219

Post by xp84 »

efskap wrote: post #185
hypersoar wrote: post #151

I attended Google I/O in 2013 and was given a Chromebook Pixel, their $1300 laptop. The hardware was very, very nice, and I quite enjoyed using it for a while. One day, I dropped it and damaged the screen well outside of its warranty period. "Oh no," I thought. "This is probably going to be pretty expensive to fix." So, bracing for the damage, I called up Google and told them what had happened. They replied that ther…

Looks and feels premium, but ultimately fundamentally disposable. This pattern extends to so many goods in modern life. Washing machines, microwaves, etc aren't worth the time of a local repairman. Repair is economically incompatible with its life cycle. Clothes are replaced, not stitched. And after a few washes at that. Cars, phones, etc, consist of proprietary parts all sealed up.

> Looks and feels premium, but ultimately fundamentally disposable.

I'd add that experiences like GP help expose that the main difference in most products between 'premium' and 'disposable' is in the branding and the price tag. With few exceptions, most companies that used to make the respected brand of the thing (e.g. Sony, G.E., Craftsman) now churn out the same garbage as you used to find 30 years ago in a fleamarket with a brand you'd never heard of - and that's if they don't actually outsource the design and/or production to that low-bidder company and simply license their logo directly to them.

And that's because these are all public or PE-owned companies, and it's a shortcut to easy short-term quarterly growth if you can cut your costs while keeping your price high or almost as high (after all, you're a "Premium Brand" so you can leverage your past reputation to trick customers into continuing to pay that premium).

Re: Googlebook

#220

Post by StilesCrisis »

bsimpson wrote: post #203
hypersoar wrote: post #151

I attended Google I/O in 2013 and was given a Chromebook Pixel, their $1300 laptop. The hardware was very, very nice, and I quite enjoyed using it for a while. One day, I dropped it and damaged the screen well outside of its warranty period. "Oh no," I thought. "This is probably going to be pretty expensive to fix." So, bracing for the damage, I called up Google and told them what had happened. They replied that ther…

Tying the browser version to the system version was a mistake too. Once it stopped getting system updates, it stopped being compatible with big corners of the web that expect Chrome to always be the newest version.

They had a fix for that in development! Sadly but not surprisingly, it was cancelled:

https://9to5google.com/2024/07/12/chromeos-lacros-ending/

Post reply on HN