Disadvantages of object-oriented programming language

Answer 1

There are no disadvantages in OOP itself -- it's just a tool. Like any other tool, if used appropriately, there can be no negatives. But if used inappropriately, companies could collapse and countries could fall. The secret to good OOP code is simply good design. Get that wrong and you'll spend most of your time redesigning instead of addressing the problem you were actually trying to solve.

Not every problem can be addressed with OOP -- it is not a silver bullet (and was never intended as such). If the data is modelled on a relational database, then OOP is probably the best approach, but for anything else you'd be better looking elsewhere before considering OOP. By the same token, C++ isn't always the best language to use when you want a working solution as quickly as possible, but at least you get the choice whether to use OOP or not. Some languages give you no option whatsoever, which is disadvantageous by itself.

Answer 2

* Unfamiliarity (causing an added training cost for developers). * Inability to work with existing systems (a major benefit of C++) * Data and operations are separated * No data abstraction or info hiding * Not responsive to changes in problem space * Inadequate for concurrent problems

Answer 3

One of the biggest problems with Object-Oriented Design is that programmers, in their enthusiasm to tackle and master new technologies, get ahead of themselves in learning the system completely, so many wind up confused as to what the system entails and how to properly use it. Managers and programmers may also confused style with substance, forgoing information for the sake of a better-looking program, and abandon more traditional - if better working - design processes. In addition, programmers using Object-Oriented design are often insufficiently trained in the programming method.

Answer 4

1) OOP is a high level concepts so takes more time to execute as many routines run behind at the time of execution.

2) Offers less number of functions as compared to low level programming which interacts directly with hardware.

3) Increased burden on part of OOP developer.

Answer 5

An object-oriented, while a good choice and a perfect approach for many problems, tends to encourage over-engineered solutions to certain problems. As with everything, there is no single tool for all tasks, and careful selection of the tool and solution architecture is necessary as a first step.

Traditionalists believe that the code generated by object-oriented language compilers is less efficient than code generated not only by low-level languages, but also less efficient than code generated by high-level, not object-oriented, languages. This is nonsense; while skilled and hand-optimized use of low-level languages will always be more efficient than any high-level language, the object oriented nature of a particular language does not necessarily lead to less efficient code.

However, the temptation for over-engineered solutions using OOP is big, and that in turn can lead to reduced efficiency.

Answer 6

Form And Substance

Project managers and programmers may confuse style with substance. Some developers and managers today believe that OOAD simply means defining classes, objects, and methods. It is like what happened when structured programming development became popular. Developers and managers at first thought that structured development simply meant that one had to remove GOTO statements and increase the use of subroutines. While these steps helped, they were just surface features of a deeper group of more significant principles.

Implications of OOAD

Managers and developers may not recognize all the implications of OOAD. They often assume that using OOAD will eliminate development bottlenecks. This is due to expectations that OOAD will reduce the complexity of programs and will provide architectural modularity. This different approach to architecture may work better with different management and scheduling techniques.

Abandonment of Traditional Design Processes

Managers may be tempted to ignore or abandon traditional software design and engineering processes. OOAD is often adopted because of the promise of increased productivity coupled with a shortened development schedule. However, a sufficient amount of development time is often not allowed that will make sure the design processes are followed correctly. This may actually result in bigger problems. These include missed deadlines, schedule slippage, and project failures.

Insufficient OOAD Training

Finally, one of the disadvantages of object oriented analysis and design is that developers may get some education about OOAD, but not enough. A false sense of programming confidence may stem from just reading articles, or even a book, or taking a class in it. Programmers will need time to immerse themselves in the nuances of OOAD.

Answer 7

There are no disadvantages in OOP itself -- it's just a tool. Like any other tool, if used appropriately, there can be no negatives. But if used inappropriately, companies could collapse and countries could fall. The secret to good OOP code is simply good design. Get that wrong and you'll spend most of your time redesigning instead of addressing the problem you were actually trying to solve.

Not every problem can be addressed with OOP -- it is not a silver bullet (and was never intended as such). If the data is modelled on a relational database, then OOP is probably the best approach, but for anything else you'd be better looking elsewhere before considering OOP. By the same token, C++ isn't always the best language to use when you want a working solution as quickly as possible, but at least you get the choice whether to use OOP or not. Some languages give you no option whatsoever, which is disadvantageous by itself.

Answer 8

object oriented language involves a large code

Answer 9

not user interactive.