This post is triggered by a CodeGear newsgroup thread.
RemObjects is running Chrome well. This pure Pascal for .NET compiler and related Visual Studio add ins really show why Pascal is not dying even if .NET and C# is there. Because Chrome 1 and Delphi 8 came nearly the same time, a simple comparison can reveal why RemObjects is bit of lucky over Borland/CodeGear.
In the past, if you need to sell a compiler, you need to sell it with a good IDE. This rule is setup by Borland with its Turbo Pascal, but Borland failed to match it with Delphi 8 for .NET/Delphi 2005/2006 (lack of resources). But how did RemObjects come through while it had nothing at all? The marriage of Chrome to Visual Studio really saves RemObjects at last even though at first selling Chrome to Visual Studio owners is not that easy.
We cannot easily draw a conclusion that Visual Studio contains more interesting features than Galileo (Borland Developer Studio), but VS is more stable and extensible. Thus, RemObjects gets rid of IDE nightmares (although headaches are unavoidable because VS source code is not that open like Eclipse). Now Visual Studio Shell is out there, so maybe RemObjects will get out of Visual Studio bundle, and starts to build a Chrome Studio some day.
RemObjects adopts to a subscription based model much earlier than Borland/CodeGear who is still fighting to get there. Who buys Chrome today can receive later update easily, even bundled Visual Studio update is available. This kind of offer can strongly inspire the users and increase loyalty.
Borland used an out-of-date model for so long and failed to deliver extra values to its loyal users, so when new technology was coming, its user base crushed. Even now, CodeGear cannot easily get rid of the clouds and mists. People who fear of “I will fix this in the new version” cannot trust CodeGear naturally.
I’d like to say in fact CodeGear tries its best to improve the experience now. Delphi 2007 is a good example. Even though the installation experience is still far from optimal, we get update all over the year which not only fix bugs but also deliver new features (like Blackfish SQL). A funny thing is that there are so many updates so it is hard to name them in numbers (numbers mess things up this time like Delphi 2007 Update 3 and Release 2), so for the first time we get something called December Update.
Old languages like Pascal need new features just like new languages like Java and C#. But Borland/CodeGear lost so many gurus along the path (Andres, Chuck, and Danny), so it is really hard to bring something new and useful in every release (generics is the best feature in Delphi 2007 for .NET). Also maintaining two compilers is not easy.
RemObjects is lucky that Marc Hoffman is such a nice leader, so some features added to Chrome is really cool (like design by contract). And building Chrome on .NET is much easier (than maintaining two compilers for two platforms).
Chrome always releases something free so you can touch (free compiler and runtime). Even though at first Chrome was full of issues too, it grows up and build up a user base. When Chrome 1 targets Mono, I doubted whether RemObjects can enhance that field of support and now Chrome officially supports Mono and targets Mac OSX with an interesting idea of coding in Visual Studio. The continuity in roadmap clears doubts.
But Borland kept losing users by messing up with its roadmap. Sometimes the trial edition is not up-to-date (Delphi 2005 and 2006) which may lead users to the wrong conclusion. Wish CodeGear can focus on the current roadmap which is still promising and meets major voice and deliver something as perfect as possible in 2008.
Yesterday I joined a fierce discussion on CodeGear newsgroup about whether RemObjects should acquire CodeGear Delphi. The idea was so original but reflected the truth that some users were still doubting CodeGear’s future.
RemObjects’ way may not be clonable because time goes by. However, because so many people still care about CodeGear, Delphi still has some hope.