> Microsoft Excel could just about cope but was struggling to scroll or filter data. Eventually I gave up and threw it into MySQL. The right tool for the job.
Although Excel has since been corrected for this use case[1], it isn't even the right Office tool for the job. That's what they created Access for.
[1]The SQL Server team built PowerPivot for Excel 2010+, which basically imports your data into a SQL db that gets embedded into the Excel file and transparently queried from Excel proper. Runs smooth as butter, and pacifies the Excel purists who refuse to lower themselves into using Access (I've worked with several of said purists).
You're correct, and Excel for Mac also doesn't support the PowerPivot addon either. However, that still doesn't mean you can fault Excel for barely being able to cope with a use case it isn't designed to support. The fact that it can handle it at all is a testament to the versatility of the program, not the other way around. It simply isn't the correct tool for the job, and shouldn't be faulted for subpar performance in a scenario it wasn't designed for.
Writing code in Word is completely possible, but would you fault Microsoft for the ensuing bad experience? You can also use Eclipse for writing a resumé, but would you fault it for not supporting that use case very well?
Although Excel has since been corrected for this use case[1], it isn't even the right Office tool for the job. That's what they created Access for.
[1]The SQL Server team built PowerPivot for Excel 2010+, which basically imports your data into a SQL db that gets embedded into the Excel file and transparently queried from Excel proper. Runs smooth as butter, and pacifies the Excel purists who refuse to lower themselves into using Access (I've worked with several of said purists).