EMBT Surveys the Damage

If you’re an XE2 user you probably just got an email from DavidI with a link to a new SurveyMonkey survey EMBT has published aimed at XE2 users who have not upgraded to XE3.  One might think they are seeing few XE2 users upgrade to XE3 despite their “bonus” pack.  It’s a positive move on EMBT’s part, showing they are at least concerned with the situation.  Make sure to give them your opinion, including issues like this!

Tags:

13 Responses to “EMBT Surveys the Damage”

  1. David Heffernan Says:

    I’ve upgraded to XE3 and still got the e-mail. Left hand and right hand appear out of sync.

  2. Luigi D. Sandon Says:

    I’m a XE2 customer who didn’t upgrade but didn’t receive anything yet. Isn’t that survey a little too early, anyway? The times when Delphi developers rushed to each new version are gone - especially since new versions become stable after two-three service packs at least. Those who aren’t SA customers will wait a little, or skip whole versions if their are not compelling enough for their needs. I think I’ll skip XE3, we’re just rolled out in the past months our first 64 bit releases with XE2, not the right time now to add an upgrade.

  3. Michael Thuma Says:

    I have not received the survey, so I cannot comment on the questions asked. Assuming ‘the’ conclusion drawn would be correct. Of course it does make sense to ask the customer, best feedback you can get.

    They are satisfied with XE2 very likely and maybe don’t want migrate the existing projects. Consider many have more than 100 or more. XE2 was a synchronization point very likely because of 64-bit Windows support.

    Some will wait for the Mobile Studio, I am sure, and hope to get it for free;)

    From a European perspective I would say, lay the foundation for having less costs in the future today and upgrade + SA. I simply did, but last Thursday. Everyone can upgrade to RAD Studio as usual from Delphi too anytime anyway.

    XE3 is a candidate for a gold release. The Delphi version that does come in the year of a new Windows is a golden and the one after is a Platinum one. I think it does not make sense to miss this upgrade.

  4. Brett Graffin Says:

    After the hangover of Delphi upgrading from D2007 to XE2, I am personally exhausted. It literally took almost 9 months to get all the 3rd party components upgraded and/or migrated. Many components that I have been using for years had to be abandoned. Research, great expense, and time to make the migration complete for (3) major projects, and I am not even interested to taking another drink. From what I’ve seen on blog postings for XE3, I am sure it is wonderful. And it is something I probably would want. And the really funny thing is upgrading my Delphi is one of easiest and least expensive parts. It’s the 3rd party components that make each year’s upgrade a process of pulling a big bag of rocks uphill. The days of yearly updates are over for me, they will probably be every 2 releases now. My recommendation is do what they did with D2007 (probably hard to do these days because of all the crazy changes going on with mobile and cross platform), make each other release non-breaking with the VCL components. Definitely, would make it more viable to do the yearly upgrades.

  5. Tommaso Ercole Says:

    I have not received the survey, but I would have liked! I upgraded every single version since 2010 and I still stick with 2010. The compilers from 2010 are full of bugs and memory leaks and memory disalignments and every year I’m praying embarcadero to drop them (and pass to something else like LLVM) or spend one year to optimize JUST them.

    So if someone is having that link, I would like to click it and share my view with DavidI.

  6. ObjectMethodology.com Says:

    For me discounts are better incentive to buy than bundling. So, EMBT should send out emails to all who have any version of Delphi and haven’t purchased XE3.

  7. David I Says:

    David - regarding your comment “Left hand and right hand appear out of sync.” - I assure you that your characterization is not accurate. I used the registration database in an application that generated the SurveyMonkey mailing list. I also checked the file that was generated and cannot find your name or email in the list. I am not sure how you received the survey from SurveyMonkey unless you have multiple registration database entries with different registered products in different accounts. If you want me to track further, send me an email to davidi at embarcadero dot com and I can do some additional research.

  8. Jolyon Smith Says:

    They would certainly get a better return on that investment than constantly sending emails out to people who HAVE already upgraded.

    Really, the impression that Embarcadero seem intent on conveying is one of complete and utter incompetence.

  9. LDS Says:

    I’m an XE2 Ent customer who didn’t upgrade to XE3 and didn’t receive anything. Anyway, isn’t it a bit early to ask why one didn’t upgrade? The old days when developers rushed to buy the latest version are over since D8/D2005, Delphi is not the iPhone.
    Moreover when new releases are always buggy until at least a couple of updates people without an SA may wait a while and see what’s happen before upgrading, especially for releases that don’t add nothing really new.
    Anyway, we’ve just released our 64 bit apps this year using XE2, and we won’t change for a while, unless Emb releases an outstanding (and almost bug free) Delphi 64 bit.

  10. David I Says:

    “Damage” in the title of this blog post? Hmm - not here. I have been doing these surveys for the past 3 releases to make sure we are listening to our customers who haven’t moved forward yet to our latest releases. The information helps us focus on additional information, webinars and other things we can do to help all of our customers get the most out of our latest releases.

    The survey is very simple with only one real question, but more importantly also has two additional items where developers can tell us what 3rd party components they need for them to move forward and also an open ended area where customers can tell us anything else they want to help us help them.

    Since we launch new releases at the end of August and beginning of September, there are a lot of events and information to get everyone to try and but. At the same time, I’ve known for years that we can’t always give everyone all of the details, information, trainings, videos and other things to help them make the decision to purchase. Each year for the past few releases, I’ve also been reminded that developers are busy on projects and don’t always have to time to evaluate and purchase a product when it is releases.

    Each year - usually in the spring we also do larger whole customer base product surveys to help guide our roadmaps moving forward.

    The quick survey is a way to hear from customers what more information and technology they are looking for in order to move forward with our latest releases. Thanks to everyone who is taking part. We are listening (contrary to what some bloggers and commenters say).

    David I.

  11. Michael Thuma Says:

    After the first 3 days, can say XE3 is a great improvement over XE out of the box. Had a look at the Prof. Cannot comment on XE2 and the relative progress between the current release and it’s predecessor.

    Maybe the FMX is a good opportunity to be sparing with third-parties and use only those that would be a huge effort to implement on one’s own and economical from this perspective.

  12. Warren P. Says:

    @Brett : I hope that there might be some ways that Embarcadero could make it easier to move up from one version to another.

    I myself have often contemplated having my code in some kind of form that can “automatically” move up to the next version of Delphi. There are a variety of things in my way, not the least of which is the common practices that require a whole new set of component packages, in a whole new folder, per each version of delphi, for most component sets. Secondly there’s the common component vendor and opensource component practice of using single {$ifdef VER240} declarations. Each time you get a new version you have to copy and paste all the {$ifdef VER240} as version=version+10 {$ifdef VER250}.

    And then there’s the breakage due to compiler changes. Believe me, I understand. But I’ve gotten frightfully good at upgrading, as I’ve tracked Delphi versions within weeks of release, got all my stuff up, from 2009, to 2010, to XE, to XE2. There’s too much work involved in doing this, but I don’t think it’s fair to blame Embarcadero. Those of us who write third party components, and those of us who buy or use third party components, need to work to make the project structures we use easier to upgrade.

    A way to apply a configuration change to every project in a project group would save hours and days in my upgrade process. But of course, Embarcadero already added a configuration-settings scheme that doesn’t work very well, that actually gets in the way of this.

    It’s a HUGE problem and it’s in everybody’s best interest to make it easier to upgrade from one delphi version to another. Some people have gotten so upset about it that they refuse to use anything but built in components, because that prevents the package-hell issue each time you upgrade delphi versions.

    And then there are the people who really make themselves suffer, by electing to purchase binary only components. Some of those people are stuck forever on Delphi 5. Don’t be one of them, dearest readers.

    Warren

  13. TPersistent.com » Blog Archive » Falling through the Cracks Says:

    [...] my last post I was asked by a prominent EMBT team member why I titled the post the way I did.

Leave a Reply