By gst
via higherlogics.blogspot.com
Published: Sep 30 2007 / 13:54
(May 3, 2007)
I work with .NET everyday, and it's a decent virtual machine from the developer's perspective, and a slight overall improvement over Java in a number of respects.
But for a language implementor, .NET continues a tradition of mistakes that began with Java, which inhibit it from achieving its much touted goal as the Common Language Runtime (CLR). These issues are divided into two categories: blatant mistakes, and nice to haves. The former requires no cutting edge features or research to implement, and the CLR should have had them from the get-go. The latter might have required some research to get right (like they did with generics), but which are ultimately required for a truly secure and flexible virtual machine.
Comments
evarlast replied ago:
If those things are what are wrong with .NET, then I think the list of things that are right must be very long.
sproketboy replied ago:
http://www.helpdesk-software.ws/it/29-04-2004.htm
FlySwat replied ago:
That link is major FUD.
FlySwat replied ago:
For example:
"No Production Databases support stored procedures with .NET"
Is completely incorrect. SQL Server has had CLR integration since 2000.
mycall replied ago:
sproketboy: thanks for the link
Voters For This Link (15)
Voters Against This Link (10)