Link Details

Link 45019 thumbnail
User 217101 avatar

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.
  • 15
  • 10
  • 3486
  • 1611

Comments

Add your comment
User 209827 avatar

evarlast replied ago:

3 votes Vote down Vote up Reply

If those things are what are wrong with .NET, then I think the list of things that are right must be very long.

User 187417 avatar

sproketboy replied ago:

-3 votes Vote down Vote up Reply
User 238564 avatar

FlySwat replied ago:

2 votes Vote down Vote up Reply

That link is major FUD.

User 238564 avatar

FlySwat replied ago:

2 votes Vote down Vote up Reply

For example:

"No Production Databases support stored procedures with .NET"

Is completely incorrect. SQL Server has had CLR integration since 2000.

User 247611 avatar

mycall replied ago:

-2 votes Vote down Vote up Reply

sproketboy: thanks for the link

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.