If I want to use all of these patterns I would program directly in Java.
B4A is usefull because B4A is simple.
If you want to have all the possibilities of Java, use Java.
I keep seeing these comments. Use Java, Use Java, Use Java. ??????
There are so many reasons to use B4A, the answer to every feature request is not to use Java. Its not a valid retort to a feature addition request.
I agree that adding too much of the requested stuff would
1. need a serious rewrite for a few people who would use it
2. make B4A look complex like the rest so people would skip it
This is the most valid concern. When classes were introduced, I thought I would never use them.
But using them refactored my code so far down, I can write reusable code within minutes, and a lot less bugs. I can show you the first versions of my code and the code with classes and there is no doubt in my mind that classes is the way to go.
The real art is to implement the 'advanced' features in a way that it doesnt come in the way of the 'simple' users.
For e.g. I never use Designer Scripts, but its an awesome feature that is there, it never comes in my way.
if you are a bad coder your apps will still be bad if you add OO or other "theoretically usefull" features.
This comment makes no sense. If you are a bad coder, you will still be bad with basic stuff.
The question is what will limit you if you are a good coder?