alphaman

I love Numbers. I've used Excel since it first came out on the Mac back in the '80s, through a couple decades on Windows for Intel and Alpha, and have learned to loathe the ribbon and user-hostile interface it has. However, I do have one gripe, and one hidden power feature not touched on above, regarding Numbers.

First, the gripe. Numbers has never had pivot tables. In the iWork 9 version of Numbers, it had Table Categories, and that was a brilliant way of viewing the same detail. Sadly, that was stripped out during the iCloud-enabling rewrite and no longer exists. I'd love for Table Categories to come back!

Not mentioned above: when laying out your sheet full of tables and charts and pictures and text boxes, you can easily arrange things that don't print out well. Turn on your rulers and drag guide lines to match your print space so that you can be sure to place elements where they'll not be ignominiously chopped up in little bits when transferred to paper or PDF. Just calculate your print space as your paper size minus your margins (top + bottom, or left + right) and divide by your print scale factor. I've not found an automated way to do that -- perhaps Apple could add such a feature?

Didn't the FBI (or was it the DoJ?) come out and say yesterday that Apple had never objected to any of the previous requests for information, contrary to what Apple claimed in their Open Letter? If this is true, then the FBI has been caught in yet ANOTHER lie. The others: 1) This will not set a precedent. Proven false by the queue of police departments now lined up with iPhones in-hand, waiting to be unlocked. 2) The County did it! Proven false by the County stating that they were working under the FBI's orders. 3) Sending Apple on a 2 week wild-goose chase to initiate iCloud backups after they'd already reset the password. 4) This is not a backdoor! Well, technically, yes it is. If the FBI's technical people don't know what a backdoor is, ... wait, the FBI doesn't know what a backdoor is??? Bwahahahaha!!! Riiiighhhttttttt... 5) We're not breaking encryption! Except you're asking Apple to bypass the system's security, so that you can brute-force-guess the password to... yup, break into the encrypted device. 6) The code will never leave Apple. Except for the data to be entered into court, the defense will rightfully have to do due diligence and ask to see the code to make sure that it is valid and the data is therefore valid -- in their labs, not Apple's. Geez, 6 lies -- no, 7 -- right off the top of my head. This is unconscionable.

Oh, one more gripe. (Sorry.)

32,768? Really Apple? These machines have gobs of virtual memory. I deal with spreadsheets that frequently have more than 2^15 rows. This is a 64 bit machine -- would 2^32 rows really be too much to ask for? 

Uh, what about EV routing? This isn't just "EV Data", it's intelligent routing to your destination plotting multiple charging waypoints. This is HUGE, especially with CarPlay integration. Can't believe it's (sort of) mentioned in the title but not ONE WORD in the body...