Wow. Threading was long time whished feature.
(MBS Xojo Developer Conference: Thursday - #12 by Christian_Schmitz - Events - Xojo Programming Forum)
getting makes it sound like ānext weekā
which makes it sounds more like they havenāt started
preemptive threads WONT operate during debug runs so youāll have the same less that ideal set up with workers and can really only test them in a BUITL version 
and realistically it will take a long while, like everything has with Xojo, to get the first cut and then iron out the bugs
It could be a very long while before they prove to be useful
SO dont get your hopes up too high right now
Not working in Debug mode. Wow. What shall that be? Maybe my Ideas are a way toā¦ but Xojo is all time good for bad good news. This is not usable at all. How shall that work? Canāt debug like I need to? I have no Idea. And no words for that.
If it turns out anything like workers kind of crappy since what works in Debug with workers may not work with them in a built app
So you have to resort to some hand grown printf style debugging to a log file to debug them using a built app
Its f*ugly
Lets say this
Iām NOT holding my breath about it because, like so many other things what they promise & what gets delivered dont often match
VERY skeptical they can deliver on this in a meaningful way or decent time frame
Ahhm sorry but that is more than outdated. Then I could go back two decades. They have no multithreading while nobody will reALLY WORK WITH THISā¦ Sounds like a bad try to bring a new technology. Shows that they have no technology guy to do that really. Maybe they should think about refitting to API 3 and use kotlin syntax. Then they have a nice compiler and can work along exactly that.
I might suggest updating the title to more accurately reflect that there is no timeline on this.
That means nothing. They have so many things without timeline. Android was without. And that came blazing fast if I remember correct. Shit dementiaā¦
ESP since Xojo has NOT committed to it being in the next version
More a someday weāll have it based on reports from the @MonkeybreadSoftware conference
Tell me again how long it took to add Android supportā¦
Why did the multi-threaded chicken cross the road?
to To other side. get the
one lesson everybody here learnt from Xojo:
itās ready when itās shippedā¦ and even then it is still unfinished, buggy and awfulā¦
If it is still unfinished (which is usually is) then it was not āreadyā when it was shipped
well thereās the āpromiseā
It will start to appear in 2024r2 (screen shot taken JUST for posterity)
Upgrading the debugger is no priority. It will be a testing nightmare.
Yes, that was his reply to me. So is he saying that shipping the shiny is a priority over proper implementation? That was sort of my readābut Iāll say that here, not there. 
Hmā¦didnāt seem āpracticalā when a customer was willing to pay for the feature. But hey, now that that customer has moved on we will take a stab at it and give you something that may or may not work! And weāll dribble out classes if/when we decide to!
My limited understanding is that like workers they wont use preemptive threads in debug runs, and will use threads like they do for workers
And only in a built app will it use preemptive ones
That will, like workers, mean debug runs are quite useless for debugging built app behaviour since they use two entirely different mechanisms
ā¦and as Geoff told me (quite explicitly), that is not a priority. Oh yes, he did qualify with āmaybe somedayā¦ā
at least a worker can be kind of built as a separate console helper then the code mode over
so you can debug that twice (yay !)
preemptive threads need to be debugged in situ so you have some hope of isolating where you need mutes, semaphores, etc
yes its not a trivial āhey look weāre buzzword compliantā thing
its a LOT of work
but if you want to be more than buzzword compliant then you do the work
the responses Iāve seen so far lead me to believe its yep we can check that one off the roadmap and list it on the sales brochure! Next !
< cough> iOS ā¦ Android ā¦ Web ā¦ </ cough >