Excel is increasingly being used as Microsoft's gateway drug to an excellent self-service BI platform, Power BI. There is incredible power in providing a smooth (and approaching seamless) upgrade path from workbook with embedded queries, to a proper dimensional modelling tool (Power Pivot, AKA SSAS Tabular columnstore engine), to a proper dashboard visualization tool (Power View), to a hosted, centralized team solution (Power BI portal - mobile app batteries included), to an on prem enterprise-grade analysis engine (SSAS Tabular).
Again, this is not a refutation, but a new use case and powerful new functionality to address the concerns you raised in Fallacy 2.
The only thing is that the reason VBA is so widely used is because it's built in to every single version of Excel (except Excel 2008 on OS X), which is why it's ubiquitous. Are Power BI and PowerView things that can be used within Excel without using a server? Are there additional licensing costs?
The desktop and mobile apps are completely free and the desktop pieces can be used without a server. The web portal is cloud-hosted and freemium to anyone with a corporate email address and the mobile apps require at least the free web portal.
Feel free to email me if you're curious about more details. Gregory.Baldini at gmail dot com.
On the one side companies want to ged rid of their Excel data silos with many unverified formulas, on the other side some choose a BI platform based on Excel (data is loaded from MSSQL DB).
Additionally, the hosted solution allows Excel Services to be the presentation layer, but the real push is toward Power View.
I would suggest you do more research before spreading this disinformation. There has been significant development on this front and what you are saying is very much out of date.
Power Pivot is the Excel add-in (available for Excel 2010+) which enables dimensional modelling and >1M row analysis in Excel, and which can be transitioned to a hosted environment via SharePoint and SQL Server.
Starting with SQL Server 2012, SSAS includes Tabular mode, which allows a seamless upgrade path from an Excel Power Pivot model to an SSAS instance.
This is seamless because the same DB engine is used in both products. Power Pivot runs a private, anonymous instance of SSAS Tabular behind the Excel process, with a few features disabled (e.g. row-level security).
Power View is a high level visualization and dashboarding tool introduced for SharePoint 2010 and 2013 as a part of the SQL Server 2012 SSRS module.[1] This is the visualization tool designed to pair with Power Pivot and the Tabular model. It is also available as an add-in for Excel 2013+[2], and as part of the standalone Power BI Desktop[3] which has been available since Power BI portal's general availability in July of 2015.
I do not know what you are referring to by saying that there is a 1M row limit in practice with SP 2013 and SQL Server 2012, because this is simply not the case. If your organization is not using the features and these are pain points for you, I'd love to have further discussion with you offline - my email is gregory.baldini at gmail dot com.
[0]https://technet.microsoft.com/en-us/library/ee210682(v=sql.1...
[1]https://support.office.com/en-us/article/Power-View-in-Share...
[2]https://support.office.com/en-us/article/Power-View-Explore-...
Use Case 1: A basic spreadsheet for data manipulation, with no extensive macros or VBA involved. People use it for vlookups and other formulas they find useful.
Use Case 2: As a statistical analysis tool to crunch data.
Use Case 3: As a software platform, making extensive use of Visual Basic for Applications (VBA).
So here are the issues I have with your statement that Excel "is far and away the best, fastest and most robust spreadsheet out there"...
Fallacy 1: Excel is the best technical option
Excel is not necessarily the fastest spreadsheet out there for all operations. In many cases I believe it is still very fast, and beats LibreOffice under certain document loads, but this is often not by much and in fact there is ongoing work towards locating problem documents and profiling of LibreOffice code to remove bottlenecks. In fact, in LO 4.2 many performance bottlenecks were largely solved. [1]
At this point, I do think it's largely a myth that Calc is dreadfully slow. Even if it should be found that there are performance issues, however, I know that the LO community, and in particular Collabora, have a good story around their ability to use valgrind to benchmark and analyze results. As a normal part of development work, Collabora are often provided with documents that they analyse and contribute performance improvements into the core LO code base.
There are many, many errors in even basic statistical functions in most spreadsheet applications, but Microsoft Excel is particularly egregious. However, IMO the LO devs are more thorough when it comes to this [2][3]. So for use case 2 (statistical work) then I think it's not suitable (actually, for any stats work, why not just use R?)
So if Excel is not necessarily better than Calc in terms of performance, accuracy or overall robustness (you might want to look at a feature comparison here: https://wiki.documentfoundation.org/Feature_Comparison:_Libr... - quite informative I think!) then really the issue is that it's being used as a platform for VBA development.
---
Fallacy 2: Excel is the best integrated option for office application development work
So now here is the rub: this has been something causing Microsoft vendor lockin for years. Expertise in financial firms around Excel is very high, and often quite extensive custom "solutions" are based on Excel spreadsheets, but almost always via VBA.
But... Microsoft's VBA diverged from Visual Basic in VB6, and Microsoft have been struggling to know what to about it ever since. I point out that they removed support for VBA in Office 2008 for OS X, but then had to put it back in due to market demands in Office 2012, and I also note that the only update to VBA7 is to introduce actual pointers.
So basically, this will only be a competitive advantage for so long for Microsoft. As the marketplace starts to open up - and it is! - firms will be looking for solutions that either do NOT rely on Excel or VBA and that can integrate with better scripting languages, like Python.
In fact, I've been hearing that a lot of financial institutions are getting quite concerned with data silos: these are usually in Excel, haven't been audited, aren't integrated into the business' DW, are isolated and thus cause problems with transparency and decision making, and are almost NEVER documented meaning that should the maintainer leave then that spreadsheet will either be used and unmaintained, or will need to be redeveloped anyway.
So really, the key advantage Excel has is ubiquity, and really only then because of VBA, but that's a double-edged sword and eventually businesses will migrate away from it.
1. https://wiki.documentfoundation.org/ReleaseNotes/4.2#Perform...
2. http://lists.freedesktop.org/archives/libreoffice/2013-April...
3. So far as I'm aware, Excel's RNG is now using The Mersenne Twister algorithm in Excel 2010 and beyond, but that's not officially confirmed from Microsoft. It's very hard to be certain of what is being used without such a confirmation, and given that Microsoft has form in releasing a flawed RNG update already (which they never got around to fixing for years and years!) I don't know how you could consider Excel to be "more robust" than LibreOffice.