Lambda the Ultimate

inactiveTopic Whither Now C++?
started 9/8/2001; 11:17:15 AM - last post 9/10/2001; 2:51:40 AM
Ehud Lamm - Whither Now C++?  blueArrow
9/8/2001; 11:17:15 AM (reads: 417, responses: 2)
Whither Now C++?
The Evans Data Corporation predicts that sometime in 2002, about 55% of North American developers will spend at least some time working in Java.

That popularity is coming at the expense of C/C++ and Visual Basic. Throwing salt into the wound, by 2002, Evans Data predicts that only about 51% of programmers to still be working in C and C++ and their numbers will be declining fast.

There's still hope...

I usually don't like discussions of this sort since they tend to turn into religious wars. This article, however, is useful - since it gives the actual reasons that influence programmers decisions. These reasons may not be convincing, or even true, but it seems to me that they pretty much reflect how people decide which languages to use.

Only two days ago someone told me that he simply had to learn C++ in order to have a passing chance of finding a job. Maybe he'd better learn Scheme

Posted to general by Ehud Lamm on 9/8/01; 11:40:49 AM

jon fernquest - Re: Whither Now C++?  blueArrow
9/9/2001; 3:53:43 AM (reads: 453, responses: 0)
>Maybe he'd better learn Scheme :)

Scheme for functional programming elegance compiled down to C for speed: Both languages have been around in a stable form for over 20 years. A thorough explanation of how to do it is in:

Lisp in Small Pieces

Use Tiny-Clos or Yasos for an object system.

I like the idea of everything under the sun under the umbrella of one language, like Oz:

Creating extensive tool sets for a given domain in a single language promotes cross-platform re-use. (Programs written in separate languages have to be connected via some operating system mechanism.)


Jon Fernquest

Ehud Lamm - Re: Whither Now C++?  blueArrow
9/10/2001; 2:51:40 AM (reads: 425, responses: 0)
Notice that the Ada standard defines how to connect Ada programs and C, Fortran etc.