Numbers; The good and the bad
I picture the Numbers development team anxiously reading this board and near tears because of the discouraging reports of poor performance.
I'd like to give them a word of encouragement - remember, nobody gives you feedback like this unless they care about the product and want it to improve.
More to the point, I think Numbers' design is wonderful - it has more innovation in one or two features than the Excel guys put in their whole product!
I hear a lot about people with megabytes worth of spreadsheets that can't convert to Numbers. But it's not just huge and complex data sets. I took 8,500 rows of data from my Google Adsense results and found Numbers would beachball when I just clicked on two columns and attempted to change them to currency.
Even when I tried a smaller 550 row data set and did the same thing, it took over a minute of beachballing before it converted.
So I am in a truly sad position - someone who loves Numbers and its potential but can't really use it 😟.
I look forward to further updates.
Or am I doing something wrong?
D
PS One relatively minor nit that should be easy to fix: My Google data, coming out with an extension of .csv, is really tab delimited. It might be wise to check for tab delimited formats when csv is spotted. For anyone gappling with this issue, the solution is to change the extension to txt, and Numbers will see it correctly. But it would be nice if .CSV worked because the default program to open .txt files is generally not Numbers.
I'd like to give them a word of encouragement - remember, nobody gives you feedback like this unless they care about the product and want it to improve.
More to the point, I think Numbers' design is wonderful - it has more innovation in one or two features than the Excel guys put in their whole product!
I hear a lot about people with megabytes worth of spreadsheets that can't convert to Numbers. But it's not just huge and complex data sets. I took 8,500 rows of data from my Google Adsense results and found Numbers would beachball when I just clicked on two columns and attempted to change them to currency.
Even when I tried a smaller 550 row data set and did the same thing, it took over a minute of beachballing before it converted.
So I am in a truly sad position - someone who loves Numbers and its potential but can't really use it 😟.
I look forward to further updates.
Or am I doing something wrong?
D
PS One relatively minor nit that should be easy to fix: My Google data, coming out with an extension of .csv, is really tab delimited. It might be wise to check for tab delimited formats when csv is spotted. For anyone gappling with this issue, the solution is to change the extension to txt, and Numbers will see it correctly. But it would be nice if .CSV worked because the default program to open .txt files is generally not Numbers.
PowerBook G4 17" ("last of the G4s"), Mac OS X (10.4.10)