IT SOLUTIONS
Your full service technology partner! 
-Collapse +Expand
Delphi
Search Delphi Group:

Advanced
-Collapse +Expand Delphi To/From
To/FromCODEGuides
-Collapse +Expand Delphi Store
PRESTWOODSTORE

Prestwood eMagazine

June Edition
Subscribe now! It's Free!
Enter your email:

   ► KBProgrammingDelphi for W...Language Basics   Print This     
Part of the mo. lesson in the May 15 Issue of Prestwood eMag
Delphi Q&A Flashcard:
 A flashcard from our Delphi Flashcards Library
 A FAQ from our Delphi FAQ Page
Native Code versus Managed .Net Code

Question:

What are the benefits of Win32/64 native code such as in Delphi over .Net?


Answer:

In general terms, native code offers faster potential performance and a smaller footprint but can be more complex to build. Also, native code does not require .Net's runtime -- Common Language Runtime (CLR).


Comments

1 Comments.
Share a thought or comment...
Comment 1 of 3

Now you need an article on what you MISS in Win32/64 that .Net could give you.  Things like WPF and SilverLight.  Xaml, binding, etc.

I probably won't ever code a Win32/64 app again unless Microsoft drops .Net.

---
Mark
Posted 11 years ago

Comment 2 of 3

Depending on your needs , decide for Native or .Net

Doing a lot of industrial software (network stuff , database etc ) on mostly not the latest and greatest harware,I can usualy write a delphi program consisting of one executable using little resources , well .. compared to the overheads with .Net

Eric

---
Eric B
Posted 11 years ago

Comment 3 of 3

What overheads?  (I know it was posted a long time ago)

And whether it is one file or a bunch of files doesn't make any difference in Silverlight.  You just "publish" and whatever is required is pushed to the server.  And if I want to do it manually, I just zip it, transfer it, and unzip it.  Not really a big deal.

Plus, having the app split into multiple files is sometimes a GOOD thing.  Like right now, I have a co-worker who is coding in C#.  But I am building a separate assembly that we can both use. In fact, when using the MVVM pattern, it is nice to be able to totally split the pieces into their corresponding parts as separate assemblies.  That way you are SURE that there is no co-dependence between the parts.

So in other words, I certainly don't care whether there is 1 file or 50.

Similarly, the computers nowadays are so bloated in their capacities that it is a hard thing to do to get them running out of resources.  I haven't seen any problem with resource usage as far as memory is concerned.

And as for performance, I have yet to think, "Yeow, this thing performs terribly, I wish I had stayed with Delphi."  Instead I think, "I would dread to go back to Delphi".

Posted 9 years ago
 
Write a Comment...
...
Sign in...

If you are a member, Sign In. Or, you can Create a Free account now.


Anonymous Post (text-only, no HTML):

Enter your name and security key.

Your Name:
Security key = P1186A1
Enter key:
FAQ Contributed By Mike Prestwood:

Mike Prestwood is a drummer, an author, and creator of the PrestwoodBoards online community. He is the President & CEO of Prestwood IT Solutions. Prestwood IT provides Coding, Website, and Computer Tech services. Mike has authored 6 computer books and over 1,200 articles. As a drummer, he maintains play-drums.com and has authored 3 drum books. If you have a project you wish to discuss with Mike, you can send him a private message through his PrestwoodBoards home page or call him 9AM to 4PM PST at 916-726-5675 x205.

Visit Profile

 KB Article #101244 Counter
11462
Since 6/26/2008
Sales Website: www.prestwood.com Or visit our legacy sales site: 
legacy.prestwood.com


©1995-2021 Prestwood IT Solutions.   [Security & Privacy]