My point is that we need a modern solution, and there’s one built into the OS, which works incredibly well in my usage, and yes, I’d like to be able to utilize it directly from within Xojo and take advantage of a dev tool and language that I am more comfortable with.
I know you don’t think that Xojo using GCD is a good idea, and I personally don’t see much value in using a limited scope scripting language that probably isn’t going to make it any easier to do what I do (which is what I want).
Are plugins, JIT and helpers permitted on the iPad? If not, then GCD is pretty much the only choice Xojo have left going forwards. Catalyst is here now, enabling iPad apps to run on the Mac (and I’d imagine with the same limitations). I pretty much expect when ARM based MacBooks arrive, iPad apps are what it runs.
Another concern about JIT, is that it’s already on Apple’s “Security” list. With Harden Runtime, JIT is barred by default and requires entitlements to work, if Apple decide that the JIT entitlements are only temporary (which has a strong possibility as Apple do NOT communicate their intentions to use developers, if we’re lucky we get a Deprecation warning, if not, it’ll just dissappear like some other entitlements have done), JIT based apps will no longer work going forwards, and in this case JIT is being used a substitute for GCD.
Anyhow, it’s not like you or I are in a position to make either solution for Xojo, who knows, maybe Xojo already have a plan, maybe it’s already underway, maybe it’s something that neither of us can see, and will blow us out of the water.
In the mean time, I’m going to be moving my most demanding logic over to t’other tool, if I have the time, I might even see if I can utilize a block to callback in Xojo to do some primitive work using native Xojo. Which would simply my workflow as I’d only need to edit one project in one language. After using two or more languages throughout a week, I often end up mixing them up, which kills productivity as my brain doesn’t see a problem.