Make the alternative look worse than it really is. In fact, go one better – don’t make it look worse, just describe it as being worse. Some may consider it unfair to pick on one specific post, but I am increasingly disappointed with how the SVN integration in the new RAD Studio XE is being hailed as some great new addition to the IDE and don’t think it’s fair to paint it in such flattering shades without doing a fair comparison.
In the linked blog post, there is a set of “oh look how clunky it used to be” steps describing how you would previously have performed a check-out from SVN prior to opening a project or file when working with RAD Studio.
Except for one thing: The steps described are unnecessarily cumbersome and make a reference to having to do task switching.
There is no need to do any task switching with TortoiseSVN and the RAD Studio IDE. The steps are simply:
- File -> Open (from within the IDE)
- In the file open dialog right-click : SVN Checkout (or Tortoise -> SVN Checkout if you really can’t be bothered to configure your explorer Tortoise context menu)
- Wait for SVN
- Navigate to and select project to open
No task switching and really not much different from the integration.
Well, actually there is one notable difference…. with the integration if you go to “Open from Version Control” and then find that you already have the required files checked-out you have to back-out from the Version Control specific operation you erroneously embarked upon.
With “vanilla” Tortoise there is less chance of running down that blind alley… you will either open the file you need or realise you need to check out from SVN first, and you can do both and/or either from the regular old File->Open dialog without having to switch modes, let alone tasks.
Oh but that’s not fair, this is only one aspect of the integration!
True, but it’s also the one and only aspect of the integration addressed by the blog post that I am referencing. Sauce for the goose.
People keep criticising me for complaining, but if there are benefits and Great New Things™ in a release then for pity’s sake can’t we find some to talk about instead of having to mis-respresent the alternatives (deliberately or otherwise, perhaps through simply being unaware) to try make the new features look better than they are?
It is surely especially important to have something genuinely positive to focus on given the great disappointment of not seeing delivery on expectations set by the previous roadmap?
(I can’t comment on other things that are in XE that others are not perhaps talking about because I don’t have access to XE yet – I wish I did. I am sure there must be something valid in there to be praising)
Comments are now closed.