It ultimately doesn't matter. Excel macros are code, and they are very often production-critical code. The people who wrote them don't see themselves as coders

It ultimately doesn't matter. Excel macros are code, and they are very often production-critical code. The people who wrote them don't see themselves as coders, sure, and management often doesn't give the code the respect it deserves (e.g. Excel is often exempt from basic things like version control and code reviews), but it's still code that the business still depends on. When someone proposes replacing MS Office with LibreOffice, what they're really proposing is to replace the runtime that a significant amount of production code runs on with something that's only compatible with part of your codebase. "If we switch, we are going to have to rewrite a decent chunk of our production-critical code" is a non-starter, especially when coupled with the fact that the developers have no experience with the new runtime and are going to have to learn it as they port the code. And because they don't see themselves as coders, they don't have the theoretical background that makes it easier for experienced software engineers to pick up new languages.