Hi Jan, I have had that headache of upgrading components from one RAD Studio version to the next for some time now, which is why I'm always hesitant to move projects to the latest version (although I am now on the subscription model, so I download the updates and new versions as they become available).
I mostly develop in C++Builder, but I think that the experience is the same as with Delphi. Migrating from XE3 to XE8 was a bit of a nightmare, but I eventually completed that migration. I started on the migration from XE8 to RX Seattle (I had to lookup the name to remind myself), but that was also a bit of a mission, so I never completed it. With 10.1 Berlin I found the migration much easier, but perhaps it was because I had done part of the work in Seattle and also because I had a bit more time to sort things out. But then moving to 10.2 Tokyo was a Breeze (essentially everything I had done for Berlin more or less just worked in Tokyo). Going from XE5 to Tokyo is probably going to be a similar mountain of work as what I experienced going from XE3 to XE8, but I think it's well worth it. I now use Tokyo as my main development platform and have streamlined the process of migrating old projects (replacing components which have not been maintained or upgraded with the new versions). I believe the annual subscription model is a necessity from XE8 onwards (unless you want to pay full price at each upgrade), but if you're using it on a regular basis then it's worth the investment. In your situation, the question is whether it's worth the investment for an occasional in-house developed project. The answer is probably not, unless there is (a) some benefit in the target platforms offered (over and above what is available in XE5), and (b) you will have the time to put into overcoming the learning curve to use those new target platforms (assuming it's different from what you've been doing). As far as I'm aware there is no Linux platform support in Tokyo, but it is on their roadmap. I have played around with mobile applications in both Berlin and Tokyo, but I haven't produced anything for use outside of my development environment yet (too few hours in the day/week/month). I have also not deployed any apps on MacOS yet (haven't needed to and haven't had a Mac machine available, until recently). I hope that helps - feel free to ask any further questions. Regards, Bevan On 21/09/2017 13:08, Jan Bakuwel wrote: > Greetings all, > > I know of course that by picking this subject I might draw some > criticism as it could be interpreted as implying that it might not be... > > I'm a one-man band only occasionally getting to develop an in-house > application with Delphi, so even though I would love to do more Delphi > development, it simply is not financially feasible to continuously > upgrade not only Delphi but also the various 3rd party component suites. > I'm sure this sounds familiar to at least some of you. > > I'm at that point (again) where I'm contemplating whether to request > funding to upgrade from XE5 to Tokyo 10.2 or not, just having spend a > fair amount of time debugging threading issues with the XE5 Firemonkey > RTL (no fun and only partly resolved). > > Being able to target Linux server is something I've longed for a long > time so that would be a bonus. Independent reviews of Delphi releases > are hard to find (I wonder why) so I'll ask here if there's anyone here > that would like to share their experience using Tokyo 10.2 for real > world applications deployed on Windows, MacOS, iOS, Android and/or Linux > server. > > Jan > > > > _______________________________________________ > NZ Borland Developers Group - Delphi mailing list > Post: [email protected] > Admin: http://delphi.org.nz/mailman/listinfo/delphi > Unsubscribe: send an email to [email protected] with > Subject: unsubscribe > _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
