Why delphi users/developers/programmers switch to delphi 2010/XE?

I'm glad reading it.

Ahah,

>>Code does run faster. The compiler has been optimized. One personal experience is a compression program I had when I used Delphi 7 ran much faster when compiled with Delphi 2009

But Why it runs faster?

Now that conflicts to the other comments.

It runs faster because the compiler that generates the bytecode has changed. Now, not all code will benefit, but some definitely will.

Systan,

Not all code run faster only some. I believe this one is due to code using the x64 platform features thus making it more faster than the x32 platform which is used by the Delphi 7. Of course a PC using the x64 technology does outperform a PC running only at x32.

Do you now have ideas? If yes, then please select the experts that contribute to your solution.

>>I believe this one is due to code using the x64 platform features thus making it more faster than the x32 platform which is used by the Delphi 7. Of course a PC using the x64 technology does outperform a PC running only at x32.

I believe because of the memory, how 64bit handles it.


Expert [Epasquiers] comment about 64bit;
About 64 bit : there is a lot of talks about Delphi not supporting 64 bits. I'm really wondering if more than 5% of the talkers knows how small an issue that is. There is absolutely NO problems with 32 bits applications running in 64bits system. Quite the opposite in fact. I'm running Delphi 5,7 & 2007 on Vista 64, and all my applications compile &  works fine.

A 64 bit compiled application will NOT work on 32bit system. So every application that needs to work everywhere will HAVE TO be able to compile & work also in 32bits version. Which means that the design of the application MUST restrain to 32bits limitations, and only implement some 64bits optimizations (key functions that have to be implemented in both versions and switch at compile time)

The key benefits of 64bits are for applications that need :
- heavy calculations on 64bits int (ex: maths problems solving). How many of Delphi developers where ever limited by the 4G values possible in 32 bits int ? most of the variables never hold values more than a few hundreds, maybe thousands
- huge memory requirements (more than 2GB). Again, how many developers create applications that can hold in memory a significant part of their hard drive ? and to be a significant leap forward you would have to run on a system with 6, 8 or maybe 10 GB of memory, otherwise your application would be swapping madly. And if you have such a 64bit system with that much memory, you could design your application to spawn different 32 bits PROCESSes (not threads), each limited to ~2GB, all working together, communication between them with TCP/IP in the local loop for example. You would then have the benefit of being able to extend easily this system of applications to run those processes on multiple MACHINES, therefore doing LOAD BALANCING, which is a much better design that a single process addressing 64bits memory space all by itself.

Which means, all combined, that there is only one out of millions of applications that really could use 64bits compilation, and none that absolutely need it.

>>Do you now have ideas? If yes, then please select the experts that contribute to your solution.
Yes, but I would like to keep this open until others comment about what ThievingSix comments.

Good point Geert;

But I thought using unicode would make the system app slow, because unicode uses international language on characters and strings,  that makes the system always find the language char,  while using only ansi focuses only on one language.

Can you submit a simple code delphi project that compares using unicode(using delphi2009) and ansi(using d5-d7) with the same output.


Thanks

Oh, you will never notice that if you have a fast computer processor and memory, as for me, I have compared them, I have a slow processor(celeron), slow memory(500mbfree).

Ok;

Thank you for the comments, I guess later to close the post.

.