Lambda the Ultimate

inactiveTopic Seven Paradoxes of Object-Oriented Programming Languages
started 8/7/2003; 4:02:07 PM - last post 8/8/2003; 4:25:51 AM
Patrick Logan - Seven Paradoxes of Object-Oriented Programming Languages  blueArrow
8/7/2003; 4:02:07 PM (reads: 270, responses: 1)
David Ungar is giving a keynote on seven paradoxes of object-oriented programming languages at OOPSLA 2003.

His list:

1. Because programming languages, development environments, and execution engines are intended for both people and computers, they must both humanize and dehumanize us.

2. Adding a richer set of concepts to a programming language impoverishes its universe of discourse.

3. Putting a language's cognitive center in a more dynamic place reduces the verbiage needed to accomplish a task, even though less information can be mechanically deduced about the program.

4. The most concrete notions are the most abstract, and pursuing comfort or correctness with precision leads to fuzziness.

5. Although a language, environment, and execution engine are designed for the users' minds, the experience of use will alter the users' minds.

6. Object-oriented programming has its roots in modeling and reuse, yet these notions do not coincide and even conflict with each other.

7. A language designed to give programmers what they want may initially succeed but create pernicious problems as it catches on. However, a language designed to give programmers what they really need may never catch fire at all

Frank Atanassow - Re: Seven Paradoxes of Object-Oriented Programming Languages  blueArrow
8/8/2003; 4:25:51 AM (reads: 237, responses: 0)
It is nearly too obvious to note, but none of these, not even #6, has anything particularly to do with object-oriented programming languages.

Either that or everything is now considered OO and so the designation has become trivial.