My take on this question is a little different. Few people posting in the P&S Forum are qualified to have an opinion on VBA because you think nothing of creating a project in Visual Studio, writing efficient code in C++ or C# to solve a problem, and jumping through the ExcelDNA or XLW hoops to create an addin. There are millions of people (at the risk of sounding like Carl Sagan, but I don't think I am exaggerating) who are just about able to augment their workbook with a bit of VBA code, most likely subroutines based on recording spreadsheet actions, who wouldn't have the first idea of how to install VS, let alone figure out what to do with it. From that starting point, there is a very long way to go, including figuring out how to write, debug and test functions, before having any consideration of stepping outside of the native Excel bubble. For this type of user, I think VBA is much better than nothing, which would seem to be the most likely alternative.