Yes. The same thing I've said before. It's great that an independent app developer has his opinion. If I had to weigh his skill and credibility against Apple's, you know, the guys that actually designed and built the iPad, I wouldn't be so quick to declare that post the definitive answer. It's interesting, but hardly conclusive.
The iPad platform is well known, stable and documented, and app developers need to work within the constraints of the platform and make their apps work. If they can't, well, I wouldn't be complaining that I need another GB of RAM to make my app work. You don't have another GB. If Infinity Blade can run on 512MB of RAM....
Listen, the iPad Air has 1GB of RAM. Period. That is not going to change. Maybe the Air 2 has 2GB. Maybe not. But any iOS app HAS TO WORK within this restriction. They have no choice. And that includes Safari.
So sometimes tabs have to reload. Every single iOS app is subject to bring booted off active RAM and bring reloaded at some point. This is iOS 101. I am able to use several tabs without reloading a single one. But then I launch another app, and I'm somehow supposed to miraculously keep Safari and all it's tabs in Active Memory as well? If the other app I launch is small, maybe. But if it needs the RAM, it is booting Safari out of active memory. Period. And that would happen with 1 of 2 or 10GB of RAM. The only difference is how many other apps I want to keep in Active Memory at the same time.
And for 99% of iPad users this is a non issue. So I'm not sure why this expectation exists that Apple designs it's products for the 1%. I'd be complaining about the closed file system a lot more than another GB of RAM...