I’m starting this “New Framework vs Class Framework”" discussion here, even though there’s another one on this forum, because the other one was supposed to be a poll, and I voted there. I’m coming at this as a FileMaker developer who switched to Xojo within the last couple years. So I’m not the seasoned Xojo developer that populates that other thread.
After successfully producing a Xojo Web app that has been running for over a year now in production for a real estate firm, I recently started rebuilding a very mature complex FileMaker Desktop app into a Xojo Web app, using the Classic Framework. It’s going very well, and I’m happy doing this. But now I hear (in that other thread) that the Classic Framework will most likely be replaced by the New Framework in some 5+ years. I have never used the New Framework.
Should I start converting this far-from-production project to one that uses the New Framework exclusively? That is, find every block of code in that project that could use the New Framework, and rewrite it using the New Framework? Here are my considerations:
If I wait until I have no choice, like some have suggested in that other thread, it would mean I would end up rewriting over 5 years of code at that point, instead of about 2 months of code currently.
But if I start the New Framework conversion now, I face the possibility that the New Framework ends up being a moving target in its implementation because of its frequently reported immature state, or it’s later abandoned by Xojo Inc.
I guess I could just wait a little longer and see how serious Xojo Inc is about this New Framework replacing the Classic Framework, so I end up rewriting, say, 6 months of code instead of 5 years of it.
I’m not looking for opinions as to what Xojo Inc should do with the New Framework. I’m just looking for suggestions as to what I should do with my current project, given the current state and status of the New Framework.