Linked by Daniël Mantione on Mon 16th May 2005 18:38 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Actually, I'd say you're almost entirely wrong.
From my experience, a depressing amount of Windows applications are done in VB, happily followed by Delphi (Borland's proprietary Pascal variant), Visual C++ and then a hodge podge of different things, including Java.
Until C# came along, Delphi was by far the nicest platform available for developing Windows applications. It made for easy RAD development but also allowed you go right down to the metal (Delphi has pointers, but it makes life easy enough that you just don't need to use them that often).
I use Delphi at work, and it's a lovely language. There are some issues, like the sparseness of the library in comparison with Java and C#, and the fact that Interfaces force memory management, but otherwise it's very nice indeed. In fact, most of the advances in Java (String primitives, single inheritance with multiple interfaces, object hierarchy rooted with a built-in Object type, easy RTTI, etc.) and C# (delegates, properties, indexed properties) are straight out of Borland's Delphi.
I've never tried any other Pascal implementation, I'd be interested to see how this stacks up.