If I were to add all the features listed in the first post, it will be the end of B4X as a RAD programming language.
"all the features listed"? I "thought" they was "one", OOP features (I'll read it again).
I think it would be the end of the RAD B4X only if you forced your customers to use OOP (can you do it? ?).
I think the "term" RAD was born only to indicate development tools that allowed to quickly create GUIs, not so much related to the language, which I don't think must have particular characteristics in order to be part of a RAD tool.
B4A is clearly better than Android-Java not because OOP is missing but because it (and its IDE) "hides" many complicated things, it simplifies them, automates them. An example, not the best one, is that a B4A programmer could develop his own apps without even knowing that an object called Context exists; this applies to many other objects and "mechanisms".
I read about Inheritance versus Composition and GO (Google) is cited as an example. Indeed the first one could create more problems than the second; on the other hand, programmers have been accustomed to using inheritance for many years.
I repeat
my opinion: if adding OOP features doesn't require too much work (
but I don't think that's the case) having it at your disposal can only be a
Plus for B4X and this could convince many skeptical people about the quality of B4X, those who underestimate B4X only because of the lack of OOP.
Incidentally, I think that B4X is poor because a snippets manager is missing ? (I'm joking here, of course - also because maybe soon I'll develop one for myself)