ReKindling My Delphi Books

If you have ever questioned the value of filling out the Embarcadero developer survey, let me assure you it’s well worth your effort.  It provides EMB with valuable feedback, and even if you don’t like what they do with the information, you can’t complain unless you participate. Kind of like voting for your “favourite” politician (but I digress).  If you do participate, there is the chance of an unexpected benefit.

I got an email recently from Deanna Dames at EMB.  Apparently, I won an Amazon Kindle for filling out the developer survey.  Just wanted to say thanks EMB!  Now I can recycle all those Delphi books and put their PDFs on my kindle.

14 Responses to “ReKindling My Delphi Books”

  1. Bruce McGee Says:


    “you can’t complain unless you participate”

    Going by the public forums, it seems that some of them can.

    I’ve never understood why some people spend so much effort explaining why they can’t or won’t spend the same amount of effort or less to give feedback, fill out a survey, make a QC entry or even vote for one.

  2. Jolyon Smith Says:

    Perhaps those people have taken the time to fill out the survey(s) in the past and are fed up with the way that their views - often seemingly/empirically in the majority - are ignored.

    A bit like those people who get fed up when they are told to “Log it on QC”, because over the years they have filed numerous reports on QC and never see anything they mention getting fixed or improved, despite - in some cases - the QC entry being updated as if the item in question has been fixed when patently it hasn’t.

    It’s all a part of the same problem that has afflicted Borland/Inprise/DTG/Embarcadero over the years - the disconnect between the current owner of the Delphi IP and the community/users.

    I specifically excluded CodeGear from that list because in that brief time when CodeGear was in the ascendant, there looked to be a positive reconnect with the community. The Turbo’s were reinstated just prior to that era, and the roadmap seemed to be realigned once more with community expectations.

    Then CodeGear was sold back to Inpr[bksp][bksp][bksp][bksp] Embarcadero, “CodeGear” was quietly and unceremoniously dropped and forgotten and normal business was resumed with the same old management driving the product down old, familiar (and previously unsuccessful) paths once more.


  3. Larry Hengen Says:


    I agree that things could definitely be better in terms of EMB listening to their user base, and acting on QC items. I’ve had many QC items go uncommented, and unresolved, or get flagged with a Need More Info when it was really self explanatory and left to die.

    I could say the same thing about Apple today, and lots of other companies whose products I have used over the years. Ultimately they do listen to your cheque book, but it takes a long time.

    The sad truth of it is, that if you complain incessantly, you’re labelled a complainer and everything that comes out of your mouth at that point is ignored. If you want to make it better then do what you can, when you can, and as much as you can to that end, and be prepared that it may not be enough, but at least you tried. You only have a carrot and a stick. Use each in turn with equal enthusiasm….

  4. Bruce McGee Says:


    I have all the appreciation in the world for people who contribute constructively, and understand how frustrated some of them can get.

    On the other hand, some others remind me of a colleague who likes to sound off about the bad task bar context menu and some Borland support incident that wasn’t answered properly some time in 2005.

    In my experience, bug handling has improved, and one of the best ways to continue this trend is to keep letting them know what we want/need and what’s holding us up.

  5. Jolyon Smith Says:

    “In my experience, bug handling has improved, and one of the best ways to continue this trend is to keep letting them know what we want/need and what’s holding us up.”

    In my experience, bug handling is the same as it ever was … I can point to QC items logged years ago that remain unfixed and some that have a status that seem to indicate they have been fixed but haven’t been.

    So when I am told “Log it in QC”, my reaction is “Why the hell should I bother ?”

    With the exception of IDE bugs (and even then, Andrea Hausladen had a better record for fixing those given that he didn’t even have access to the source!) I can generally fix/work around bugs in the VCL.

    My time is demonstrably far better spent doing that than padding the QC database.

  6. Bruce McGee Says:

    Bugs that are marked as fixed but aren’t would be a huge problem. If you really can point to some, then they should definitely be brought to Embarcadero’s attention.

    If you want to go by anecdotal evidence, I suppose I could point to bugs (some old, some new) that have been fixed. I guess the real measure is whether they’re doing it better than they used to.

  7. Bertrand Person Says:

    A link to this survey would be appreciated.

  8. Warren P. Says:

    I have only praise for Embarcadero’s direction. They can’t listen to everybody all the time. I think it is a difficult call to balance things like “cross platform” versus “x64 on windows” timelines, and no matter which way they went on that, they were going to upset somebody.

    The core thing is to take what 90% of the users use 90% of the time, and keep making that better incrementally, and not just going after new R&D goals that destabilize everything else. If anything, Embarcadero understands that. Their compiler and IDE people are doing their level best, I believe, to keep building the product.


  9. Bruce McGee Says:

    Link to a survey published in May.

  10. Michael Thuma Says:

    @Warren. Right. Especially the x64 timeline - I think it was not an easy decision to get the right way - .net, x64 native, cross plattform.

    Today it is no longer a question to develop object pascal crossplattform under 32bit or 64bit - it is just a question when one can do it native. This is progress.

  11. Bertrand Person Says:

    @Bruce: Thanks!
    The survey is only a blank page now.
    I guess it’s over.

  12. Bruce McGee Says:


    When I follow the link, I get an introduction page with a Next button that takes me to the survey (FireFox). Not sure why you’re seeing a blank page.

  13. Bertrand Person Says:

    I get an introduction page with “Click here to participate in the survey” in the text. This is the only link I see. I do not see a Next button anywhere.

  14. Tim Del Chiaro Says:

    The survey has ended so I made a note about that on the EDN article.

    This was a study about general development attitudes and plans and not a way to gather feedback on Delphi or determine future direction for any specific product (which is done via the yearly survey from product management).

    The first set of results is published at We’ll post some more information on answers to other question areas and more detailed data from the answers in the coming weeks.

Leave a Reply