It does look like a high degree of pet subject enthusiasm on the part of the person running the course. As much as Java is mentioned in the article, Java did not invent object orientation and there are many other Object Oriented languages or languages which have embraced object orientation after their initial invention. I don't see functional programming being the silver bullet which makes all Object Oriented systems redundant.
Is what is being suggested here that data and functionality should be kept separate for the greater good? I can see some of what is being suggested but I don't believe that having data in special data structures and functions to work on the data automatically makes a system more modular and reusable. The code in the function may expect data in a very problem specific way or the function may perform functionality which is so specific to a given problem that it may not be any more reusable than code on an object where the data and code are combined together. Having data and functionality separate is somewhat the case with C isn't it. C however does have some state by virtue of static variables which can point to some other kinds of state holding structures. I don't know. Some of these food fights and almost dogmatic talk of the one enlightened way of doing things can make me feel fed up with the whole programming community. I always end up doing the wrong thing according to someone. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
