You should be able to run Q3 and maybe even Q4 quants with 32GB. Even with the GPU as you can up the max RAM allocation with: 'sudo sysctl iogpu.wired_limit_mb=12345'

It figures that the thermal pads are applied by hand, when I replaced mine they weren't very well installed in the first place.

You'd like to think that a GPU like the 3090FE would go through QC that include some sort of stress test. It would only take seconds to see the VRAM temps would be well out of spec.

If they were out of spec you'd experience some form of thermal throttling. GDDR6X can handle very high temperatures, for example 120 degrees celcius is within spec I believe? Which is quite warm!

Unfortunately Web API 2 doesn't seem to work on it.

I get around $30 a month from a Hacker News app I made for iOS.

Unlikely to have a major upgrade until the Broadwell is out in mid-2015.

Lack of quad core is the only serious issue I have with the 13" now. Hopefully Broadwell will let Apple put a quad core into the 13".

The new Thunderbolt version which works like a native port at full gigabit speed.

The USB 3.0 ethernet adapters are also quite good if you're not running OS X (and thus don't have thunderbolt support).

Try this bookmarklet: https://github.com/joelcarranza/particular-pinboard

How is Apple magically supposed to know that you've switched phones?

I think the point is that it shouldn't try taking control of my SMS.

uhhhh.... iMessage is opt-in and isn't enabled until you actively sign up for it in settings. You don't want it taking over your SMS & MMS - don't opt-in to it.

They're not stored in plaintext, they're stored in the Keychain. The point here is Chrome provides essentially unauthenticated access to the Keychain.

For reference, here's what Safari prompts you with when you try to view your saved passwords: http://imgur.com/k2gIqtM

"Unauthenticated" except for the time you told Keychain to "Always allow" requests from Chrome.

However I'll admit that there's a big difference between what I expected Chrome to be using those passwords for (logging me into websites) and how it's ended up (making those visible to anyone looking at the settings page).

> "Unauthenticated" except for the time you told Keychain to "Always allow" requests from Chrome.

1. that does not make it OK to display all cleartext passwords, Keychain requires the account password before displaying the cleartext. And keychain can optionally require the master password to be entered before providing a password for form-filling as well.

2. an other user notes above that, whether you "allow" or "always allow", Chrome will copy the entry it just got to a new keychain entry which it sets to always allow.

Chrome creates it's own keychain entries and sets them as "always allow from chrome" regardless of what the user does.

This is a problem entirely caused by Google

Why can't Chrome do the same thing Safari does in that image? If the user wishes to see the password in plaintext, ask for their master keychain password first.