@Rich H Though I never embraced Xojo Core in my projects, one of the sentiments that I had during the conference was API 2.0 would be the way forward while original framework / core framework could be used, it would not be updated unless there was a serious bug. Also, once you move to later releases of Xojo, it wont be possible to bring your project back to earlier versions.
Again, it makes sense, we just have to embrace the change like we do with Apple products.
For the long run yes... but the transition period is the issue (though less so than with Xojo Core), because of the time it takes for new things to become stable with good performance across all the relevant platforms/OS versions supported.
Over the years I have learned to be weary of adopting newly implemented Xojo features because of potential bugs (when there is a significant amount of new code, there will likely will be some bugs initially that were missed) as well as performance issues (which may be platform specific) ...
It often takes several releases before things settle down.
I usually like to use the current version if possible, but until I know for sure the new features are OK, keeping code compatible with prior versions, even with new code, IMO is a good idea. Been burnt by not doing that in the past!