Earlier quoted context omitted.
Eh, VBA & Excel serve a fundamentally different use-case for Microsoft. Building lots of hacky applications using spreadsheets was never the intention, and does not result in good applications. Access... I agree and miss it, but I can see why they wanted to replace it. You couldn't build scalable applications with it because of database locking, and to do the sort of stuff you can do in PowerApps you had to resort to…
Their biggest mistake was not scaling the VBA/Excel/Access stack beyond desktop and updating it. Where is the WinUI integration for VBA? The product and language was fine but it has been abandoned by Microsoft. It is easy to learn and use but they never tried to make it a cross platform technology.
Also most VBA code already written is inherently locked into the windows API and COM framework so isn’t multi-platform by design. Code written in VBA on Excel for Windows often doesn’t port across to Mac without errors because there is little abstraction from the host OS. That’s why the replacement technology is a cross-platform JavaScript API for Excel (that will eventually allow fully cross platform macros).
It does have WinUI integration via winforms, but again porting winforms to mobile and web would be a huge technical challenge and be very ugly (or break compatibility).