Supposedly the RAM is soldered onto the motherboard. I've heard mix-messages, but the Apple person on CHAT confirmed it. However he could be wrong too.

I guess we'll find out soon.

If it is soldered, that is a sad day indeed.

There is a meager i7 option when "Built to order"

BUT!!!! No Quad Core i7. Still just a dual core.

That, combined with the soldered RAM has a bunch of people upset.

Sorry, my "Follow the thread" statement wasn't meant to sound like a jerk. Meant to say something nicer but clicked "Post" before I thought of something

Follow the thread.

This was about the 27" Retina iMac they are releasing. My concern is their Revision A products tend to have issues.

When they redesigned the 27" screen on the iMac last time, it had a number of issues. Likewise they changed something around with the Retinas on their laptops and they ran into a number of issues.

Ghosting, splotchy screens, bad glue-jobs, etc.

Meanwhile they've been doing Retina for a while and 27" for a while and just recently had problems changing both. Combining the two is probably going to have issues as well.

Because this is their first REALLY BIG Retina display? Apple's first attempt at something unique often has issues, hence the mantra of "avoid any Revision A Apple product."

Recall the various screen issues and defects they had 1-2 years ago with smaller Retina displays? Recall a bunch of issues they had with the 27" iMac (non-Retina) redesigned screen? Things looking blotchy, bad glue jobs, etc. Apple had done retina a bunch before those issues, and 27" Macs a lot too. But a large enough redesign and all of a sudden they realize "oops, there's a manufacturing issue"

Apple isn't any worse than any other company, and I tend to think they're slightly better than most. But first generation products, while trying something new, tend to have some quirks to roll out.

I've been thinking about giving the OSX another try... I've been messing around with it at work.

The mini wouldn't be a bad way to go... it's not that expensive and I can still use my 27" monitor.

The iMac Retina... no. Besides not wanting to spend that much now, I'd hold off on a first generation rig like that.

Thanks. Yeh, it seemed like the perfect phone. Decent build quality, nice size, great price... I was thrilled.

Until I had to make calls :-(

And when the replacement had it too :-(

It was a shame. But enough to turn me off of Nexus for a version or so.

Yup, replaced it and got another defective unit. This was around March or April. The person on Google Play's support line knew what I was talking about when I called about it too.

It was a common / known issue, and others had bad replacements as well. A Google search will show it.

Perhaps a bad batch, or a bad software update was pushed or something.

So I did a full return / refund on the second unit.

I could tolerate a common-crash or some Internet based issue that might "eventually" get fixed in a patch. Heck maybe the Mic issue was eventually fixed, but a Google search shows people still complaining about it in June.

But being unable to use my phone as an actual PHONE made it a no-brainer... I had to move on.

Did that, got another bad one. Didn't matter who used it or tried it. Same thing. Even brought it to a couple AT&T dealers to see if they could figure it out... none of us were blocking the mic with our fingers or anything.

Others on the support forums had similar "replaced with yet another bad one" situations.

It was a known problem... perhaps with a batch? If you Google Nexus 5 microphone bug you'll find a lot of hits from around the same time.

I would have been OK with the occasional crash or some other unstable bug that would eventually be fixed by software. But being unable to use it as an actual PHONE until it was fixed was not an option.

Funny.

Obviously the rumor is LG isn't making it. That wasn't my issue. My last sentence summed it up

If Google wants to promote their Nexus line as THE official TEMPLATE for their phones... and misses such a HUGE design flaw that impacts the core aspect of the device (being a phone) then I'm not going to trust future Nexus versions for a while either. Because either they didn't care enough to notice it, or didn't care enough to do something drastic to delay the release or AT THE LEAST put out a press release. I'll go with something else instead (HTC, Samsung Galaxy, etc.)

Apple was kind of in the same boat with the whole "You're holding it wrong" situation. That was a big bug that impacts day-to-day use of the core aspect of the phone. They missed it, presumably because they tried to test the phones with camoflauged cases.

Though I find the Nexus 5 MICROPHONE issue worse than hand-gate (and bend-gate) because the mic issue completely prevents me from using the phone as a phone. While Hand-Gate was just a signal reduction issue resolved with a bumper, and bend-gate doesn't affect me. And I still skipped iPhone for a generation.

I decided to give the Nexus 5 Google Play Edition a chance. It was a (relatively) decent price, decent kit, and a nice screen. It didn't have as many features as the latest Galaxy but it was still quite good. And I was digging the latest Android screenshots so I got it shortly after release.

It had a major Microphone bug.

It didn't matter where I held it, but the mic would sometimes die out and nobody could hear me. At all. I eventually left myself a voicemail at work and could BARELY hear myself.

I wasn't the only one with the issue.

So... was NOT a fan LG after that. And I don't know how much faith I'm willing to put in a Nexus phone if it released with that big of a bug.

I understand that.

But I don't know how they setup this "fix"

Did they just put local mirrors of NetFlix content in their server farm? And have stream2775.netflix.com point to a local node instead of the "real" stream2775.netflix.com out on the Internet?

In which case, Google DNS would point to the real one on the Internet while the FIOS one points to the local node inside their server-room.

I should clarify... by "acting up" I mean regular webpage browsing... not Netflix.

It was acting funny -- slow speeds, page not found's, etc.

So I switched it. As mentioned it was probably a short-term issue for a few hours or a day or something and I just happened to catch it at the beginning. But I didn't bother switching back.

Obviously the answer is: switch back. But my concern is if it becomes an ongoing issue... will I have to choose between Netflix and the rest of the web.

Long-time FIOS user.

Would using Google's DNS or Open DNS negate any benefits from however they set things up now post-deal?

I toggle Google DNS because a couple months back, for whatever reason, my FIOS was acting up and I tracked it down to that. Used FIOS DNS and it was cruddy, switched to Google DNS and it was fine, back to FIOS it was cruddy... so I left it as Google DNS. It might have been a short-term problem for a day or so but I haven't bothered switching back.

The thing is, someone was saying that now... FIOS's DNS might redirect me to the good/fast route or internal server setup for Netflix while Google DNS (or Open DNS) might take the "unoptimized route"

Anyone know for sure?

I either NEVER had a sense of smell, or at least not since I was 5 years old. So I should have died over 25 years ago.

It is a minor inconvenience... I have to be careful about gas leaks and such.

As for food, I have a good enough sense of taste to distinguish most foods so it's not like I feel like I'm eating sawdust like some people assume.

A for the rest, just minor stuff:
Visually check to make sure I didn't step in dog poo
Don't use any fragrance or cologne... I'll never get it right
Make sure I'm always clean, and have deoderant on
etc