Comments

Besides the dynamic language bits, which are nice, what is interesting about the DLR is that they are refactoring the CLR aka CoreCLR.

You should definitely check out Tomas' blog, which littleguru linked above.  He has an article with a code sample library for implementing asynchronous workflows-like code in C#, as well as a nice set of articles introducing F#.

As interesting as F# is, I would still love to see LISP or SCHEME running on the CLR/DLR. I would find it absolutely delightful if a user-friendly dialect of LISP became the most popular software development language 5 years from now, with versions to generate CIL and JVM (and maybe Dalvik) bytecode.

Somebody posted this earlier in the thread. It's the download link for the MSDN Library for Visual Studio 2008 DVD ISO.

BlackTiger wrote:

Ok. Downloading...

But... No MSDN library for VS2008?

evildictaitor wrote:



JChung2006 wrote:  JohnnyAwesome wrote: They wrote J Script in the time-span of several weekends? And he wrote that in Lisp and then rolled a C translator from scratch? There is a reason why I could not work at Redmond and that just about summarizes it. It's not that difficult, especially if you've done it before, like most people would have in any decent computer science graduate program.

Bearing in mind that Computer Science graduate programs didn't exist fifteen years ago, and were a one-year extention of a maths or engineering course.

SecretSoftware wrote:

Why does C++ even exist? Why does MS keeps maintaining such a language that caused so many buffer overflows, and generally was not as secure as C# or Vb.NET.

The only + point for C++ is that it compiles into machine code directly, and if we can get C# to do that, then there is no need for a language like C++.

I was wondering why C++ still exists when C# is that good of a language.


MS, why not retire C++, and just focus on C# and Vb.NET and F#?

Expand C# capabilities, and get rid of P/invoke and replace it with a new kind of mechanism to call dlls outside the .NET framework.

Finally, make the .NET framework really .NET, in the sense that it is distributed in terms of processing power, by enabling sharing. So that my application could use the processor that is Idle in a second room in the the house, automatically through the use of Remoting in LAN.

Kill C++, and lets all be on one page, with C#.

Its confusing many people, and things needs to be simpler, with few languages. C# for experts, VB.NET for beginners and intermediates.

That is all.

PS: some might say, there are programmers outthere who enjoy dealing with buffer overflows, and the pains of C++, and to them I say stick with Visual Studio 6 C++ IDE. and that is that.

Charles, I'm surprised that you didn't mention that Chad was one of the authors of the "Pickaxe" book.

Programming Ruby: The Pragmatic Programmer's Guide

staceyw wrote:

I have been through the VB variant type years ago and I don't want to go back to that.

They are not advocating going back to that; I recall their comments about C being a weakly typed language and how that was not a good thing.  The dynamic languages that they evangelize are strongly typed.