This was a very interesting piece from the review, taken from the software section. For those of you concerned about the lack of RAM and how Safari is handled on an iPhone 6.
The other issue has the potential to be far more serious. While iOS' software architecture is more RAM efficient due to manual garbage collection and the use of precompiled binaries, it's quite easy for me to push the phone past the breaking point in Safari. For example, six tabs of common websites for mobile devices cannot consistently be held in memory. If I continuously go through all six tabs, at least one will need to reload. In my first attempt at running this test, Safari crashed as I tried to go through all tabs constantly to keep them in memory. I didn't notice this behavior in the new Moto X, which can do the same test without issue. Outside of memory intensive use cases though, the iPhone 6 does respectably and I usually don't notice the lack of RAM. I have to emphasize that this should be a generally unlikely problem, and that the same behavior can be replicated on the iPhone 5s given the same workload. If you did not have issues with out of memory crashes before, there won't be any issues now.
Yes, he mentions it, I guess for comprehensiveness sake, but then completely glosses over the negative effects of paltry 1GB RAM on performance and user experience. Safari performance is a joke and I say that as an Apple enthusiast. Chrome is what I have switched to on iPad Air and 6 Plus and it is better but reloading and crashing issues still exist due to inadequate level of RAM. Makes you wonder if they're all fishing for Apple jobs like the one Anand bailed for.