View Single Post
Old Jan 2nd, 2007, 3:58 PM   #7
Tim
Unverified User
 
Join Date: Dec 2006
Location: Bristol UK
Posts: 19
Rep Power: 0 Tim is on a distinguished road
Competly agree Arevos.

One thing that really gets me is that MS tie a .net release to a version of Visual Studio. This means if you want to develop .net 2.0 apps using Visual Studio you have to upgrade to 2005. I can see the business sense behind this but it does not help developers migrate to newer versions of .net.

One thing that saddends me is that there is this move away from programming native (as MS call it) code. If you teach someone java or some .net language they dont have to worry about the complexities of the platform. There is no need to teach about memory management or pointers(though in c# pointers are still present). This is all brought about though the use of a managed runtime. This is all great but the memory and cpu overhead it produces makes me want to cry.

In Delphi(win32 version) I can create a VCL app that when running uses about 5MB of ram, but when the same app is ported to .net it consumes over 25MB of memory and is noticably slower. There are some people that say that this memory overhead is the price we have to pay for RAD and secure programs, but Delphi can do RAD and it is possible to create secure programs easily using it, yet it is fading away.

I dont understand it, is it just because some people believe the average programmer is completly incompetant and cant be trusted with pointers and memory management? Or is it just the marketing departments of companys such as MS and Sun telling us to use these technologies?
Tim is offline   Reply With Quote