I have used Blitz (Plus) in the past for business purposes, but not at this job.
Although there are a few things we are doing that I think would be better developed in BlitzMax than .Net or C++. .Net has more overhead and C++ tends to take more time. Max is close to C++ in performance and can be made to take up small amounts of resources.
We have several smaller tasks that require no database connectivity, etc. that could've easily been done in BlitzMax and would probably make more efficient use of resources.
I think BlitzMax is still too unknown to be "allowed" in most business environments, because most companies will look for something they know they can find other hires to work on, and also most managers like to stick with big names.
As much as the GUI needs enhancement, BlitzMax needs a standard database API to be accepted by most companies, and that means ODBC or similar. At that point it'd be a pretty impressive app, cross-platform, good GUI, SQL support, you'd be able to pull in some smaller shops and go from there.
For what I do, BlitzMax as is now plus a good DB module would be able to cover most of the work I need to do, at which point it'd just be the work of convincing the company to shell out for a licence or ten.
Another way to get BlitzMax wider coverage would be to get it into some of the emerging markets, such as the mobile apps arena. Developers in emerging markets are more open to using less well known products.
Although there are a few things we are doing that I think would be better developed in BlitzMax than .Net or C++. .Net has more overhead and C++ tends to take more time. Max is close to C++ in performance and can be made to take up small amounts of resources.
We have several smaller tasks that require no database connectivity, etc. that could've easily been done in BlitzMax and would probably make more efficient use of resources.
I think BlitzMax is still too unknown to be "allowed" in most business environments, because most companies will look for something they know they can find other hires to work on, and also most managers like to stick with big names.
As much as the GUI needs enhancement, BlitzMax needs a standard database API to be accepted by most companies, and that means ODBC or similar. At that point it'd be a pretty impressive app, cross-platform, good GUI, SQL support, you'd be able to pull in some smaller shops and go from there.
For what I do, BlitzMax as is now plus a good DB module would be able to cover most of the work I need to do, at which point it'd just be the work of convincing the company to shell out for a licence or ten.
Another way to get BlitzMax wider coverage would be to get it into some of the emerging markets, such as the mobile apps arena. Developers in emerging markets are more open to using less well known products.