The user community was screaming for these; the company tried to give us what we asked for, while expanding their user base. Industry metrics show mobile is where it’s at, and I guess they figured desktop already worked well enough. It certainly works well enough for me, my complaints are mostly with the IDE.
1 Like
I turned off auto renew once I learned it was 10% off, but Black Friday was 20% off. WTF.
4 Likes
if your computer language is not multithread ready, and don’t have features like Tasks, Futures and Async/Await that can take advantages behind the scenes
Features like Tasks, Futures and Async/Await have nothing necessarily to do with multiple cores.
JavaScript has Async/Await but is single-threaded, single CPU.
Ruby has Async/Await but is single-threaded, single CPU.
Python has Async/Await but is single-threaded, single CPU.
It’s presumably possible to implement an Async/Await framework in Xojo as well. Not sure how useful that would be.
People have created an astonishing number and variety of applications with JavaScript, Ruby, and Python despite their lack of multicore support.
Multicore support is essential for a very small subset of applications, and it may be desirable for a somewhat larger subset of applications, but a large portion of applications evidently don’t need it.
I don’t think Xojo will be doomed because of this issue. (And Apple’s move to ARM is hardly an inflection point—as I noted, 8-16 thread CPUs have been common for many years already, so if this was going to doom Xojo, it would have happened already.)
Sure, but can have it. In Java, not Javascript, for instance, we can make such tasks run in different threads (or core if one less occupied is available).
In Dart, we can ask for an Isolate, and our “Task” will run in a different process (it means another core if one less occupied is available)
Me too. Just will suck when compared to others.
I had it on for a while, then I remembered to turn it off.
welcome to the one place where you can post your opinion 
stay with 19r1, if it works for you and meets your needs, no need to invest in future versions.
A14 is meant to have a lot of cores.
From Roadmap:
Multicore An easy way to utilize multiple cores in your Desktop/Console applications. Web support coming after initial release.
Will the above coming for A14 ?
Guess that depends on how fast Xojo delivers on thing doesnt it ?
Is that not just the ability to write background console apps. I don’t believe they actually have true multitcore support on their radar. Not in the way that other languages do it with coroutines or async/await that can actually delegate tasks to alternate cores.
I think the demo showed it as being able to writer helper apps right in the same project
But it only allowed you to use what amounted to the Run event of a console app
And then there is the question of what code you can share into it, whether the compiler will catch things like trying to access a global that maybe isnt part of the helper etc etc
So, not related to A14 plethora of cores.
Thanks.
No idea
Multicore is #6 on the Xojo roadmap so I dont know what that means in terms of WHEN it might occur
1 Like
mmmmm, behind android, api2, web2 ios2 etc etc, so never probably, or when another tool is available that can do all those things, is free and can multi core operate.
or if we are very lucky apple make an os that automagically spreads the processing along all the cores without a developer thinking about it… roll up Rick, never gonna give you up…
The whole roadmap for Xojo will probably disturbed by Apple when they do ARM transition.
I have come to the same conclusion – about beginning a move to Swift as well as the discovery that Swift itself isn’t the difficulty, rather the Cocoa framework and it’s depth.
I am also finding it difficult to find many educational resources for Swift for Mac OS development.
Have you found any good resources you might care to share?
Cheers
IF they do ARM
its still just a rumour at this point
if its announced then we can all wonder what it will mean 
I had done a lot of learning about Swift from the iOS point of view. But had one very large project in Xojo that Xojo management was not happy about. So I decided to say “FU Xojo” and I’m doing it in Swift … it is a macOS project… and you’re right, the amount of decent documentation especially with examples is practically non-existent… So I’m doing a lot of trial and error, and so far have solved all the issues I’ve run across.
I would say post any questions you have in new threads in “General Programming” and see what answers they gather
IfNotNil is NOT tool / language specific 
So if Apple goes with ARM technology… it will be mostly all new, meaning that the Intel platform will be older legacy technology.
Does that mean that in the abbreviated parlance that IT seems to love this would be referred to as
ARM and LEG
just saying
2 Likes