Serge's Technology View

Talk about Technologies, Software Architecture and Management

Posts Tagged ‘tiburón’

Delphi 2009 beta: Installation improvements

Over the span of few weeks I have had “hot” conversation in public NG about speed of installation and that R&D team should do something about it.

Good news

For people who worried about future experience with installation of the Delphi 2009 – it is fast (or faster, since it is always comes to personal opinion). I have done several “fresh” installs, along with “on-top” installations. It did took me less then I spend downloading it over my 3Mb connection. Keep in mind a size and compare it to Visual Studio installation time and it start to look very good.

Not to be along with that statement there is other people’s opinion – Holger Flick posted last Saturday about his experience.

History

For many years, Delphi installation was created and maintained using InstallShield product line. It was based on it and IS Express edition was included in distribution for developers to use it. I am not sure how many people have actually used it, but it was there and it was free. Back in 2006

Newly formed CodeGear(TM) chooses InstallAware for delivering the newest versions of Delphi®, Delphi® for .NET, C++ Builder®, and C# Builder® tools. InstallAware Express is now bundled with CodeGear’s developer products as the installer tool of choice.

Let’s look at the possible reasons:

“Using InstallAware’s MSIcode, we have drastically reduced the need for creating custom plug-ins,” says Allen Bauer, Chief Scientist at CodeGear. “Our InstallAware setup dynamically defines the features and files to be installed. Instead of building, maintaining, and shipping separate installers for all the languages, IDEs, and product editions that we offer, we are now able to build and deliver a single install image. This has dramatically reduced our integration workload along with reducing our costs.”

“Electronic software delivery (ESD) will be playing a larger role in the way we deliver our products going forward. InstallAware will be powering our new ESD functionality in the Delphi and C++Builder products,” adds Michael Swindell, Vice President of Products at CodeGear. “We will be able to increase Internet delivery flexibility and performance providing customers with instant access to features based on electronic software purchases. Our goal is to make the user experience for both trial evaluations and electronic purchases as simple and flexible as possible. We evaluated a variety of installation and delivery technologies and InstallAware had the right features, performance, and technology for our requirements.”

Reality check

After initial release everyone had “suffer consequences”. Setup was much slower, updates could take substantial time to be applied. As a result, there was up until recently big “roar” to “toss” IA and return to “good old days”.

Alternatives

Aside from choosing to use batch file/XCOPY setup mode (can you imagine that this is still preferred way to deploy ASP applications?) let’s look at the alternatives for InstallAware (MSI).

  • InstallShield: recently acquired by Acresso. This is a target – “If your software targets Windows, InstallShield® is your solution.” – MSI. Long history with Borland/CodeGear and marketing/pricing/features may played the role in the decision of looking elsewhere for new deployment solutions.
  • InstallAnywhere - just to mention here and it is a product from the same company. In general it may be better positioned since supports not just Windows bit other platforms as well. Not a mainstream product for some time, but what could happen is that it will eventually merge with InstallShield taking best from both. At the time (2006) probably was not even considered to be a choice.
  • Wise installation Studio by Symantec – again Windows platform. – MSI and WinInstall. Product line had struggled for many years, was very non-trivial in maintenance and even though it did have potential, uncertainty of it existence at the time may played the role of not going with it.
  • InnoSetup - great product, native to Pascal/Delphi developers with its Pascal-like scripting language. But even though it is a great product, it may luck of some Enterprise features CodeGear was looking at the time highlighted above. Would it be faster? For sure. Would it lock the deployment to some of the “legacy” ways of doing so? Most likely. – WinInstall

Choice

Some of you will disagree with me on the need of standard ways of deployment, ability to automatically be certified for any future versions of Windows (Vista certification at the moment), common UI elements and interfaces… But reality is that it is that it is needed. User/System administrator/Company should be comfortable and familiar with the product deployment strategies and be able to do the same “that those other setups can do”. InstallAware gives just that. Yes, there is some hype in the air as it is with any product on the market, and yes there is a learning curve. Mind though, learning curve here more related to MSI technology itself, then to InstallAware implementation. Team has to have knowledge, desire, and  budget to properly implement requirements regardless of the platform they are using.

It my strong believe that what we have seen over last few years was a story how higher management decisions affect development rather then technology problems. Yes, I could be wrong, but after over a decade working with different deployment solutions, I think that we are in no worse situation with InstallAware then with any other product. With new management direction at CodeGear it may change, but improvements shown in latest installations for Delphi 2009 beta may finally let story rest in peace.

Update (Aug 28, 2008)

Last night I have had a chance to compare RAD Studio 2007 setup speed and RAD Studio 2009 speed once again. Impressive. 1 : 10 ratio. RAD Studio 2009 installs much faster.

From Inprise to Tiburón. Fall and rise of development tools.

First, if you were looking for information about Hyndai’s sporty compact, it is not about it.

CodeGear joined Embarcadero and finally is free to do what they suppose to do for many years now – develop the software for developers and not some few of many tools for IT management (there would be no problem there in general until development tools line start to degrade).

CodeGear extends the Borland legacy, but not in the way it was done last 8 years since the era of Inprise ALM movement.

Back in 2000, Dale L. Fuller, then president and CEO of Borland, said about going back to the roots and renaming from Inprise to Borland:

“The Borland name has always been synonymous with superior technology,” “We recognize the influence the Borland name has on customers, and we know this decision will strengthen our identification within our target markets.  The Borland name symbolizes a new start for the company, which has proven itself over the past eighteen months with two consecutive quarters of profitability.  As we continue our turnaround, the name change signifies our renewed commitment to customers, stockholders, employees and analysts.  Borland has always been well known for its ability to simplify complex technologies and the new name signals a return to the commitment to deliver superior technology that helps speed and ease the software development lifecycle.”

Promiss which never had a chance to be furfilled. “Software development lifecycle” took over the “developers, developers, developers” (Microsoft (c), this guy can motivate) moto which we used to associate Borland’s name with. It took long 10 years to fully realize potentials of the development tools market.

Now with CodeGear finally free form “Inprise” legacy (it is sad that we have lost good old name “Borland” in “Delphi”, but may be it is for the best.) we all looking forward to see a comeback of Delphi development platform, both as a language and as IDE, to get back its rightful place among modern development platforms.

We have a great tool which just need to return to the day light.

Do you want to know more about a new version? Read what people are saying about a new version, codename Tiburón. If you are not currently using it, give it a try. See what Delphi name was about for years.

Tiburón: Why Unicode IS important

There is a hot discussion brewing in public about importance of the Unicode support in upcoming version of Delphi (Tiburón). There are people who do not see it as something to spend time on in current Delphi situation and some who disagree with that.

Did you notice that word “Tiburón” is in Unicode?

Let’s come back in time December 2002 – Delphi VCL Controls for Win32 should support unicode – 4.89 rating, 359 votes. One of first from the dozens of QC reports asking to add Unicode into Delphi. Do not tell me it is not important for many people.

Is it too little too late? Could as well be, but it is better to finally have it and enjoy a feature which is now mandatory for any major development platform.

Keep in mind that Delphi (itself) was already “unicoded” storing string resources and source code as Unicode for some few versions. Full VCL/RTL conversion had never received much of the attention from upper management allowing Dev team actually work on the feature. Everything was about ALM those days. This time around it is different. Today Unicode one of the features which are critical for Delphi survival.

Yes, for many years we have learned how to deal with no support for Unicode in Delphi, but it is way around things, and not a solution. How many times was I asked – “why Delphi, being a modern language, still does not support Unicode?”. Well, I have had no reasonable answer.

Let look at the feature in question. Would it be important for US or even EU markets?

Yes, if you write an application which is used outside of your company’s building.
No, if you are running a home-only applications.

Let’s not go into discussion of dancing around the issue instead of solving the problem. Delphi applications do not exist by themselves, there are plenty of 3rd party API, data, code you need to interact and if they are in Unicode and your code cannot be native to the data, then you will encounter many things which you otherwise would not see in your “home” environment. Windows NT, XP, Vista has Unicode support. Being a programmer means one has to follow the main stream, not go against it. Otherwise you look as a white crow.

Now let’s come back to Tiburón. As a component vendor and Delphi programmer for many years, I would worry about such drastic change and impact it might have. But after having “converted” my code to have Unicode support by simply opening my projects in a new Delphi and recompiling gives me an assurance that work is done well by the CodeGear team.

Yes, let’s not idealize the situation, some modifications could be required, especially when Windows API functions are used. But even in this case, you most likely would get informed about the problem on the time of the compile, since you would be asked to adjust a few places in your code to use your string resources as Wide or ANSI strings specifically. Otherwise, your code would just run.

Did it worth the time and resources and is it a major thing for the release? YES. Remember it is a lot of work to make sure that everything is converted properly and working considering that there is a lot of dependencies between VCL code and underlying Windows API.

PS. And do not forget that Tiburón is not only about Unicode. Read all information about it as CG team is talking about new features.

So it began: Tiburón in the news – July 25, 2008

Now we finally can talk about a new version of RAD Studio - Tiburón.

Did you miss some of the posts? Check the list below for most comprehensive list of posts about upcomming Tiburon release.

Valid XHTML 1.0 Transitional  Valid CSS!