Linked by Thom Holwerda on Thu 20th Mar 2008 17:52 UTC, submitted by WillM
Permalink for comment 305867
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.





Member since:
2007-02-05
There are many situations where it makes sense to work with managed code.
Typically applications that used to be VBA(in Access, adp-style. Connected to server, not using local db files obviously) are now often being ported to .NET
Aside from the fact that Microsoft slowly have been killing proper SQL-connectivity support in Access it makes sense. .NET is quite faster than VBA, they can write in a language that's quite familiar, popular(means more peopel and more resources.)
These are typicaly making programs such as project manegemant systems(for instance for the Oil Bussiness). None of these gives a rat's ass if these programs don't run faster than Lynx, all they care about is that it is easy to program, and get working. (Managed code may be slow but it's easier to avoid bugs, and easier to debug.)
In my experience I've found .NET to be faster than Java. Might been bad/good luck, but it wouldn't suprise me if that's the case. After all... .NET is prettymuch a ripoff after Java, only that it's made after Java so they could see what mistakes where made in Java and fix them from the start. (Not dissing Java though, it was in it's time quite a excellent idea! And it has multiplattform wich MS has chosen for obvious reasons not to implement in .NET)
Now, making 3D Studio Max in Java or .NET is probably not a good idea... but there are uses for managed code.