Hi everyone, it’s been a while since I have been on the Xojo forum. I was looking at Xojo back in 2020, which seemed like a time of big change (and somewhat confusing deciphering the differences between old and new ways of getting things done - especially when starting out).
At the time, I ended up deciding on waiting out the updates to API 2, and checking Xojo out at a later date once the dust settled.
Looking at what has been accomplished with Xojo in the last couple of years seems very impressive. Congratulations to @Geoff_Perlman and the rest of the team (trying to catch up on posts, I did see that @Greg_O_Lone announced in February that he was leaving Xojo after many years, which was sad to see, but I am happy for him to get to start a new stage in his professional life). During this time, I also noticed that there was a price increase, but coming from a developer looking to switch to Xojo, I am fine with an increase in cost if it means a brighter and more stable future for Xojo.
In 2020, I was hesitant to switch from my familiar C# .NET and Python - but now I think I am ready to give it a good spin (though I don’t think I could ever truly leave Python haha). With these recent advances, and API compatibility between platforms, I am ready to try to make Xojo my primary development environment. I had been working with .NET Blazor since it was released, which is supposed to be a multi-platform environment sometime in the future with .NET Maui, but despite the hype, I question if will actually be anywhere near the level of capability that Xojo offers right now.
I may still use C# for gRPC services and Python for other web related tasks. Right now, I am trying to scour the Xojo forums in order to figure out what I should expect in regards to actual limitations with the Xojo platform. I don’t expect one tool to be the best at everything, and I am looking at Xojo mostly for front end work, while perhaps keeping backend services in C# or Python if that would work the best.
The idea of writing everything in one language does have appeal, and the effort put into tools like @Tim_Parnell Lifeboat look really nice, and gives me hope that perhaps Xojo on the server can be robust and scalable enough to replace some other battle tested web frameworks.
As a developer new to the platform, I would just like to know where the landmines are, so that I can simply avoid them, and concentrate on what Xojo does best - to avoid wasting a lot of time, when other tools that I already know how to use, would be a better fit. Of course I would prefer to be able to decrease complexity, working only in Xojo, but I am willing to augment Xojo with other languages if beneficial. Any guidance from seasoned Xojo devs would be helpful in providing some realistic expectations I can work from.
Anyway, hello again, and it is nice to be back!