I just caught my self in discussing the same subject with 4 of my colleagues in row, which in fact made me this blog entry.
When I wrote my first program in cobol when I was in school, It was all sequence of statements which we used to generate school reports. Though it was a business programming language for me it looked fun and I started practicing, and then it was C, C++ and now Java, the first flow chart that I wrote was mainly for step-by-step solution to a given problem, now when look at thefuture of programming technologies it’s all graphical programming languages and concurrent programming is crap. Now all my flow charts are for a business process. each block which was a statement earlier is piece of UI now.
Abstractness, programming is getting so abstract that developers don’t have to show their level of competence and which we all (Developer Community) go to think whether we need this shift. I personally don’t like this shift as we have lot things to do and graphical programming is completely unusable in complex programming. Only thing that we do is zoom in and zoom out and we loose the whole context.
Since we all live in SAP space, there were quite a lot arguments saying event driven programming is a must when we deal with large data sets, learning is easy and you can spin events to get the required result more quickly.
Either we like or dislike what I see is we got to use graphical programming techniques and its forward engineering. Quite a lot progress I see is everything is coming down to modeling and with eclipse. In fact it’s reducing lot of human effort, with which we have stuck in sequential programming.
Beauty of latest NWDS is a good compromise between texts and graphical, for sure it is easier and more productive, just to bias between two things that I’m discussing what I see is next-generation programming languages may not resemble its predecessors in any way other than performing advanced functionality.