Re: .Net applications, not optimized for CPU at all?
- From: Eric Grange <egrangeNO@xxxxxxxxxxxxxxx>
- Date: Sat, 29 Apr 2006 09:55:18 +0200
> then you already saved disk space vs native win 32 apps with .net apps
How so? I mean apart from 'hello world' class of applications (which are comparable to the size of Delphi when using BPLs), the .Net EXE and DLL didn't strike me as being particularly lean at all compared to native versions.
The .Net DLLs especially are huge, things like Tao.OpenGL, at 2 MB+, is about 10 times the size of the equivalent Delphi *DCU*, and even Microsoft-provided DLLs are huge for the amount of things they do, meaning it's not a programming mistake of non-microsofties that makes the DLLs big, f.i. System.Windows.Forms.dll at 2MB is similar to the whole VCL (and S.W.F.dll's code, in itself, covers only a fraction of what the whole VCL code covers).
IME .Net EXEs and DLLs size is in the same order of magnitude as their code size, just like for DCUs in Delphi, except that in native Delphi applications, the linker links those DCU into EXE/DLL, that are typically one order of magnitude smaller than their DCUs (and more when you use a little bits of functionnality from a lot of big standard libraries).
Eric
.
- Follow-Ups:
- Re: .Net applications, not optimized for CPU at all?
- From: Andre Kaufmann
- Re: .Net applications, not optimized for CPU at all?
- References:
- .Net applications, not optimized for CPU at all?
- From: Arthur Hoornweg
- Re: .Net applications, not optimized for CPU at all?
- From: Euan Garden
- Re: .Net applications, not optimized for CPU at all?
- From: Arthur Hoornweg
- Re: .Net applications, not optimized for CPU at all?
- From: Euan Garden
- .Net applications, not optimized for CPU at all?
- Prev by Date: Re: VCL Components Interfaces list
- Next by Date: Re: VCL Components Interfaces list
- Previous by thread: Re: .Net applications, not optimized for CPU at all?
- Next by thread: Re: .Net applications, not optimized for CPU at all?
- Index(es):
Relevant Pages
|