Lambda the Ultimate

inactiveTopic The Future of .NET Languages
started 10/15/2003; 2:49:49 PM - last post 10/16/2003; 5:44:08 AM
Ehud Lamm - The Future of .NET Languages  blueArrow
10/15/2003; 2:49:49 PM (reads: 7714, responses: 2)
The Future of .NET Languages
One of the unique aspects of the .NET platform is its support for multiple programming languages, with over 23 available today. How do these multiple languages influence the design of the CLR and CLS? How can languages written to the CLS differentiate themselves from one another? Join the architects of languages including C#, C++, VB.NET, Eiffel, and Cobol to get their insight on how they design new language features, for "Whidbey" and beyond.

One of the more interesting panels planned for the upcoming PDC.

The web page allows you to submit questions for the panelists, as well as to vote for questions already posted.

Since the answers should find their way to the web, even those not planning to attend the PDC may want to submit questions.

Among the panelists you'll find Anders Hejlsberg and Erik Meijer, representetives from the VB team and the Visual C++ team, as well as others.

Posted to cross-language-runtimes by Ehud Lamm on 10/15/03; 2:51:55 PM

Ehud Lamm - Re: The Future of .NET Languages  blueArrow
10/16/2003; 12:49:17 AM (reads: 414, responses: 0)
If anyone wants to have a go at answering the questions already posted, fel free to use the discussion group.

Patrick Logan - Re: The Future of .NET Languages  blueArrow
10/16/2003; 5:44:08 AM (reads: 402, responses: 0)
Any thoughts on creating a .NET language targeted at "occupational" programmers i.e. folks that aren't programmers but need to essentially encode/automate an algorithm, run it repeatedly and store the results? I would think this could be a great addition to VSA where an admin assistants with no formal programming training might be able to write a small program to automate a task in an Office app.

Here's a suggestion from the 1970s...

Multics Emacs proved to be a great success -- programming new editing commands was so convenient that even the secretaries in his office started learning how to use it. They used a manual someone had written which showed how to extend Emacs, but didn't say it was a programming. So the secretaries, who believed they couldn't do programming, weren't scared off. They read the manual, discovered they could do useful things and they learned to program.

Here's another idea the was demonstrated in the 1970s...

In 1972 Kay took a job at Xerox's Palo Alto Research Center (Xerox PARC) and began using Smalltalk in an educational context. Young children were exposed to computers and their reactions were analyzed. Kay concluded that children learned more through images and sounds than through plain text and, along with other researchers at PARC, Kay developed a simple computer system which made heavy use of graphics and animation. Some of the children became very adept at using this system; in fact, some developed complicated programs of their own with it!

Yes, I think (no surprise) it would be great if the newest "manage runtime" could manage support for the longest-used "managed runtimes"!