I wish I knew what these huge issues are surrounding Blitzmax. For my next game I'm hoping to make the leap up to Bmax...so spill the beans please!
I'm a lone coder so I don't know from experience, but from what I've read about other's experience:
Blitzmax is easier and quicker to maintain when working with teams, compared to c++ and c#. That means you'll finish projects faster, which also means they'll have nothing to do afterwards.
Also, since you do not need to maintain three different versions of the code for three different platforms, you'll have the need for fewer coders.
So you have fewer programmers and the programmers you have work fewer hours. This is a very unacceptable practice for the Programmer's Union (PU), and can result in PU relations problems.
I just read in the newspaper last week that the PU at a huge gaming company was on strike because management refused to replace the coffee holders with better ones. The current ones would break often, and when they didn't break, they'd sometimes slide back into the computer spilling coffee everywhere. The strike was ended when management finally agreed to new cup holders, but in exchange that they stopped the practice of putting comments in all their code, that was marketing's job.
So if you don't want all the Union headaches, you are better off dropping BlitzMAX in favor of a less efficient language that better supports job security.
In case you haven't figured it out, the above was intended to be taken tongue-in-cheek.