<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I have been using 10.2 Tokyo now for 6 months or so.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The big shock was No BDE. I never realized how pervasive BDE actually was. I haven’t used any BDE components or 20 years, but never the less all of my existing
projects would not compile.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I had to make a decision, and in the end installed the optional BDE that comes with Tokyo. The main driver for that was that my last version (XE2) was such a
pile of crap that I couldn’t live with it any more.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The next challenge was my 3 X OEM component sets. The cost of upgrading these is a huge disincentive, and you have to think about this carefully.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If I put those two matters aside, the upgrade from XE2 to Tokyo was uneventful.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Really the main thing I have against Delphi, is the TCO. For me it’s about 4K NZD to upgrade including the 4 subscriptions. However, for building vertical applications
it’s still a country mile ahead of the rest if you use it the way it is intended to be used.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> delphi-bounces@listserver.123.net.nz [mailto:delphi-bounces@listserver.123.net.nz]
<b>On Behalf Of </b>Jeremy Coulter<br>
<b>Sent:</b> Thursday, 21 September 2017 3:23 PM<br>
<b>To:</b> NZ Borland Developers Group - Delphi List <delphi@listserver.123.net.nz><br>
<b>Subject:</b> Re: [DUG] Delphi 10.2 Tokyo ready for production?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">I have to agree. I have to make a very considered decision to upgrade because of the pain of having to install components. I think EMB. have come some way to help by introducing GetIt, but no all my component Devs are using it and there
there are the ones who are no longer around so I have to do it myself, and the same for my own components.<o:p></o:p></p>
<div>
<p class="MsoNormal">I look forward to having a "Personal" GetIt where we can specify the components we want to install therefore making Delphi upgrades easier.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Jeremy<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Sep 21, 2017 at 3:06 PM, Jan Bakuwel <<a href="mailto:jan.bakuwel@omiha.com" target="_blank">jan.bakuwel@omiha.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Hi Bevan,<br>
<br>
Thanks for your response!<br>
<br>
On 21/09/17 13:44, Bevan Edwards wrote:<br>
><br>
> Hi Jan,<br>
><br>
> I have had that headache of upgrading components from one RAD Studio<br>
> version to the next for some time now, which is why I'm always<br>
> hesitant to move projects to the latest version (although I am now on<br>
> the subscription model, so I download the updates and new versions as<br>
> they become available).<br>
><br>
> I mostly develop in C++Builder, but I think that the experience is the<br>
> same as with Delphi.<br>
><br>
> Migrating from XE3 to XE8 was a bit of a nightmare, but I eventually<br>
> completed that migration. I started on the migration from XE8 to RX<br>
> Seattle (I had to lookup the name to remind myself), but that was also<br>
> a bit of a mission, so I never completed it.<br>
><br>
> With 10.1 Berlin I found the migration much easier, but perhaps it was<br>
> because I had done part of the work in Seattle and also because I had<br>
> a bit more time to sort things out. But then moving to 10.2 Tokyo was<br>
> a Breeze (essentially everything I had done for Berlin more or less<br>
> just worked in Tokyo).<br>
><br>
> Going from XE5 to Tokyo is probably going to be a similar mountain of<br>
> work as what I experienced going from XE3 to XE8, but I think it's<br>
> well worth it.<br>
<br>
For the project I'm currently working on migrating it (to 10.2 Tokyo)<br>
should not pose too much trouble.<br>
<br>
<br>
> I now use Tokyo as my main development platform and have streamlined<br>
> the process of migrating old projects (replacing components which have<br>
> not been maintained or upgraded with the new versions).<br>
><br>
> I believe the annual subscription model is a necessity from XE8<br>
> onwards (unless you want to pay full price at each upgrade), but if<br>
> you're using it on a regular basis then it's worth the investment.<br>
<br>
Indeed.<br>
<br>
><br>
> In your situation, the question is whether it's worth the investment<br>
> for an occasional in-house developed project. The answer is probably<br>
> not, unless there is (a) some benefit in the target platforms offered<br>
> (over and above what is available in XE5), and (b) you will have the<br>
> time to put into overcoming the learning curve to use those new target<br>
> platforms (assuming it's different from what you've been doing).<br>
<br>
<br>
What prompted me to write this email is that while debugging for days I<br>
got the feeling I was working with a substandard product (XE5 +<br>
FireMonkey). Multithreading is a basic necessity in any responsive GUI<br>
application these days. And even if one would not create their own<br>
threads, threads are created by the RTL in many occasions. I wasn't too<br>
pleased finding out that - apparently - XE5 FireMonkey RTL wasn't tested<br>
well enough. I have the hope that things are much better in 10.2 Tokyo<br>
but then I've been bitten by that sort of thinking before.<br>
<br>
If by upgrading I would get a well tested production ready development<br>
platform for Windows, MacOS, iOS, Android and Linux, I'd be tempted to<br>
once more spend the money.<br>
<br>
><br>
> As far as I'm aware there is no Linux platform support in Tokyo, but<br>
> it is on their roadmap.<br>
<br>
There is, but as far as I can tell only in the Enterprise or Architect<br>
editions (<a href="https://www.code-partners.com/product/delphi" target="_blank">https://www.code-partners.com/product/delphi</a>)<br>
<br>
> I have played around with mobile applications in both Berlin and<br>
> Tokyo, but I haven't produced anything for use outside of my<br>
> development environment yet (too few hours in the day/week/month).<br>
> I have also not deployed any apps on MacOS yet (haven't needed to and<br>
> haven't had a Mac machine available, until recently).<br>
><br>
><br>
> I hope that helps - feel free to ask any further questions.<br>
<br>
It sure does, many thanks!<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
Jan<br>
<br>
_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@listserver.123.net.nz">delphi@listserver.123.net.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@listserver.123.net.nz">
delphi-request@listserver.123.net.nz</a> with Subject: unsubscribe<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>