Google’s PixelBook: the target is bigger than it seems
chromeunboxed.com
chromeunboxed.com
From what I've read on other threads about high end Chromebook Pixel's, getting them repaired if there is a manufacturers defect, or worse yet it gets damaged is very inconvenient and costly. Comparatively, replacing a smashed screen in a T440 is a $50, sub-5 minute affair, and Dell & HP's enterprise laptops seem just as repairable (albeit parts are 40% to 50% more).
They buy it because Dell and Lenovo replace/repair a device in 24 hours.
Laptops purchased through enterprise sales were not affected by this.
For me, If they have the best product available when I'm ready for a new laptop, and I know how to buy it such that I won't be getting any bloatware/spyware/etc., then I'll still buy from them because the quality of their hardware has been consistent for me.
Because I doubt BigCorp with thousand deployments of ThinkPads with Windows images would suddenly go MacBook Pro.
I wish Microsoft would get serious about hardware. I trust them more than any of their partners.
Their ideapads on the other hand...
That is really a problem across the board though, people conflate the brand with the cheapest product line out of the nearby brick and mortar.
For example i have read all kinds of doom and gloom about Acer quality control. Yet i have seen their business line survive far beyond what people claimed.
In fact, do you even care that you get back the same machine?
Actually given how strict many companies are about NDAs and controlling their internal network, it surprises me how some put their golden eggs on Google's basket.
Think of it as a security-analog to infrastructure as a service: why build best in breed, when you can buy cloud resources that already have security integrated (and maintained!)?
Even at a large org, keeping internal infrastructure secure and updated is non-trivial.
I work at a Big Corp Inc. This is unfortunately not the case here. The person you replied to is correct in how our security team sees things.
Not sure how much to attribute to C-level staff turnover.
One of the major factors seems to be standardization. Once security has blessed a cloud provider, they're blessing the infrastructure and features, so the blessing holds for most projects that might want to use it. In contrast to getting approval for a semi-custom config on-prem.
Caveat: I'm not working with privileged data (gov or healthcare) anymore, so those considerations aren't influencing the behavior. Imagine HIPAA shops would be a lot more conservative.
This.
I worked in the Dell Call Center in Bangalore, India around 2005. Customer support was treated as the most important function in the entire company. I remember they would make us agents skip meals if the call volumes got high. Managers would walk to the cafeteria can carry us meals/sandwiches to our desks. Breaks were highly partitioned throughout the day. It was 2 fifteen minute breaks, which you could take anytime. And then a 30-45 minute meal break. Every single thing in the building looked like revolved around one single thing- 'customer satisfaction'.
The metrics for performance were designed around these quality parameters. resolve rate(solutions/calls), mean time to resolve(span of solution calls/no of calls)... things like that. There used to even y-jack(eavesdrop) on our calls randomly for evaluation. There were also strict penalties for goofing up, upto things like getting fired if you make them more than 3 times.
I could go on..
The point being these people are good at customer service because they take that business very seriously. As techies we may laugh at that, but that is whole different league of business with cut throat performance requirements.
The users however do not want to drag around stationary computers for some reason so we mostly have laptops of different brands, even some mac's since salespeople refuse to use anything else... :-)
Google's offerings are as much software as hardware, and having Google drop your account over a misunderstanding and thereby disabling all your laptops for several weeks would be a nightmare. Many of the people in charge of making purchasing decisions will have this type of concern in mind.
Whether they can turn that around and make a strong enterprise support channel is a valid question. But it's going to take some strong sales and tech to get people to risk trying it out. Google's a great company as long as you don't have to actually talk to anyone. Which makes them wholly undesirable for companies that obsess over the number of nines in their reliability.
My experience is not the same for all the products I bought for Google.
It was really easy to contact support and replacement devices came quickly.
So far, so simple.
It's been 4 months of calls, emails, faxes, and sending the device back and forth between Google, LG, the insurance, and the repair facility.
Google says they're not responsible for Nexus devices, so we should talk to LG. LG says they're not responsible, we should talk to Google. We got someone at LG to discuss this, and they told us to send it to their official repair facility. They just sent it back because of a typo on the form, or because the insurance didn't say fast enough that they'd fund it, or because "dunno".
We've now taken the device to Media Markt to get it repaired, and it took 2 days.
Never ever are we going to buy a device from Google again.
(disclosure I work at google but this was before I started)
This is now the second time we’ve had this odyssey with Google (the Nexus 7 2012 being the first case), and by now it’s obvious it’s not a problem with the OEM, but Google.
It's just an anecdote, so weigh it appropriately. I've absolutely no idea if they have improved.
This I think will be the biggest challenge. I've never heard of Microsoft disabling software or cancelling support if by some stroke you were audited and failed. The matter is handled outside of normal business operation.
I understand that this isn't the experience that folk have with every Google product, but I suspect that any enterprise support would hook into their GCP support platform.
Concerns about "turning off your account" are certainly valid, though you that's something that Amazon or any other SaaS vendor could do with (I've seen a few nightmare reports over the years, though they seem to be the exception not the rule).
> There's also Google's terrible reputation of poor and unreachable support, as well as the unappealable terminations of service... some companies have had service terminated leaving them with no recourse. Google's offerings are as much software as hardware, and having Google drop your account...
That's directly referring to cloud services/software support, not hardware support; I'm not making any claim about the latter.
As others mentioned, if the company is accepting that everything goes to cloud (which I guess is the pre-requisite for even considering Google device) then you don't need to worry so much about broken hardware, as you can just provision a new device for user and RMA the old one. Vendors could go even further and provide this spare device free, only charging money for devices which are in use.
Hell, i can't shake the suspicion that Android on anything but phones were left to languish for years because of this. Because just as ChromeOS and Chromebooks were unveiled, Android was being readied to go beyond phones with Android 3.0.
This included support for new input devices, and even a generation of tablets that had full size USB ports for various uses.
Only recently have we seen Google return to this via two prongs. First is Android for Work, the second is combined development of windowing Android apps and Android apps on ChromeOS.
I know that Apple Macbooks are as popular as ever but there has been some grumbling that RAM is limited, the touchbar has caused a split in opinions, and there has been suggestions that Apple is trailing Intel's top of the line chip launches, and finally that Mac OS X is not getting the love that iOS is getting.
Put that all together and maybe Google has a small window of opportunity to surprise the dev community and bring out a kick-ass Linux laptop workstation to offer true competition to Apple on their home turf. That would be pretty exciting, all the more so if they got within sniffing distance. Since the demise of SUN Solaris and SGI Irix workstations and the like Apple has had this segment (brawny Unix workstations) pretty much all to themselves in a way.
Dream machine: Great Intel hardware, RAM up to 64G, decent graphics card, flawless 2D/3D drivers (minimum brawn needed for ML work), ChromeOS w/ dev tools a couple of command line scribbles away, software repo as large as Debian/Unubtu/Arch/Gentoo, ability to run Android apps, Secureboot and non-reboot kernel/driver updates, ability to install my won boot key if I so wish, fingerprint reader –– hey I did say dream machine!
I had a 2013 Chromebook Pixel that started to have a vertical line of dead pixels running down the screen. It should have been a simple fix. But first, Google didn't want to repair the thing because it was barely out of its one-year warranty (which you can't even pay to extend, by the way). Then, when they finally relented and agreed to take it, they sent me a new one, rather than fixing the other one. There have been minor problems with it since then, but I don't dare try to get them addressed, given that the laptop is way out of warranty and no longer manufactured.
My next laptop after the Pixel was a Dell XPS 13. And that was in no small part because I knew that Dell could provide hardware support if something broke. I even paid additional support to extend my warranty through 2019, because it's mission critical that this thing work.
Google needs to understand that there's no way any reasonable person can be expected to spend $1200+ on a laptop that can become a paperweight because it suffers a hardware failure and the manufacturer refuses to touch it. The "rumor" is that the original Pixel was created because Google themselves was having trouble getting support from Apple for their employee Macbooks, which makes the lack of Pixel support even more mind-boggling.
This still fits the "device for google internal use that they also sell outside" model since the Pixel 2013, with perhaps increasing emphasis on selling outside.
Making ChromeOS a stable, durable hypervisor that also hosts other OSes (better linux support than Crouton, and possibly adding windows support) just makes it an ever-more viable replacement for those-other-companies' high-end laptops.
Is there any benefit of a VM-friendly ChromeOS retaining Chrome as root-level functionality? Why not move the Chrome-browser-UI into a client VM as well, parallel to Linux and Windows clients?
Taking this a step further would not surprise me the least.
I had to once wait over an update, because it broke the system. It had symptoms of GPU driver issue.
Generally I'm quite pleased with the machine, but I wouldn't buy another ARM Chromebook. Rockchip SoCs have drivers mostly open source from what I understand, but GPU driver is not OS. Intel is safer bet. I really like the idea of AMD Chromebook, but you can't have everything.
[1] https://productforums.google.com/forum/#!msg/chromebook-cent...
After all, Google is a SaaS and developing a SaaS requires back-end services. I run a SaaS and on the dev side, we've dockerized the database, cache, and other services. Google's plan may be to provide local versions of their cloud services for development on the PC.
The PC is powerful enough to run all of this. 512GB of storage and (hopefully) a powerful processor would explain this.
Since ChromeOS is basically a browser based OS with high dependency on web applications,....
I happen to know what PIDE/DGS stands for.
Every person even those that you think are your best friends, are a possible spy.
I guess my attitude isn't great for your business, is it? Oh well.
> How do you do this?
Settings → SyncUntil you can run Sublime Text, and bash (with perl, python, sed, awk, etc, or any other arbitrary piece of software I don't see developers moving to this device.
There I tried to do my best with XEmacs, DDD (or similar) and some GUI builder.
Thankfully eventually IDEs started to be a thing on GNU/Linux as well, starting with KDevelop and Anjunta.
We have customers where it is considered breaking security if one somehow gets it installed.
1. Standardization - if you use one web browser and know that your apps all work and display properly on that browser, you have one less call driver to support. This seems silly, but when Bob from accounting calls to complain about not being able to access his app and you find he's using Chrome which isn't supported, that's time wasted ("But Jim in Sales told me to use this!")
2. Security is a concern. Honestly, Chrome is at least as secure as the other browsers, and possibly more secure. Nevertheless, more browsers means you have a larger attack surface to worry about. Related to this, some industries have to prove compliance, and that may mean testing each application that gets installed to verify that they are complaint with various regulations. Testing each browser is extra expense that doesn't really add anything to the company's bottom line.
The most reliable way to prevent Chrome installs is to have AV treat it like a virus.
Likely because of this fear that Google might be using corporate data (even if it was not done for corporate emails, aka Google Apps / GSuite, even before this policy).
[0] https://www.theverge.com/2017/6/23/15862492/google-gmail-adv...
The real reason most companies are hesitant to use Google for work email is that they don't know where their data is getting stored.
no pun intended? :)
Using cloud resources or ssh'ng to other boxes just about make sense which you can do with any laptop. But any heavy apps or workloads will have your fans spinning up, throttling and heat and generally reduce the life of a pretty expensive product.
Then to get a secure Chrome OS and the cherry on top is Android support.