Originally Posted by erann
I am trying iCloud at the moment at my summer house in the middle of nowhere over a lousy 3G network (download speed 1,5 M, upload 1,5 M) and Pages is incredibly fast! Can't wait to get back home to try it over proper internet connection.
I'm using 15" MacBook Pro (2,6 GHz Core i7, 16 GB RAM).
A lot of people are posting responses like this, all I can say is that what I described is exactly how it worked for me.
I do a lot of writing and I'm generally working with a document that's around 100,000+ words or about 400-500 pages. When I tested it I was at work on an iMac on gigabit ethernet at an organisation that forms part of the internet backbone so there shouldn't be any speed problem with my connection.
I am of course not in Southern California. I find it frustrating that so much of the time when someone like me posts a speed problem the internet becomes alive with "works like a rocket for me" comments all mostly coming from Americans, and primarily Americans living in Southern California. Speeds will no doubt vary around the world.
Scrolling issues like the one I described would seem to me to be far more concerned with the browser cacheing than internet speeds anyway. For any web based editing program to work well, it needs to be able to effectively cache documents of multiple gigabytes in size (at minimum) and sync the changes back and forth to the cloud.
If it really is reaching into the cloud for data when I scroll unexpectedly from page one to page 251, then that's just a bad design IMO. Perhaps they have optimised the performance for the typical two page, "I'm making a flyer for my lost cat!" document and not for people doing actual work. Again I think this is a horrible mistake if true and simply, bad design.
I won't go on further as it is a beta, but it has a lot of problems from my point of view and they have made some bad design choices IMO (like having documents open at a set default resolution instead of "fit to width" without letting the user set or alter that default resolution). The lack of support for plain old English as a language is also alarming. It needs to launch with multi-language support at minimum. I can't imagine they will really launch it without supporting the main English language and I will be shocked (and very complainy) if they do.
In regards iWork in general (not just the web version), I'm just disappointed in the disrespect Apple has shown for what are for me, a central and very important applications. The lack of any significant updates or effort on their part, and the lack of attention to detail is atrocious. The idea that they seem to actually think their work is "done" or "good enough" and are thinking of making the whole thing free as part of a loss leader package to sell hardware infuriates me. I've got a lot invested.
A lot of users like me *believed* Apple when they said they were serious about making the iWork apps serious competitors. I think they've let down all those people who actually took them at their word and moved all their creation away from Office to iWork. I think they owe the users of iWork apps, who have been suffering all this time, a far bigger apology than the one they gave to the few users who lost data on MobileMe.
If the team leader for iWork apps was in front of me at this moment I'd step on his/her foot and slap them in the face.
And I say that as a lifelong Apple supporter and someone who has never actually hit anyone in their life.