05-08-2022, 02:38 PM
It feels great that QB64 is once again alive and well. I'm not sure if it's realistic of me to expect it to be around FOREVER. I do have grand children who are now leaning to code at school and asking me questions. I hope to turn them onto QB64 basic language.
Given how we almost lost everything, I was wondering if there may be some kind of steps or ideas we should be considering that not only can avoid (if not just tone down) fatal arguments and perhaps we should also consider ways we can support key development members who may need a break or even retire. A way QB64 lives on after we are gone.
I guess ... once burned, twice shy ... being the selfish person I am, I'd hate to lose you all again.
Given how we almost lost everything, I was wondering if there may be some kind of steps or ideas we should be considering that not only can avoid (if not just tone down) fatal arguments and perhaps we should also consider ways we can support key development members who may need a break or even retire. A way QB64 lives on after we are gone.
I guess ... once burned, twice shy ... being the selfish person I am, I'd hate to lose you all again.