Comments for Borland Delphi Update - September 2005http://dn.codegear.com/article/333032008-12-01T19:46:43-08:00Borland Delphi Update - September 2005james owenhttp://threads.codegear.com/threads/threads.exe/userall?commentid=38751http://threads.codegear.com/threads/threads.exe/view?commentid=387512005-11-15T16:35:59-08:002005-11-15T16:35:59-08:00Borland Delphi Update - September 2005Tue 11/15/2005 7:26 pm. I was pleased to hear about the new CEO; good luck. The "Borland Delphi Update - September 2005" would be OK if Delphi/Borland were a thriving product/company. To the contrary, I think it would be fair to say that many developers perceive Delphi/Borland as in trouble (geez was I right; I just read the other comments!).So you should try explaining how that's going to change. I am a Delphi/Kylix programmer; for Windows I use Delphi 5 (standard) by preference, and I stopped upgrading at Delphi 7, because of the quality deterioration, mostly bugs in the IDE. So here're some questions:1. I've appreciated the free "personal" versions of Delphi that have popped-up from time to time, but I still don't understand why we can't have $100 standard versions anymore. I just don't get it; I know you want expensive overhead-paying pro and insane millionaire editions, but what benefit do you derive from *not* having the stripped-down $100 version? Do you really think many customers are saying, "oh shucks they don't have the $100 copy, guess I'll spring for the $400 one"? No, we don't; we just keep using the old one.2. I am disenchanted by the .NET stampede. It's my impression Microsoft undertook this whole thing because they were frightened by Linux and its armies of scripting languages -- which do produce amazing results, to be sure -- and while many applications probably won't suffer at all shifting from compiled to interpreted code, others will. ... An obvious example: when is the .NET version of Microsoft office showing up? ... In any case, I never understood how Borland expected to compete with Microsoft on this basis: only a Delphi fanatic is going to choose Delphi over Visual Studio ... That is, by emphasizing .NET, you discourage new purchases -- and probably many Delphi loyalists also. So why not emphasize the compiled Win32 nature of the product more? Of course I can't guarantee you'll get rich that way, but I can't understand why *anyone* would bet on the .NET-everywhere Delphi.... Ok, that's two questions. Notice I didn't whine about Kylix; you tried, they didn't buy it, game over.-- best wishesj.g. owen * * * * * * * * * * * * * * * * * * *web: http://owenlabs.home.att.net/also: http://owen_labs.home.att.net/rant7.htm#kylixemail: owen_bda4@yahoo.com* * * * * * * * * * * * * * * * * * * * * * * *Borland Delphi Update - September 2005Robert Grindstaffhttp://threads.codegear.com/threads/threads.exe/userall?commentid=38706http://threads.codegear.com/threads/threads.exe/view?commentid=387062005-10-22T08:18:40-07:002005-10-22T08:18:40-07:00Borland Delphi Update - September 2005I agree with you. I asked my boss for Delphi 8 and got it. This is a product that should never have been marketed. I asked for Delphi 2005 Enterprise, thinking the problems would have been fixed, and got it... I don't have the nerve to now go to my boss and ask for VB.NET. Today is Saturday and instead of sitting in my kayak with a flyrod in my hand, I am sitting in my office trying to step my way through the bugs of deploying an asp.net app after installing update 2. re: Borland Delphi Update - September 2005Christian Elferthttp://threads.codegear.com/threads/threads.exe/userall?commentid=38694http://threads.codegear.com/threads/threads.exe/view?commentid=386942005-10-04T18:15:37-07:002005-10-04T18:15:37-07:00re: Borland Delphi Update - September 2005Probably there is a chance for Delphi: make it OpenSource and merge it with Lazarus and Mono. This would introduce a huge community-boost-effect for Delphi(.NET)Borland Delphi Update - September 2005Christian Elferthttp://threads.codegear.com/threads/threads.exe/userall?commentid=38693http://threads.codegear.com/threads/threads.exe/view?commentid=386932005-10-04T18:07:12-07:002005-10-04T18:07:12-07:00Borland Delphi Update - September 2005Regarding these quality initiatives for Delphi ...You say:" all designed to deliver the superior quality that our customers expect and demand".Come on, be honest. The Delphi 2005-IDE is still too buggy for using it in larger projects. The Idea behind is great, the functionality is great too, but if its not stable it makes no sense in using it. And i really would like to us it instead of Delphi7.I beg all of you on my knees, make an IDE-feature cut and make it stable! With Regards,ChristianBorland Delphi Update - September 2005Craven Weaselhttp://threads.codegear.com/threads/threads.exe/userall?commentid=38676http://threads.codegear.com/threads/threads.exe/view?commentid=386762005-09-24T14:58:30-07:002005-09-24T14:58:30-07:00Borland Delphi Update - September 2005Q. Can you tell us Borland's plans for Delphi's future, without talking about ALM and Java?re: Borland Delphi Update - September 2005Pedro Pimentelhttp://threads.codegear.com/threads/threads.exe/userall?commentid=38668http://threads.codegear.com/threads/threads.exe/view?commentid=386682005-09-22T10:17:53-07:002005-09-22T10:17:53-07:00re: Borland Delphi Update - September 2005The difference? Borland is known to me and hundreds of developers here for their high quality and productive IDE callen Delphi, not for C++Builder or JBuilder, or any development decoration (versions control, UML modeling). Of course, that was even version 7, using BDE or ADO for data connectivity.But since they released Delphi 8 and Delphi 2005, everybody has lost the hope in Borland as a IDE developer. For that reason the Delphi developers are turning to VS.NET for web application development, and keep Delphi 7 for desktop GUI applications.Delphi 2005 has a lot of cool features that I like, but everything is so buggy. So, I WANT A STABLE IDE BACK!re: Borland Delphi Update - September 2005C Johnsonhttp://threads.codegear.com/threads/threads.exe/userall?commentid=38662http://threads.codegear.com/threads/threads.exe/view?commentid=386622005-09-15T15:06:25-07:002005-09-15T15:06:25-07:00re: Borland Delphi Update - September 2005Check out the newest VS 2005 offerings and something called LINQ (currently in development for the next VS, but VERY VERY VERY cool technology!)True, you'll have to work in C# or VB.NET (a real language, not a VB scripting error), but I think you'll find C# an easy switch (esp. compared to moving to C++)re: Borland Delphi Update - September 2005C Johnsonhttp://threads.codegear.com/threads/threads.exe/userall?commentid=38661http://threads.codegear.com/threads/threads.exe/view?commentid=386612005-09-15T15:04:09-07:002005-09-15T15:04:09-07:00re: Borland Delphi Update - September 2005Seriously, how is that any different that the Win32 based IDE efforts of past? The delphi IDE has always been the bane of Delphi developers every since V3 came out.re: Borland Delphi Update - September 2005C Johnsonhttp://threads.codegear.com/threads/threads.exe/userall?commentid=38660http://threads.codegear.com/threads/threads.exe/view?commentid=386602005-09-15T15:03:01-07:002005-09-15T15:03:01-07:00re: Borland Delphi Update - September 2005Who told you that dotNet isn't native code? Both MS and Mono's engines have JIT compilers which result in native code.If you want to avoid the JIT stage, you can even pre-JIT applications directly to native code and run the pre-JITed images instead.re: Borland Delphi Update - September 2005Jim McKeethhttp://threads.codegear.com/threads/threads.exe/userall?commentid=38659http://threads.codegear.com/threads/threads.exe/view?commentid=386592005-09-15T09:31:21-07:002005-09-15T09:31:21-07:00re: Borland Delphi Update - September 2005x64 may be future of native development, but .NET is the future of Windows development, and thanks to Mono it is also the future of Linux development. It is like a 10 to 1 ratio of lines of code written in a managed / scripting language vs. a native one. Sure we see games, operating systems and databases written in native languages, but in the grand scheme of enterprise application development you see very little any more. In 5 years we will see a whole lot less native development.