@Gijs R Appreciate the effort the team put into R2.
So do I.
@Paul R I'm guessing you don't have a million lines of API 1.0-based code to manage...
Most likely, we do.
And while I appreciate the start and idea of API 2, I consider this just a start. And hope Xojo will provide us further improvements to continue working with an existing codebase. On the one hand to continue with API 1 only (and get less "fuss" about what's not intended to use right now), on the other hand to better get an overview (improve Analyze Output) and provide safe migration helpers (e.g. select a whole "issue-block" such as
Label.Value, which will replace all at once as long as it's safe - that's what a global search&replace can't guarantee).
Feature Requests for all that are in place... let's see how much more productivity (and also "code safety") the next release will bring for those with existing codebases.
Currently, it's all nice and good for new projects or newly created code. So a good start. But having more productive ways for existing customers/projects/codebases is missing - which doesn't mean we won't get that ever. So I continue appreciating API 2. But won't use it for now myself. I wait a bit more to see what works and what no longer works, and until there are new features allowing to continue working productively with our projects.