what next after object oriented programming

[Bill Mc Coy]

computer science in 1970 relied on modular programming and so c and c++ were developed
in 1990 object oriented programming came to scene and presently object oriented programming languages like java .net rule roost
what will be next development after OO programming???

[Jesus Angeles]

Ill say, spuck-oriented programming. No more objects. We program direct to the machine-language. We think it, code it, and boom, we time-travel, or whatever you wish.

[Devesh H Rao]

AI

[Ernest Friedman-Hill]

Well, we've stepped back quite a bit already from object-oriented programming; we've got XML-oriented programming (configuration-driven programming) in a lot of cases now.

Quite a few folks seem to think that MDA -- Model Driven Architecture, in which a product specificiation is used to automatically generate all code, with no actual programming involved -- is the next big thing. I think in certain application areas, that's probably true, although not generally.

[Mark Spritzler]

Originally posted by Ernest Friedman-Hill:
Well, we've stepped back quite a bit already from object-oriented programming; we've got XML-oriented programming (configuration-driven programming) in a lot of cases now.

Quite a few folks seem to think that MDA -- Model Driven Architecture, in which a product specificiation is used to automatically generate all code, with no actual programming involved -- is the next big thing. I think in certain application areas, that's probably true, although not generally.

Yeah, I love it. Make a Drawing and POOF! System!

Mark

[Bear Bibeault]

What's next?

Colossus, P1, Skynet, Janus and the CodeMaker.

(For the non-SciFi fans, these are all examples of future software gone horribly wrong).

[Max Habibi]

BPM.

As a guy who's written several books on Java, who's heavily invested in it's success, and has worked for Sun Microsystems and IBM, BPM is to JEE what JEE is to assembly.
[ February 17, 2007: Message edited by: Max Habibi ]

[Mark Spritzler]

ESB

Enterprise Service Bus

The easy way to move messages and transform them between disparaging systems.

Mark

[Jim Yingst]

I hate working with disparaging systems.

[Ernest Friedman-Hill]

Seriously. I'll be all, like, typing away, and all of a sudden the disparaging system will be like, all "Your shirt is ugly", and I'll be like, all "your algorithms are primitive," and then it'll just be like all, "you need a shave", and so I'll be like, "you lack cohesion." And we just go back and forth like that until one of us storms out.

[Max Habibi]

Dude, you crack me up

[Jim Yingst]

Do you think maybe Mark meant desperate systems? Those can also be difficult to work with. You think you've found a nice, reliable place to store your data - and then one day you find out that it's been sold at the local pawn shop in order to raise cash for a quick fix of RAM. Very discouraging. So far random testing seem to be the best way to at least detect such problems, but maybe this "ESB" thing can help prevent such problems at the source. That would be cool.

[Avi Nash]

SOA.

[Ulf Dittmer]

SOA

Architecture trends come and go, but language trends are more long-lived. SOA could be implemented in any programming language paradigm invented so far, and in any that's still to come, as long as it's Turing-complete. (Of course, a language would be rather uninteresting if it weren't.)
[ February 19, 2007: Message edited by: Ulf Dittmer ]