What's good about PureBasic?
Okay, I've hesitated about posting this, but here goes:
The number one thing about PureBasic is that it allows you to get applications up and running very quickly. This in turns means fast turnaround on projects which equals profit. However you measure that, be it money or time savings or just satisfaction.
Right now I have 5 computers networked and connected online via a router. All of the gear was "bought by PureBasic", this calendar year, working part-time for "fun and profit", as the saying goes. I have also had some good nights out and a few personal perks, and have some cash in hand. For, all up, max 40 serious hours. Add 20 for the yarning and relationship-building you do when you deal with people.
All of the earner apps are almost purely Pure. A few API calls for things like getting current directory name, and similar. No user libs, no ASM. If it needs heavy ASM it needs MASM. If it needs heavy libs, it probably needs to be in C/C++ or VB/FB.
Importantly, all of the Apps are within the capabilities of PureBasic and don't require expensive (in time, and therefore in money) workarounds. This translates into more competive quotes to the prospect. Which in turn translates into more wins. Both ways - mine and the end-user's.
That has to be a plus!
As Pure adds more - like double precision and unsigned longs and etc - more doors will open. (Or, more accurately, I will be willing to go through more open doors.)
For others, perhaps PureBasic allows the framework to go up quickly and they are willing to then do the workarounds. For me, keep it pure or use something else. It doesn't really matter, the fact is it is a RAD without the RAD.
Scattered throughout these forums there are stories like this. Some are earner stories, some are time-saver stories (same thing, really) and some are by people who do heavy duty work with industrial-strength languages. In other words, very credible people (despite the sniping some of them took on this thread

lol)
@}--`--,-- A rose by any other name ..