Well, 1000 item limit on offset wasn't introduced recently. It was always there, and it was always documented. It's actually that no matter what you do, query always returns max 1000 items, offset just works "locally" on these items. There have been workarounds floating around the net, I remember one about using filtering on timestamps.
What is not documented is 1MB limit on memcached entries and also on HTTP response size (I found out only cause of exceptions). And there is 5 second limit on urlfetch with undocumented cryptic "DownloadError: ApplicationError + various numbers" exceptions.
What is tricky is that many limits happen only on production servers, so you don't discover them on a development one.
On the plus side, limits are very generous on memcache total size. Which is good as even trivial operations on datastore take a lot of CPU cycles.
Still, limits can be good. They force you to architect your application in a different, hopefully more scalable, way.
What is not documented is 1MB limit on memcached entries and also on HTTP response size (I found out only cause of exceptions). And there is 5 second limit on urlfetch with undocumented cryptic "DownloadError: ApplicationError + various numbers" exceptions.
What is tricky is that many limits happen only on production servers, so you don't discover them on a development one.
On the plus side, limits are very generous on memcache total size. Which is good as even trivial operations on datastore take a lot of CPU cycles.
Still, limits can be good. They force you to architect your application in a different, hopefully more scalable, way.