In another thread, Erel posted this today:
I know that Anywhere Software prioritize the ability to run old code in new versions of B4X, and I do think it is the correct decision. However, I wish for a slightly less rigid enforcement of this, so we can remove some of the old stuff that wasn't great. The details on how to do this can be discussed, but one way of doing it that strikes me would be this:
Erel posts a survey(*) with a description like:
"I would like to remove/change Q because of reason X, Y and Z. Potential issues if I were to do this is A, B and C which can be solved by doing D, E or F. If you find it not ok to remove, please briefly explain what the problem would be for you. This survey will close in M months."
Example options in the survey:
The survey could be open for a really long time, like 3-12 months, to make sure everybody in the forum sees it and gets a fair chance to make their voice heard.
When the survey is closed, if there's too many(**) users saying it's not ok to remove, then it'll stay. Otherwise, post a statement that the feature is expected to be removed/changed in an upcoming version and that it's a good idea to start preparing if you need to change your code beforehand.
(*) Preferably in a subforum called something like "Development of the B4X language" (that only Erel can create new threads in?), or something to that effect. But whatever forum makes sense is fine, obviously.
(**) I'll leave it to Erel to decide what "too many" means.
I know that Anywhere Software prioritize the ability to run old code in new versions of B4X, and I do think it is the correct decision. However, I wish for a slightly less rigid enforcement of this, so we can remove some of the old stuff that wasn't great. The details on how to do this can be discussed, but one way of doing it that strikes me would be this:
Erel posts a survey(*) with a description like:
"I would like to remove/change Q because of reason X, Y and Z. Potential issues if I were to do this is A, B and C which can be solved by doing D, E or F. If you find it not ok to remove, please briefly explain what the problem would be for you. This survey will close in M months."
Example options in the survey:
- I never use this - ok for me
- I have used it but I can change - ok for me
- I use it now and then, it would cause big problems for me if removed - NOT ok for me
- I rely heavily on this in my current day-to-day coding - NOT ok for me
The survey could be open for a really long time, like 3-12 months, to make sure everybody in the forum sees it and gets a fair chance to make their voice heard.
When the survey is closed, if there's too many(**) users saying it's not ok to remove, then it'll stay. Otherwise, post a statement that the feature is expected to be removed/changed in an upcoming version and that it's a good idea to start preparing if you need to change your code beforehand.
(*) Preferably in a subforum called something like "Development of the B4X language" (that only Erel can create new threads in?), or something to that effect. But whatever forum makes sense is fine, obviously.
(**) I'll leave it to Erel to decide what "too many" means.
