Slashdot Mirror
Delphi Renaissance
bongo69 writes "The TIOBE Programming Community Index is reporting that Delphi is experiencing a revival, this coincides with Borland recently releasing Delphi 2005 allowing users to target both win32 and .net platforms, which to some, is a welcome alternative for .net developers reluctant to use Microsoft Visual Studio or the opensource alternative SharpDevelop."
http://lazarus.freepascal.org/
.net but it does support windows linux and (just about) mac os x
ok so it doesn't support microsofts
Which makes it harder to write bad code. PLus, it's Borland. Borland, IMHO, writes better compilers than MS, and better libraries too.
Best Slashdot Co
The reason is only rarely technological. Borland's languages, from their Turbo- series onwards, were always significantly better than Microsoft's, but the market chooses tools based mainly on intertia and marketing. Microsoft advertised their way to dominance. Remember that so-called "Visual C/C++" was simply a wrapper around a few poor tools, with Visual Basic being the only component-based system, producing slow interpreted code, while for yearsBorland were producing fast compiled OO apps with Delphi.
There's a reason why some people dislike using MS tools and adore Borland's tools. Often, though, the developer does not have the say in such choices.
Sig for sale or rent. One previous user. Inquire within.
It's interesting to note that Novell is porting SharpDevelop to Mono.
See http://www.monodevelop.com/
Why is it so hot? Where am I going? What am I doing in this handbasket?
I used Delphi in my first programming job out of College. Initially I chuckled over the fact that it was Pascal, but eventually grew to learn and love Object Pascal.
It wasn't so much the language that made it great, it was the way the IDE, Debugger and compiler all played so nicely together. And yes, a C++ version was available as well. It was all of the ease of Visual Basic (and let's be honest, more) but without the bullshit of being stuck with some horrible language and the pain of trying to manage runtime distribution. Delphi compiled all dependencies into your binary, if you so wished. No more dll hell, at least, as far as your Delphi applications went.
It also had the relatively unheard of concept (at least in the windows world, at that time) of direct database access. You didn't have to mess with ODBC. You could write your corporate app for in-house use, and just let them change parameters in configuration screen, use them to connect to a database yourself. No freakin ODBC control panel applet to mess with. Nirvana, I tell you.
The VCL was another nice Borland item. It was their Visual Component Library (I think) and it was basically a wrapper around the standard Win32 controls/forms. Worked very well, and even made it over to linux with Kylix.
Unfortunately, Borland subscribed to the commodore school of marketing. The best place to see Borland adverts was in Borland targeted publications. The choir was already converted, but they never figured that out. That combined with typical MSFT tactics (hire away their best developers, give away competing products for a song) reduced Borland to a shell of it's former self. Now they exist by pumping out JBuilder updates every 8 months and living off that revenue gravy train.
I'm sure that there is going to be a bunch of Delphi bashing posts but Delphi was one of the first truly great object-oriented development environments (the other might be IBM's VisualAge). It allowed for rapid layout of forms with the power of OO components. And the language, although not loved by many, is consistent and just as powerful as Java. The component library was also second to none.
Delphi 2005 is really good value for money. For the same price as previous Delphi releases you get C#Builder, Delphi for Win32 and Delphi for .NET all in the same IDE. And Borland have enhanced the Win32 language too, they haven't just plugged it into the new IDE. So they show that they do actually care about the rest of us that do not believe that .NET really delivers that much benefit (and quite a few negatives actually) to end users.
.NET than VB6 to VB.NET.
Unlike Microsoft, Borland doesn't believe in pushing one platform. They have no specific platform agenda. When you buy Borland tools you know you're getting something that preserves your existing investments well- be they multiple platforms or simply your existing code base. For example, it is much easier to move code from Delphi for Win32 to Delphi for
That, and all the enhancements to the IDE such as refactoring, sync-edit, and MDA developement make Delphi 2005 a winner!
Microsoft Visual Studio is neither visual, nor is it a studio.
Discuss.
Weaselmancer
rediculous.
I would say that SharpDevelop is one of the best Free-As-In-Beer environments for you to learn how to write software in C#. Download the ECMA docs for the specification and try to write a few programs, and it works out pretty well. Certainly much better than trying to write something with a text editor and trying to compile by command-line when everything else you may have is done through a GUI environment. Get the C# How-to books if you don't have access to them anyway.
I happen to be a Delphi developer as well, and my #1 complaint about Sharp Develop is that they use the Visual Studio environment as the model for how user interaction should take place. It isn't bad, but moving between Delphi and #Develop can be a bit of a paradyme shift that is uncomfortable. For those who are VS fans, it would be a much more familiar environment (like the windowing stuff and location of help files, etc.)
The GUI end is a little bit clunky, but it is getting better. The first time I tried #Develop the menu editor was so buggy that it crashed the package. It has been showing significant improvement over time, and is remarkably stable now for some fairly serious GUI development. They bootstrapped the development with Visual Studio, but I believe that #Develop is self-compiling now (the editor can be edited with itself).
The part of getting it to work with Mono is a big deal, and the only real reason that it doesn't self-compile in Mono is because Mono lacks the GUI support necessary to get it to work. This is being worked on, and with #Develop getting stable there is now a larger push to get it working in Mono on Windows (and yes, Linux too). It would be terrific if you could get true cross-platform development going for a GPL'ed GUI development environment.
The person who originally wrote Turbo Pascal, and was also largely responsible for Delphi, led the C# design team.
Delphi is some kick-ass technology. It's a solid language, it compiles like *lightning* (essentially instaneous since ~1997), zero link times, and the provided libraries are great. Maybe not greater than .net, mind you, but an excellent alternative that was there many years earlier.
Delphi used to be the darling of the small developer and hobbyist programmer. Not only did you get all of the above benefits, but the standard edition was only $70. An absolutely brilliant alternative to Visual C++ and Visual Basic.
But then Borland quietly upped the price and changed the licensing. It used to be Standard for ~$70, Professional for ~$500, Enterprise for ~$1000. Then they changed it so the cheapest edition you could use in a commercial environment was $1000+. The only other version is Personal, around $100, but it is strictly license-bound to be used for learning the language and writing applications that other people don't use. Borland essentially made a one-line change to the license that forced programmers to jump to a product that costs 10x more. The result? Delphi web-sites and tutorials and hobbyist-written programs in Delphi dropped like a rock. Too bad, Borland.