[Estimated Reading Time: 7 minutes]

I imagine the news has spread like wildfire – the Delphi 2009 Trial Edition is now available for download!  I got me one, and these are my initial impressions.

1. The Installation

The installer itself is a small downloader stub, so the initial download is very quick.  During installation of course it then needs to download the necessary bits and pieces so actual installation time will vary according to your network connection and presumably the load on the download servers.

Once downloaded the files appear to be cached in a user specified location, so no need to go digging around to find those files later.  Subsequent installs/reinstalls should therefore be much quicker, and I’m guessing it is the speed of these installs that is said to be much improved over Delphi 2007)

The documentation is installed (and downloaded) separately, which also contributes significantly to the reduced installation time of the product itself (if you ignore the time to install the help).

Sadly it’s difficult to find anything complimentary to say about the appearance of the installer itself.  The actual installer screens are the slate grey affairs that I seem to recall from installing the 2006 trial, but there is a red/white/blue motif running through them and in the splash panels, that is carried over from the initial, rather crude and uninspired (and uninspiring) install front end.

Reactions to the installer artwork that I have seen have ranged from

“Oh.  Is that it?” to “What the hell is that?  Sheesh.”

Of course, it’s only the installer and it’s only graphics for crying out loud, but first impressions last, or so they say, and I can’t help but feel that a hugely important release such as this deserved a little more pampering on this front.

2. Gentlefolk – Start Your Engines

Cold start: 30 seconds, subsequent restarts: 8-10 seconds

That’s not too shabby, but still that first cold start is a lumbering affair – it took 10 seconds even for the splash screen to appear!

By comparison Delphi 7 on the same machine is up and running from a cold start in less time than it took Delphi 2009 to show it’s splash screen (9 seconds), and restarts are virtually instantaneous (1-2 seconds).

And yes, that is starting RAD Studio with only the Delphi personality.

3. A Stroll Around the IDE

The default IDE configuration will be instantly familiar to BDS or Delphi 2007 users I imagine, and so of course to Visual Studio users.  For those coming from earlier Delphi versions the usual culture shock will hit them.

You can of course get almost back to a less Visual Studio’y IDE configuration but that still involves tinkering with a number of options (and you still can’t get the palette quite the same, but let’s not go there).

I do wonder why CodeGear don’t provide a one-click option for this during installation to allow the user to choose a default IDE configuration for those coming from their own, admittedly older, products.  It’s almost as if they are contractually obliged to someone, somewhere to try to coerce us into getting used to the Visual Studio look and feel, and only begrudgingly offer the undocked mode (which ironically I expect to see Visual Studio adopt, or similar, with the recent indications that future versions will be better suited to multiple monitors, which was always the ace in the undocked IDE’s hole).

4. A Disappointing Realisation

QC #2134 remains resolutely UNaddressed.

It surely cannot be beyond the capabilities of CodeGear to devise some means for a new installation of a new version of a Delphi IDE to determine that “Oh, look, this user has a previous installation of an older version of Delphi” and at least OFFER to import some or all of the IDE configuration.

Grid settings, editor settings, font, syntax highlighting, etc etc, ALL have to be setup ALL over again.

QC #2134 was reported 6 years almost to the day and 6 versions ago, and I’m certain it was on people mind’s before even then.

5. Project Options – A Silk Purse Or A Sows Ear?

There is no way to avoid it – the changes to the Project Options dialog are a mis-step.  It simply defies reason to consider the changes an “improvement”.

Quite apart from the mixing of On/Off and True/False terms for boolean state options, either of these and the gulf of white space that now exists between the label of some option and it’s current setting and the need to read words to determine state are giant leaps backwards in terms of practical usability, and having all options listed uniformly and vertically is not an improvement – it  makes it harder to quickly locate an option when wishing to set or alter it’s state.

Previously, once you learned where on the dialog each group of options were located (it didn’t take long), you could instantly find them.  You didn’t have to read the caption of each group box when you were looking for the Range Checks setting.  Runtime Errors.  Top right.  Top checkbox on or off?  Done.  Now though you have to scroll up and down a visually indistinct listing of words where it is only the words that distinguish between each group of things, so you do now have to read them to find the Runtime Errors section, then read the labels of the errors, then scan across the chasm of white space and read True or False.

And that long, long list of options also now requires that the dialog be resizable – never mind any new options, the dialog now does not show even all the old options that it previously could at it’s default size.

But it sure do look pretty, don’t it?

I suspect that this change was in fact driven primarily by the wish to be able to reflect “inherited” project options now that configuration sets can be “derived” from others.  I haven’t yet done so but I’m sure I could have devised a much more user friendly UI for this functionality.

The visualisation of the relationships between different these option sets (which as far as I can tell are different again from the configuration sets also supported) is also not at all intuitive to me.  It may be clear enough if you sit and study the UI long enough, but frankly this whole area is downright confusing, and I really don’t think it needed to be.

It also does not seem to be possible to create additional option sets.  There is Base and from Base are derived Debug and Release.  That’s it.  You cannot add any others as far as I can tell.

Oh, just in case you were confused (actually, trust me, you will be) – the “Directories and Conditionals” node is not actually the “Directories and Conditionals” settings you know from previous Delphi Project Options dialogs.  No, those “Directories and Conditionals” are all new and refer to these settings for the “Resource Compiler”.  The “Delphi Compiler” has it’s own “Directories and Conditionals”.  Oh no, wait.  It doesn’t.  The Delphi Compiler directories and conditionals are on the, um, “Delphi Compiler” node itself.

And while on the subject of the nodes, I simply cannot fathom why Forms and Version Info are not leaf nodes underneath the Application node or why there is no “Package” or “Library” node for projects of those types.

New and different is fine – one must accept a period of readjustment.  But there are problems of clarity, consistency and basic usability in this dialog that I fear will prove difficult to ever get used to and be a constant thorn in the Delphi developer’s side.

6. And Be Snappy About it

On a more positive note the IDE overall feels much faster than I remember BDS 2006 or 2007 trials being.

There is still a noticeable pause when accessing IDE dialogs that is simply not there in Delphi 7, where dialogs snap into existence almost before you’ve finished clicking the relevant menu item, but the pauses in Delphi 2009 though noticeable are nowhere near as teeth grindingly painful as they were in BDS 2006 and Delphi 2007.

7. So Much To See, So Little Time

Of course, I’ve not even started to scratch the surface with Delphi 2009 yet.  Some of the new controls look interesting and fun and I look forward to exploring the new language features and assessing the impact of Unicode on some of my stuff.

But here’s where I see a HUGE problem with this Trial.

14-Days is all you get to road-test this puppy.  14-Days.  One-Four.  Fourteen.

How anyone at CodeGear reasonably expects anyone to be able to seriously evaluate this release in such a ridiculously short period of time beggars belief.  I only hope that I can find the time amongst my day-to-day work and personal committments to do some serious evaluation.

Which brings me to another problem.  There is no chance what-so-ever that I am likely to consider an Enterprise license, let alone Architect.  I am a Professional SKU customer or not at all.

Having to wade through an Architect SKU, referring to data sheets and feature matrices to determine what things I would get were I to purchase a Professional license, and what things I would not, is going to be a real pain.

There should at the very least be a Professional Trial, separate from Architect.

It’s not as if I can take my time over it.  14 days remember.

Which reminds me…. I haven’t got time to sit here blogging about it.

The clock is ticking!

17 thoughts on “Delphi 2009 Trial – First Impressions”

  1. I Agree. 14 Days is not enough. The longest trial software in the world that I know is Windows 2008. It’s trial for 8 month. And the standard trial is 30 days. Strange think about 14 days, may be they finish this project @ 2 PM? The address is of the project manager is number 14, or live at 14nd street? Just irregular.

  2. Fourteen days is indeed ridiculously short and after that time you sit with unusable scrap (hundreds of megabytes of never-functioning software again!). I’d like to see an EXPLORER edition or an EXPRESS edition with some limitation on the license or functionality. Regarding this issue, Microsoft did a good job by making EXPRESS edition of their development tools, so that everyone can evaluate the product as their hearts’ contents! CodeGear also should go in that direction and two flies should be caught in one sweep:

    a. More people get acquinted with Delphi/BCB (I still find the price abnormally high compared with competing products)
    b. For pirates the product will be far less interesting (Due to the high proces pirates are motivated to do naughty things…)

    Codegear can also think about other trial modes:

    – Nag screens upon application entry and exit
    – Watermark in executables (DLL, EXE, OCX)
    – EXPLORER mode like Turbo 2006 editions

  3. Couldn’t you run the trial in a VM where time only ticked when the VM is actually active?

  4. BTW, your server gives ‘Internal error 500’ if I give an email adress of the type “i.rather@not”. That’s a bit harsh…

  5. A bit off topic, but in response to http://delphixtreme.com/wordpress/?p=22 now would be the perfect time to release Smoketest:)

    I *love* object pascal (or delphi language or whatever you’d like to call it) and I do hope this release succeeds, because the alternative is C# or java (blah all the {}).

  6. Thanks for taking the time for putting this “quick view” of D2009 together. You made some valid points, but I do wish you had thrown in more positive points about the IDE.

    I know many hate the newer Delphis because they believe it’s a copy of Visual Studio. If it helps anyone cope with this phobia, you can think of the newer IDEs as a copy of the Eclipse IDE. There are a number of visual similarities with that IDE too.

  7. As a PAID SA customer… The more I read about you using an already available “Trial Edition” the more it angers me that I have not received any info to download/install my already paid for full version… very frustrating!!

  8. You can create your own option sets. Right-click on the Build Configurations. I can’t remember if it was Nick or David I, but someone showed it off in one of the online demos.

    As for the trial period, I agree that it’s too short. I’d rather see something like 45 or 60 days.

  9. Another poll suggestion.

    What Delphi SKU do you use regularly?
    – Architect
    – Enterprise
    – Professional (includes Turbo professional?)
    – Personal/Turbo explorer
    – None

  10. @Anders – I’m not sure if that internal error was related to the invalid email addy or just a coincidence (this post has attracted a lot of traffic and my site doesn’t seem to cope well with high volumes, although whether that’s a problem with WordPress or my hosting provider I don’t know). Thanks for the heads-up though. I’ll try to keep an eye on it.

    I’m not sure if the VM idea will work. Unless things have changed the Trial clock starts ticking from the day you request your trial activation serial #, not the day you actually install the trial. Although I suppose tinkering with the VM system clock would be less disruptive than tinkering with the host machine clock (assuming that the trial expiry trigger can be so easily fooled).

    @Rick – As I understand it, the Trial Edition can be “upgraded” to a full installation simply by providing an appropriate license key. I don’t know how SA works – but if you can get your key before you get your official download, but it might be worth pursuing.

    @Bruce – thanks for the poll suggestion. And apologies – one of your previous comments on this weeks polls got accidentally deleted when I was deleting a rather large number of spam comments (why auto insurance sites want to link to my blog I’ll never fathom!).

    I’ve found now that you can create additional configurations via the Configuration Manager, but only for specific projects. Yet when editing a specific Project’s Options you do not seem able to add new configurations, um options, and you cannot create additional default options.

    “Configurations”, “Options” – I still maintain that this whole area is unnecessarily complicated and confusing.

    @Kyle – Yes I was aware that a lot of what I had to say – in terms of word count at least – was negative. Unfortunately there is always more to be said about negative points, not least because they really should be substantiated so that others can understand why I consider them negative – they may not have the same priorities or concerns, so can then decide to ignore my “complaint” if they wish.

    Positive observations are – ime – less likely to be picked apart and dissected, but there were some of those too!


    I confidently expect to have a lot more positive things to say when I get deeper into the new VCL components and language changes.


    As far as IDE “phobia” goes, I don’t think the fact that Eclipse is also Visual Studio-like helps much if/when the problem is that the Visual Studio-style is what is disliked, not the fact that it is Visual Studio.

    Interestingly, even among people I know who use Visual Studio, many of them don’t particularly like it. They like the features and functionality, but not necessarily the IDE itself.

  11. 14 days?
    GREAT !!!
    That means, we should get some service-pack pretty soon: CodeGear do not want to have so many “unpatched” trials on work for such a long time. Reducing trial period avoids this (potentially high-risk) situation.

    I don’t know about any company to update to D2009 before any service-pack is out.

    Though, most of the “2009 budgets” (ruling investments i.e. update strategies) are to be approved until end of November.

    And there’s also the “Christmas-gift” business ahead:
    after 14 days trials, a frustrated developer could think about asking Santa to kindly provide him with a full license. 🙂

  12. thank you for posting this very good review.
    Indeed, embarcadero/cg engineers should correct some of the older issues, or have a code contest do the same, rather than filling blogs with information.

  13. “I know many hate the newer Delphis because they believe it’s a copy of Visual Studio. If it helps anyone cope with this phobia, you can think of the newer IDEs as a copy of the Eclipse IDE. There are a number of visual similarities with that IDE too.”

    It doesn’t for me, I don’t like the VS IDE and eclipse is even worse!

    Just let me have my palette a la D7, its not sooo hard now is it????

  14. What a very poor review.

    As a developer, I’m primarily interested in the IDE for reliability, ease of use and speed. You already told me it’s FASTER than 2007 (I use 2007 and that is FAST). What is D2009 like in daily use?

    Installation, dock/undock and project option issues are not a prime concern.

    Please import your D2007 apps, use 2009 for a couple of weeks and then write a usability review from the developer perspective.

    Better still, do the same with Visual Studio and then do a comparison.

  15. First of all it wasn’t a review and you shouldn’t have read it as such. It was – as the post title made very clear – a summary of first impressions, written a day or so after the trial was available.

    If my first impressions didn’t cover all the aspects of interest to you, why not download the trial yourself and conduct those investigations you feel most relevant to you?


    I might yet write a more comprehensive review, but that will only be possible if/when I’ve used it intensively for a meaningful period.

  16. Very good article.

    I am still on D7 using XP but Windows 7 will be the death of D7. The new IDE will be culture shock but if I am going to be able to program in the future I will have to upgrade at some point. Will just put it off as long as possible.

    Thanks Again

Comments are closed.