Visa Signature offers similar coverage, however making a claim with Visa vs Amex is a much bigger headache.
I've submitted multiple warranty and purchase protection claims with AMEX and its about the easiest process imaginable. Highly recommended.
They did so, at the cost of $10 per month. I paid $120 for them to print out about 40 sheets of paper and mail them to me snail mail.
I did the same with my Visa that I had at the same time, and they only charged me $2 per month. Still abhorrently expensive for paper transcripts imho, but 5x cheaper than AMEX on that respect.
I download all copies of my statements every year now though, that's for sure!
Extended Warranty can extend the terms of the original manufacturer's warranty on warranties of five years or less. We match the length of the original warranty if the original manufacturer’s warranty is less than one year, and we provide one additional year if the original manufacturer’s warranty is between one year and five years. Shipping and handling costs for the purchase will not be refunded. Certain purchases are not covered, e.g. items with physical damage, damage as a result of natural disaster, software, motorized devices and vehicles and their parts. Other important exclusions apply. You will only be covered up to the amount charged on your eligible Card; coverage is limited up to a maximum of USD $10,000 per occurrence; not to exceed USD $50,000 per Card Member account per calendar year. You may be required to send the purchased item to us, in which case we will reimburse you for shipping cost. This product is in excess of other warranty plans that you have in place for the eligible item.
I've got my DSLR and my MBP covered for $60/year—I got it mainly for the camera, in case I dropped it in a lake or something, but it was cheap to throw the laptop on it too and then that saved my ass when I spilled water in it.
What most people mix up is, that there are two different types of warranties. One that is given by the shop and the other one is given by the manufacturer.
The warranty given by the shop is required by law and is 2 years. It covers _only_ that the shop gave you a device without defects at the time you received it. After 6 month you as the customer has to prove, that a defect was there when you received the device, which is hard to prove.
The warranty by the manufacturer is a free given by the manufacturer. Apple give you a 1 year limited warranty. If something breaks during usage, than Apple will replace it within this 1 year.
That basically means, if something breaks between 1 year and 2 year, then you can't use the manufacturer warranty. You could try the by law required shop warranty. But then have luck in proving to the shop, that the defect was there when you bought it.
Also, insurance companies are not non-profits. They take a cut as well. The factory already makes a profit, but that's not going to increase simply because they have to lawfully offer two years of warranty. They'll have more costs but it probably wouldn't affect the profit margin as much as an insurance company would.
If they make a solid product a manufactures warranty shouldn't cost them anything.
http://www.which.co.uk/consumer-rights/regulation/sale-of-go...
The only exception of that rule are insurances which cover stuff I might accidentally do to other people.
Insurance companies know the odds better than us, they set the premiums, and they still manage to make a profit every year (billions of dollars in lots of cases)
It glaringly obvious that "on average" the average person should not get insurance when not required, because otherwise you're just paying for the profit of said insurance company.
For example, I kill cell phones regularly from dropping them; for me, insurance might be more cost effective; for the people who keep cell phones turned off except for emergencies it probably isn't good value. But, anecdotally I would say that these are the very people who have insurance. They are buying 'peace of mind', a very expensive product created by Madison Avenue.
I buy insurance if either:
1. I believe I'm significantly more likely to break the item then their estimates (ex: you use your phone at your construction job, and are significantly more likely to break it).
2. It's enough money that it would cause significant problems for me (home insurance, renters insurance, etc).
Otherwise, I figure I am 'self-insuring', and will come out ahead over the long term.
Not necessarily. Insurance companies on average lose money from policies and make it up by investing the float. Think of the money they lose on policies as the "interest" that you get paid for lending them your premiums.
Of course, I'm happy for Google to prove me wrong. I would have firmly thrown Photoshop into that category until Adobe announced they were making a ChromeOS-compatible version of it. I happen to quite like my Pixel, so if the Chrome Apps can one day let me do everything I need to do without needing to go to a Linux chroot, I'd be thrilled. Until then, however, I need Sublime (Caret is pretty good, though), I need git, etc.
I believe the Eclipse folks think that Orion (http://www.eclipse.org/orion/) is the path out of that jam. I'm super stoked about that project, and think it may have real legs if they don't lose focus.
That is their solution to your git need, also, unless one requires a dedicated git client to do rebases or other ninjary: https://github.com/creationix/js-git
I am 100% positive it will take some mental and maybe even logistical reorganization to switch to a cloud-based coding environment. Almost every change I can think of in a professional capacity is evaluated in a cost-benefit analysis.
But today I am home sick, and thus have no access to my properly configured PyCharm, nor access to the local feature branches on my machine and it would be a bunch of ssh hoop jumping to deploy anything that I did write while at home. My interests are pretty much in descending order of that list. I would love a copy of cloud-PyCharm.
So the idea, and if I recall correctly, proof of concept, of ChromeOS running Android apps isn't a large stretch.
edit: I just watched the promotional video, and I was right about their interest in ChromeOS running Android apps, I was just wrong about its maturity level. The video states that ChromeOS runs "select" Android apps.
The Pixel has:
Better processor (i7 2.6Ghz vs i5 2.7Ghz)
Slightly better resolution (2560×1700 vs 2560x1600)
Double the RAM (16GB vs 8GB)
The Macbook has:
Double the SSD storage (128 GB vs 64 GB)
Better integrated GPU (Iris Pro 6100 vs HD5500)
So I would say there is no clear-cut winner.
Regardless what people thinks, the base specs for the Pros are quite fair for the price.
EDIT: I was forgetting that the Pixel has a touchscreen display, somehting that Apple doesn't offer at all, at the moment.
Cpuboss gives the edge to the i7, but if you have some source with benchmarks comparing the two CPUs (or similar ones) I would be really interested in seeing them, in particular how TDP affects performance.
In my opinion the recently refreshed 13´Macbook Pro is one of the most interesting machines on the market, for the price.
Dell and Google have a better record on this front, and the XPS 13 and the new pixel are "solid gear".
I could see myself working on a Pixel fulltime.
That's not exactly a glowing endorsement, considering the price, why would you want to work on it full-time then?
For what it's worth, I've been using a Acer Chromebook for awhile now. It's been an excellent machine, when you consider I only paid $180 for it and threw Arch on it before its second boot. It can't hold a candle to the Pixel or an XPS, but I never expected it to.
ChromeOS is not for everyone but I wouldn't dismiss them outright as some people don't need much more than access to a shell environment and web browser to be productive. There are a few small frustrations, openvpn limitations etc. And they could do a bit more to make them friendly to devs/linux users.
Basically, Chromebook is a terminal + a browser for me.
For embedded programming, where I need to run a programmer to flash a microcontroller, I use an ARM board as a host.
It mostly comes down to what everyone here already knows: Chromebooks don't run all the apps many people need, like Photoshop:
> Personally speaking, I wouldn't buy one -- but that's mostly because it won't run Photoshop, and it doesn't play nice with certain peripherals like my running watch. Barring that, though, I love the Pixel. Between the design, display, keyboard and battery life, it's among the finest notebooks I've had the pleasure of using. I'm sad to have to give my review unit back.
- More RAM
- Better battery life / charge time
- USB-C ports
Here's what I'm not sure if it will fix: - Overheating (original Pixel gets HOT on the top-left corner where I'm guessing the CPU resides)
- OpenVPN support (ChromeOS does not support simply loading a .ovpn profile--I have to do some hacking from the command-line to get it to work)
- Longer warranty (1-year limited is all that is provided with the previous model--and since these are directly from Google, you can't get an extended warranty through the retailer)
- Weight (Love the metal slate look, could be lighter, however; based on the specs it seems like not so much)
And finally, the things that Google will never fix, and you should simply be aware of ChromeOS's limitations:
- Lack of apps
I will say, however, that in the past year, Crouton, which allows you to sideload a linux partition onto the device, has come a long way, to the point that you can actually have an Ubuntu chroot running in a tab inside ChromeOS as though it were just another window/app. It has proved incredibly useful for running things like Sublime or Eclipse without having to do the complete environment-shift that was required some time ago.
Price is still a little high, however. I feel like those looking for a high-quality Linux laptop could probably get an Acer Aspire for cheaper.