It doesn't matter how it's done. What matters is the result
I get why the "distrust" face, and its all about technical debt. If the company thinks B4X is unknown/obscure and too small, it might end up the way of COBOL did. If that employee leaves, quits, retires, etc, is it "industry standard" enough to bring someone in to take over? or does it become technical debt and require a complete rewrite in more standardized environments?
The entire topic is debatable and subjective but that's what goes through the minds of corporate executives. the COBOL reliance situation has become such a huge problem, they are trying to incentivize developers to get back into it and teach it again to take over the now aging/retiring programmer base for that language.
The same thing happens to me a lot where I work. I am the only developer currently, and I have total control of the tech/apps. But when people ask me what i develop in and I tell them? I get all kinds of strange looks.
Then I get the question of: "So your entire ecosystem is reliant upon one man/company? What happens if they pull the keys or otherwise rip the rug out from under you? are you SOL?" And yeah... its a good point.
We were looking at getting acquired one time (actually a couple times) and during the due-diligence process, it got broken off due to how obscure the source tree was, they didnt have anyone qualified to value or vet the B4X source code so they valued the entire technology platform at $0 in the proposal, basing it only on the customer base/sales so we said no.
It is a real issue, but I keep plugging forward.