[UnoriginalGuy]

The two are completely district languages. Kind of like comparing Java with JavaScript.

I'm sure in general Microsoft would love to scrap VB in Excel but there's too many companies that run entire areas of business on it, or the whole business itself.

It is the typical legacy/back compat problem. Python or even Powershell would be a vast improvement, but you're going against billions in sunk cost/skills/knowledge.

VB.Net was slowly losing popularity, VB in Excel isn't.

[Exmoor]

Would it be impossible for Excel to allow coding in multiple languages? I totally get that there's a huge (disturbing) amount of business critical stuff using the current scripts, but they really should move on to something more modern.

[applecrazy]

That’s a thing now, but for add-ins: https://docs.microsoft.com/en-us/office/dev/add-ins/referenc...

[toyg]

Multiple-language runtimes typically don’t get popular - people just end up choosing one language and standardizing on it. See for example Windtows Scripting Host: you could always use Javascript with it, but almost nobody ever did in practice. After a while, typically the vendor sees other languages as a drag on development, and they get dropped in favour of the main one.

Retrofitting a multiple-language runtime under VBA would likely be a big endeavour, and in the end most people would probably stick to the established language anyway.

[cm2187]

Microsoft pretty much built it (would allow any .net language to behave like VBA, with an integrated IDE and ability to save code inside the document). Then they killed it. I think that was a huge mistake from a productivity point of view, and also to get a fighting chance to retire VB6.

https://en.wikipedia.org/wiki/Visual_Studio_Tools_for_Applic...