Ans
Object-oriented programming takes pride in its suitability
for sustaining huge software and web development projects. This is a far better
option than using structured programming when you have massive code bases. The
sheer nature of object-oriented programs allows the developer to save a lot of
time and energy when developing programs as the components of the programs are
in the form of objects which can be plugged into the program wherever they are
needed. So having an application with several hundred buttons implemented as
objects would be pretty easy to maintain, for example, if the developer wanted
to change the style or behavior of all the buttons, it would simply entail
changing a single object which defines everything about the button and this
would change every instance of the button object.
Even though object-oriented programming is suitable for large
project and long term maintenance of software of web projects, this method of
programming poses its own disadvantages as object-oriented programming tends to
be more complex than structured programming as there is a lot as far as design
the decisions that need to be made and consequently the entire task of managing
the project may be a bit difficult to the inexperienced web developer.
As for performance, from a user stand point, the difference
between structured and object-oriented programming may be minimal. However in
some cases the fact that object-oriented programs are slower seeing as there is
extra work the interpreter has to go through to compiler the classes as opposed
to the structure method of running in a top down sequence. This could make one
consider what method to use for their next web development project
OOP seems to be more
advanced than structured programming languages in terms of
technology (Boehm-Davis & Ross, 1992; Pennington, Lee, & Rehder,
1995), but it is also more complex and probably takes longer to learn
(Boehm-Davis & Ross, 1992; Kim & Lerch, 1992; Rosson & Gold,
1989). Many students become confused by the bewildering number of classes and
methods to be mastered (Mazaitis, 1993; Osborne & Johnson, 1993). The
amount of new elements to be learned certainly contributes to learning
difficulties. In addition, learning new material is made more complex
when some of the elements must be learned together (Sweller & Chandler,
1994).
As a result of all these factors, "the acquisition of
an object-oriented world view . . . will not happen overnight. The
frustration level of experts transitioning to OOP may be higher leading to
reports of disappointment and distress among such learners (and lending face
validity to claims about the effects of negative transfer). Such negative
factors do not mean that the switch will not take place. Alan Kay, one of
creators of the Smalltalk OOP language, remembers struggling
with object-oriented ideas when he was assigned to evaluate SIMULA-67
(the first object-oriented language) at the Palo Alto Research Center
of Xerox. When he "suddenly saw what SIMULA was trying to be," Kay
reported that "the shock of realization was so great that it was the last
time I ever thought in terms of subroutines and structures
No comments:
Post a Comment