(04-24-2022, 02:36 PM)dano Wrote: Thanks for the update, I really appreciate knowing more on why. I have to say that I was genuinely worried quite a bit about the future of QB64.
QB64 is key to my business...let me explain:
Hi Dano,
Did you ever visit The QBasic Forum, back in the day? I also posted there as "Pete." I ask, because we were on the same page, using QBasic to run a business. Same memory ceiling. I somewhat broke that ASCII ceiling by using databases to RUN, not CHAIN, other QuickBASIC exe files I needed in my office program. I think I had 14 programs in total, and each of those was close to the memory limits. Also, I was able to get about 250K per program, by making each program, usually limited to between 50-64K, into a multi-modular program. If I hadn't learned how to do that from some book, I would have needed around 40 interrelated programs to get the job done. Anyway, when this guy Rob started his QB64 project in 2007, which we hosted it over at The QBasic Forum, I help beta test it by converting and combining all of those 14 programs into one single program. I was very happy that after all the issues were worked out, and the compiler speed improved. I ended up with a fully functioning SINGLE program!
So even though I often refer to QB64 as a hobbyist language, I also know from experience, and a couple of other friends you used it similarly, that it most certainly can be used for business purposes. The only shortcoming of the language, as I see it, is as a C/C++ translator, it is nothing we can use to make mobile apps, which run on JAVA. Oh, and not for website work, except wait... a member here who goes by dbox has a neat project underway, which converts qb64 statement to JavaScript, and that, of course, will run on the Web!
Anyway, great to read your story, welcome to the forum, and I hope you enjoy your stay.
Pete